TRCE messages
JVMTRCE000E Trace option unrecognized: -Xtrace:%s
Explanation
An option used with the -Xtrace parameter
is not known.
System action
The JVM ends.
User response
Use -Xtrace:help to find the
correct syntax for the -Xtrace option and try
again.
JVMTRCE001E Error processing trace option: -Xtrace:%s
Explanation
An option used with the -Xtrace parameter
could not be processed correctly due to a syntax error.
System action
The JVM ends.
User response
Use -Xtrace:help to find the
correct syntax for the -Xtrace option and try
again.
JVMTRCE002E Error processing trace option: -Xtrace:%s=%s
Explanation
An option used with the -Xtrace parameter
could not be processed correctly due to a problem with the option
or the arguments used.
System action
The JVM ends.
User response
Use -Xtrace:help to find the
correct syntax for the -Xtrace option and try
again.
JVMTRCE003E Error processing trace option, detail: %s
Explanation
An option used with the -Xtrace parameter
could not be processed correctly due to the problem described in the
detail string.
System action
The JVM ends.
User response
Use -Xtrace:help to find the
correct syntax for the -Xtrace option and try
again.
JVMTRCE004W Error opening trace file: %s
Explanation
The specified trace file could not be opened.
System action
The JVM continues but trace data is not written to this file.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be opened.
JVMTRCE005W Error writing header to trace file: %s
Explanation
The specified trace file could not be written to.
System action
The JVM continues but trace data is not written to this file.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be opened.
JVMTRCE006W Error writing %d bytes to trace file: %s rc: %d
Explanation
The specified trace file could not be written to.
System action
The JVM continues but trace data is not written to this file.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be opened.
JVMTRCE007W Error opening next trace file generation: %s
Explanation
The specified trace file could not be opened when the JVM attempted to open the next trace file in a cycle of generational trace files.
System action
The JVM continues but trace data is not written to this file.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be opened.
JVMTRCE008W Error performing seek in tracefile: %s
Explanation
The JVM could not find an expected location in the specified trace file.
System action
The JVM continues but trace data is not written to this file.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be opened.
JVMTRCE009W Error writing to snap file
Explanation
The JVM could not write trace data to a snap file while the JVM was running.
System action
The JVM continues but trace data is not written to this file.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be opened.
JVMTRCE010W Native memory allocation failure, falling back to nodynamic trace settings.
Explanation
The JVM could not allocate space for another trace buffer.
System action
The JVM continues but trace reuses existing buffers. Trace points that are not written to disk before a new buffer is required might be lost.
User response
No action is required. However, to reduce the amount of trace points produced, change the trace options.
JVMTRCE011W Module not configured for trace: %s
Explanation
The JVM could not configure trace for the specified
module, typically due to a native out of memory situation.
System action
The JVM continues but there is no trace data generated
for this module.
User response
Contact your IBM® service
representative. You might need to obtain additional information by
running with -Xtrace:debug=<n>.
JVMTRCE012W Unable to open trace point counter file %s, counters redirected to stderr.
Explanation
The JVM could not open the specified file for the trace point counts at shutdown.
System action
The JVM writes the counter information to stderr at shutdown.
User response
If you need to collect the trace data, restart the JVM specifying a trace file that can be written to.
JVMTRCE013I Writing trace count info to %s
Explanation
The JVM is writing trace counter information to the specified location at shutdown.
System action
The JVM writes the counter information to that location at shutdown.
User response
No action required. This message is for information only.
JVMTRCE014E Trace engine initialization failed, trace not enabled
Explanation
The JVM cannot start the trace engine.
System action
The JVM ends.
User response
Contact your IBM service
representative. You might need to obtain additional information by
running with -Xtrace:debug=<n>.
JVMTRCE015E Error registering trace write subscriber
Explanation
The JVM cannot start the trace subscriber thread that
writes trace buffers to disk.
System action
The JVM continues but trace data is not written to
disk.
User response
Contact your IBM service
representative. You might need to obtain additional information by
running with -Xtrace:debug=<n>.
JVMTRCE016E Storage for RasGlobalStorage not available, trace not enabled
Explanation
The JVM could not be initialized.
System action
The JVM ends.
User response
Contact your IBM service
representative.
JVMTRCE017E Unable to allocate RAS thread local storage key
Explanation
The JVM could not initialize.
System action
The JVM ends.
User response
Contact your IBM service
representative.
JVMTRCE018E Unable to allocate UTE thread local storage key
Explanation
The JVM could not initialize.
System action
The JVM ends.
User response
Contact your IBM service
representative.
JVMTRCE019E Trace engine failed to initialize properly, RC = %d
Explanation
The JVM could not initialize.
System action
The JVM ends.
User response
Contact your IBM service
representative.
JVMTRCE020W Timeout occurred during trace engine termination
Explanation
A timeout occurred during JVM shutdown while the trace engine is waiting for trace
subscriber threads to finish.
System action
The JVM ends without waiting for trace subscriber threads to
finish.
User response
Contact your IBM service representative.