EAServer traces

EAServer provides trace facilities to help you obtain information on different areas of activity:

Server level—see Table 1-1.
Open Server—see Table 1-2.
Methods as Stored Procedures (MASP)—see Table 1-3.
Listeners—see Table 1-4.
Security—see Table 1-5.
Servlets and Web applications—see Table 1-6.
Components—see Table 1-7.
Message service—see Table 1-8.
Java class loading and unloading—see Table 1-9.
Additional Java and JVM tracing—see Table 1-10.
Connections and transactions—see Table 1-11.
Web server redirector—see Table 1-12.
PowerBuilder or C/C++ clients—see Table 1-13.
Other related properties—see Table 1-14.

The tables below describe the options available in each area.

Some properties exist only in certain EAServer versions. Check the documentation and release notes for your EAServer version.

For information about setting the com.sybase.jaguar.* properties, see Appendix B, “Repository Properties Reference,” in the EAServer System Administration Guide. Consult PowerBuilder Application Techniques for information about how to configure the PowerBuilder properties.

**Table 1-1: Server-level tracing**
Name	Description
com.sybase.jaguar.server.lwc.debug	Logs the EJB-to-EJB calls that use the lightweight container.
com.sybase.jaguar.server.logspid	Includes the thread identifier in each message in the log file. To enable this property, you must add “%SI” to the server log profile.
com.sybase.jaguar.threadmonitor.trace	Logs peak number of active and waiting threads in server log. If com.sybase.jaguar.threadmonitor.callstats is nonzero, also enables printing call statistics.
com.sybase.jaguar.threadmonitor.callstats	Number of seconds between call statistics in server log.
com.sybase.jaguar.instancepool.debug	Logs named instance pool information.
com.sybase.jaguar.server.flowcontrol.trace	Initialization and processing for flow control.
com.sybase.jaguar.CosNaming.debug	Outputs server- and cluster-naming properties. You must set this property on the Advanced tab of the CosNaming package.
com.sybase.jaguar.server.dynamo.trace	Traces PowerDynamo plug-in calls.
Synchronization -verbose	Sends verbose output to the log during synchronization. You can set this property using either the Synchronize Cluster dialog box in EAServer Manager or jagtool—see the EAServer System Administration Guide for more information.

**Table 1-2: Open Server tracing**
Name	Description
com.sybase.jaguar.server.tracenetdriver	Traces network driver requests
com.sybase.jaguar.server.tracenetrequests	Traces requests to transport control layer (an internal EAServer library that serves as an interface to network drivers)

**Table 1-3: MASP tracing**
Name	Description
com.sybase.jaguar.server.traceattentions	Tracks TDS (Tabular Data Stream™) protocol attentions
com.sybase.jaguar.server.tracetdsdata	Tracks TDS packet contents
com.sybase.jaguar.server.tracetdshdr	Tracks TDS header contents

**Table 1-4: Listener tracing**
Name	Description
com.sybase.jaguar.server.http.cache.debug	Writes static page cache information to the server log.
com.sybase.jaguar.server.iiop.log	IIOP logging. Output is verbose.
com.sybase.jaguar.server.iiop.log.ac	IIOP logging for events that occur after the server begins accepting messages. Less output than com.sybase.jaguar.server.iiop.log; omits server start-up messages.
com.sybase.jaguar.server.http.requestlogenable	Logs all HTTP requests. Enabled by default.
com.sybase.jaguar.server.http.elffenable	Determines if the extended log file format is used to write information to the request log.
com.sybase.jaguar.server.http.elffitems	Determines the items that are logged and the order in which they are written to the request log. Fourteen items can be logged, including request, status, bytes, and cookie—see Appendix B in the EAServer System Administration Guide for the complete list.

**Table 1-5: SSL connection tracing**
Name	Description
com.sybase.jaguar.security.logpeerIP	If this property is set to true in an SSL listener’s security profile, a client’s IP address is logged when an SSL connection cannot be established. The default value is false.

**Table 1-6: Servlets/Web applications tracing**
Name	Description
com.sybase.jaguar.server.servlet.trace	Sets trace logging in EAServer servlet execution engine
com.sybase.jaguar.webapplication.sectrace	Sets security implementation tracing

**Table 1-7: Component tracing**
Name	Description
com.sybase.jaguar.component.debug	Logs trace information for instance lifecycle events (creation, destruction, pooling and so on)
com.sybase.jaguar.component.trace	Logs methods and parameters
com.sybase.datawindow.trace	Set to true to enable tracing for the Web DataWindow component (DataWindow/HTMLGenerator)

**Table 1-8: Message service tracing**
Name	Description
com.sybase.jms.debug	Enables message service JMS debugging To help debug your JMS client application, you can enable tracing by setting this property to true in the InitialContext object. When you enable tracing, diagnostic messages are printed in the console window. By default, tracing is disabled. This code sample illustrates how to set the tracing property: Properties prop = new Properties(); prop.put(“com.sybase.jms.debug”, “true”); javax.naming.Context ctx = new javax.naming.InitialContext(prop);
cms.debug	Enables all message-service debugging options You can set this property and the following two properties in the MessageServiceConfig.props file, located in $JAGUAR/Repository/Component/CtsComponents.
cms.debug.network	Enables message service network-level debugging
cms.debug.session	Enables message service session-level debugging

