Tracing provides information about activities carried out by an application. Trace output is sent to the server’s log file. To establish the level of detail for logging and tracing:
Use the Management Console to connect to EAServer.
Expand the Servers folder, and select the server.
On the Log/Trace tab, select or unselect the following properties:
Capture Console Output in Log Writes messages that display in the console to the server log file.
Enable HTTP Request Log Generates an HTTP request log. Logs are named serverName-http-YYYY-MM-DD.log and created in the logs subdirectory. serverName is replaced with the name of the server and YYYY-MM-DD is replaced with the current date.
Enable java.sql.DriverManager Log Writes DriverManager log messages to the server log.
Generate Exception Cross-Reference Cross-references exceptions in the server log file.
Generate Transaction Cross-Reference Cross-references transactions in the server log file. To start transaction tracing from the command line, use the logTransaction flag when you start EAServer
Log Application Exceptions Writes application exceptions to the server log. If a deployed module requires that application exceptions be logged, set either the ejb.logExceptions (EJB) or web.logExceptions (Web applications) property in the module’s XML configuration script to true. You can edit this script in the Management Console, using the module’s Configuration tab.
Log System Exceptions Writes system exceptions to the server log. To log system exceptions, use the same technique described in Log Application Exceptions, above.
JMX Logging Level The logging level for the Systems Management JMX agent. See “Running the SNMP subagent” in Chapter 14, “Systems Management,” in the EAServer System Administration Guide.
Enable RMI-IIOP Trace Traces remote method invocations for IIOP and RMI-IIOP in the server log. You can also enable RMI-IIOP tracing from the command line, which does not change the value in the server properties file. To start IIOP tracing from the command line, use the rmiiiopTrace flag when you start the server.
WARNING! Enabling RMI-IIOP trace may result in plain-text passwords appearing in the server log, depending on the authentication mechanism used by remote clients.
Enable RMI Local Trace Traces local RMI method invocations (intercomponent calls) in the server log. To start tracing from the command line, use the rmiiiopTraceLocal flag when you start the server.
Enable EJB Trace Traces EJB component invocations in the server log. To start EJB tracing from the command line, use the ejbTrace flag when you start EAServer.
Enable Web Trace Traces Web component invocations in the server log.
Enable JMS Trace Traces Java Message Service (JMS) operations in the server log. All public and protected JMS provider methods are traced. To start JMS tracing from the command line, use the jmsTrace flag when you start EAServer.
Enable SQL Trace Traces JDBC driver activity in the server log, including JDBC prepared statement operations, parameter and result information for container managed persistence operations (queries and updates), and transaction commit/rollback operations. To start SQL tracing from the command line, use the sqlTrace flag when you start EAServer.
You can also enable these logging and tracing properties from the command line or in the setenv.bat[sh] file—see “Managing system logging”.
For information on viewing the log files, see “Viewing server log files” in Chapter 11, “Runtime Monitoring,” in the EAServer System Administration Guide.
