Developer Trace and Log Files
The trace and log messages of the Java Startup Framework contain important information about the status of the Java instance. In case of errors, check and analyze these messages.
The developer trace and log files are located in the /usr/sap/SID/inst_name/work
directory,
where SID
is the system ID of the cluster (for
example, C11
) and inst_name
is
the instance name of the instance (for example, DVEBMGS00
or JC01
).
Structure
The following trace files provide useful information in case of errors.
dev_jstart
This is the trace file of the Java instance controller.
Recommendation
We recommend that you always check the end of this file for error messages regarding the startup of the AS Java instance.
dev_<component name>
The trace file of the corresponding JSTART server process (the <component
name>
can be deployment
, bootstrap
, server<n>
, 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 JSTART
server process (the <component name>
can
be deployment
, bootstrap
, server<n>
,
or icm
).
For example, the output file for the offline deployment process
is std_deployment.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
JSTART server process (the <component name>
can
be deployment
, bootstrap
,
or server<n>
).
For example, the output file for the JVM running the bootstrap
process is jvm_bootstrap.out
.