**Table 1-9: Java class loading/unloading tracing**
Name	Description
com.sybase.jaguar.server.jvm.verbose	Logs all Java classes loaded and the location where each class file was read
com.sybase.jaguar.server.classloader.debug	Logs information about loading classes from custom class lists defined for the component, package, application, or server
com.sybase.jaguar.server.jvm.verboseGC	Logs information when memory is freed by the Java garbage collector

**Table 1-10: Additional Java tracing**
Name	Description
com.sybase.jaguar.server.jvm.debugging	Enables Java in-server predebugging in the pre-4.1.3 debug server. In EAServer version 4.1.3 and later, simply use the debug server.
com.sybase.jaguar.server.jvm.debug.options	Enables additional JVM options to configure in-server Java debugging.
com.sybase.jaguar.server.jvm.displayOptions	Writes the current JVM properties to the server log.
com.sybase.jaguar.server.jvm.nojit	When using the Client Hotspot JVM, indicates whether the JIT (just-in-time) compiler is disabled. In EAServer versions earlier than 4.1, the default for new servers is true. In 4.1 and later, the default is false.
com.sybase.jaguar.server.jvm.options	Specifies options to pass to the server’s Java virtual machine.
com.sybase.jaguar.server.jvm.minHeapSize	Specifies the minimum heap size for the server’s Java virtual machine.
com.sybase.jaguar.server.jvm.maxHeapSize	Specifies the maximum heap size for the server’s Java virtual machine.

For more information about the cmp_driver properties defined in Table 1-11, see Chapter 4, “EJB CMP Tuning,” in the EAServer Performance and Tuning Guide.

**Table 1-11: Connection and transaction tracing**
Name	Description
com.sybase.jaguar.server.jcm.trace	Traces Java Connection Manager (JCM) activity.
cmp_driver_debug	Tracks what the driver wrapper is doing; for CMP (container-managed persistence) wrapper driver.
cmp_driver.print_warnings	Logs all database warning messages received by driver wrapper; for CMP wrapper driver.
cmp_driver.trace_commit	Traces transaction commit, rollback, and autoCommit changes for CMP wrapper driver.
cmp_driver.trace_connect	Traces connect and reconnect operation for CMP wrapper driver.
cmp_driver.trace_create	When using the Sybase driver (CMP JDBC wrapper for Sybase jConnect driver), traces the creation of semipermanent stored procedures.
cmp_driver.trace_execute	Traces the execution of stored procedures and SQL command batches; for CMP wrapper driver.
cmp_driver.trace_execute_ms	Traces the execution of stored procedures and SQL command batches that take longer than the specified number of milliseconds. Takes precedence over cmp_driver.trace_execute; for CMP wrapper driver.
com.sybase.jaguar.conncache.cmp_stats	Seconds between “Table Statistics” entries in the server log when using CMP.
com.sybase.jaguar.server.jta.trace	Java Transaction API; set to an integer for the desired trace level.

For information about setting the Web server redirector properties, see the EAServer Installation Guide for your platform.

**Table 1-12: Web server redirector tracing**
Name	Description
Connector.LogLevel = [inform \| error \| verbose]	Add this directive to the Web server redirector plug-in configuration file, and specify the logging level: inform, error, or verbose.
Connector.SessionId ID	Traces requests from connectors. Set this directive in the redirector config file so the connector appends the value of Connector.SessionId to the URL forwarded to EAServer. EAServer writes the URL to the server’s HTTP request log to help in debugging.

**Table 1-13: PowerBuilder or C/C++ clients**
Name	Description
ORBLogIIOP	Specifies whether the ORB should log IIOP protocol trace information. If set to true, enables logging. The default is false. This parameter can also be set in the JAG_LOGIIOP environment variable. When this parameter is enabled, you must set the ORBLogFile option (or the corresponding environment variable) to specify the file where protocol log information is written.
ORBLogFile	Sets the path and name of the file in which to log client execution status and error messages. This parameter can also be set in the JAG_LOGFILE environment variable. The default setting is no log.
JAG_LOGFILE environment variable	Setting this variable is an alternate way to set the ORBLogIIOP and ORBLogFile properties.

**Table 1-14: Other related properties that do not affect logging**
Name	Description
com.sybase.jaguar.component.cpp.debug	Determines whether to catch exceptions for a C++ component.
com.sybase.jaguar.server.debug.useagent	Specifies the remote debugging interface. If set to true, the server supports Java debugging using the sun.tools.debug interface. If set to false, the server supports remote debugging using the JPDA (Java Platform Debugging Architecture) interface.
com.sybase.jaguar.server.jpda.port	Specifies the port number for JPDA remote debugging connections.
com.sybase.jaguar.component.pb.debug	Specifies whether a PowerBuilder component can be debugged while executing.
com.sybase.jaguar.component.refresh	Specifies whether the component implementation can be replaced without restarting the server. For Java components, if refresh is disabled, the component is loaded in the system class loader, using the system CLASSPATH setting. If refresh is enabled, the EAServer class loader loads the component using the settings in the Component Properties/Java Classes tab. For C++ components, refresh is supported by running a copy of the specified component DLL or shared library.
com.sybase.jaguar.webapplication.web-resource-collection	A comma-separated list of HTTP methods including: POST, GET, TRACE, DELETE, PUT, OPTIONS.