You can configure some EAServer subsystems to log trace data to the server log file, including:
Thread monitors, to log performance data for the components to which you have assigned the monitor. See “Thread monitors” for more information.
For EJB CMP entity beans, you can configure the EAServer JDBC wrapper driver to record query execution statistics. See “CMP runtime monitoring” for details.
For in-server Java code, you can turn on tracing for the custom class loader. You can use the trace to identify classes that are loaded redundantly for different components and Web applications. To enable tracing, set the server property com.sybase.jaguar.server.classloader.debug to true. For information on configuring custom class lists, see Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.
For in-server Java code, you can turn on tracing for the Java garbage collector by setting the com.sybase.jaguar.server.jvm.verboseGC server property to true. The trace output describes how often the garbage collector runs, how long it takes, and what objects are deallocated. For information on the encoding of the output, see the documentation for the JDK version that you are running the server with.
