InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.19: Administering the product messages, logs, and traces (overview) >
6.6.19.0: Properties for tracing, logging, and messages >
6.6.19.0.3: Server trace properties

6.6.19.0.3: Server trace properties

These are settings for tracing the internal components of the application server.

Trace Output File
The file to which to log trace events. Note that serious events are always logged to the standard output stream and to the specified trace file. On an administrative server, the property is called traceOutput.

Specify one of these values:

  • stderr
  • stdout
  • filename (or Specify)

where filename is a file of your choice. If you do not specify the full path to the file (drive letter and directories), the file will be created in the working directory of the application server, as specified by the properties of the application server.

  For an application server, the literals stderr and stdout refer files named stderr.txt and stdout.txt (respectively). For an administrative server, they actually refer to the standard error and standard out streams (such as an error file, or the screen, or so on).

It is recommended you trace to stderr or stdout instead of to a file. Tracing to stderr or stdout is more efficient than tracing to a specified file.

Trace Specification, Trace String
Specifies the application server components to trace.

On an administrative server property is called traceString.

The valid format is:

<comp1>=<type>=[enabled|disabled],...:<comp2>=<type>=[enabled|disabled],...

where:

comp
Specifies the component name. The component can be a class, package, or group of classes or packages.

Specify the full name of the component, or use a wildcard ("*") character. When you terminate a component name with a wild card character, the enable|disable action applies to all components whose names begin with the specified prefix.

For example, if components named "a.b.c.d" and "a.b.c.e" are registered, then specify "a.b.c.d" to trace only the "a.b.c.d" component. Specify "a.b.c.*" to trace both components.

type
Specifies the type of tracing to perform:
  • debug - Provides information for debugging purposes.

  • entry/exit - Indicates that a process has entered or exited a method.

  • event - Indicates that a significant event took place, such as a state change.

  • all - Conducts all three types of tracing.

enabled|disabled
Specifies whether tracing is enabled or disabled for the component. Type either "enabled" or "disabled."

Here is an example of a valid trace specification or traceString. The statement:

com.ibm.ejs.container.*=all=enabled:com.ibm.ejs.jts.*=entry=enabled
enables all tracing on the container and entry/exit tracing on the JTS.
View Log File

To view a log file, select the log file, determine which region of the file to view, and click "Refresh."

The names of particular log files are as configured elsewhere in the server configuration.

Note that it might be extremely slow, or impossible, to load the entire contents of a very large log file.

Go to previous article: Trace Administration properties Go to next article: Administering the product messages, logs, and traces

 

 
Go to previous article: Trace Administration properties Go to next article: Administering the product messages, logs, and traces