Show TOC Start of Content Area

Object documentation Developer Trace and Log Files  Locate the document in its SAP Library structure

Definition

The trace and log messages of the Java startup and control framework contain important information about the startup process. In case of errors or misbehavior it will be helpful if you check and analyze them.

The developer trace and log files are located in the /usr/sap/<SID>/<INSTANCE NAME>/work directory, where <SID> is the system ID of the cluster (for example, C11) and <INSTANCE NAME> is the instance name of the J2EE instance (for example, JC01). In case of a Java-only installation, the instance name consists of a prefix (JC or J) and the two-digit instance number afterwards.

Structure

dev_jcontrol

The trace file of the JControl process.

JControl is responsible for starting, stopping and controlling the processes of the J2EE instance.

Use the dev_jcontrol trace file when you have problems starting or stopping the whole J2EE instance.

Note

We recommend that you always check the end of this file for error messages regarding the startup of JControl.

dev_<component name>

The trace file of the corresponding JLaunch process (the <component name> can be bootstrap, bootstrap_<cluster_element_ID>, dispatcher, server<n>, sdm, jcmon, or icm). For example, the trace file for the bootstrap process is dev_bootstrap.

std_<component name>.out

The standard and error output file of the corresponding JLaunch process (the <component name> can be bootstrap, bootstrap_<cluster_element_ID>, dispatcher, server<n>, sdm, or icm). For example, the output file for the bootstrap process is std_bootstrap.out. Output and error messages from the Java VM are written to this file.

jvm_<component name>.out

The standard and error output file of the JVM running the corresponding JLaunch process (the <component name> can be bootstrap, bootstrap_<cluster_element_ID>, dispatcher, server<n>, sdm, or icm). For example, the output file for the JVM running the bootstrap process is jvm_bootstrap.out.

 

For more information in case of errors, see the Trace and Log Files Error Messages.

 

See also:

Incrementing/Decrementing the Trace Level

Creating a Stack Trace

 

End of Content Area