DUMP messages

Dump agent messages.

JVMDUMP000E Dump option unrecognized: -Xdump:%s

Explanation

An option used with the -Xdump parameter is unknown.

System action

The JVM ends.

User response

Use -Xdump:help to find the correct syntax for the -Xdump options.

JVMDUMP001E Dump event unrecognized: ...%s

Explanation

The event name provided with the -Xdump parameter is unknown.

System action

The JVM ends.

User response

Use -Xdump:events to find the supported set of event names.

JVMDUMP002W Token unrecognized: %%%1$c

Explanation

An unidentified token was found in the dump label.

System action

The JVM ends.

User response

Use -Xdump:tokens to find the supported set of tokens.

JVMDUMP003E Dump agent unrecognized: %s

Explanation

An unsupported dump type has been requested.

System action

The JVM ends.

User response

Use -Xdump:help to find the supported set of dump types.

JVMDUMP004E Missing file name

Explanation

The dump file name could not be found.

System action

The dump cannot be written.

User response

Provide a valid filename for the dump.

JVMDUMP005E Missing external tool

Explanation

The executable file for the tool could not be found.

System action

The tool cannot run.

User response

Provide a valid path and filename for the executable file.

JVMDUMP006I Processing dump event \"%1$s\", detail \"%3$.*2$s\" - please wait.

Explanation

A dump event has occurred and is being handled.

System action

The JVM attempts to process the event.

User response

No response is required.

JVMDUMP007I JVM Requesting %1$s dump using '%2$s'

Explanation

The JVM is about to write a dump. The dump might have been triggered by an event, such as an exception, or requested using JVMTI, JVMRI, -Xtrace:trigger or the com.ibm.jvm.Dump Java API.

System action

The JVM attempts to write the dump. A second message is generated when the dump is complete.

User response

Review the dump and take appropriate action.

JVMDUMP009I %s dump not available

Explanation

The specified dump type is not currently available. For example, a JVM trace snap dump has been requested, but JVM trace is not enabled.

System action

The JVM does not write the dump.

User response

This message is only for information.

JVMDUMP010I %1$s dump written to %2$s

Explanation

The dump was written to the specified location.

System action

The JVM continues.

User response

To understand how to interpret a Java dump file, refer to diagnostic information.

JVMDUMP011I %1$s dump created process %2$d

Explanation

A tool dump process has been created.

System action

The JVM runs the executable process specified for the tool dump. Any parameters are passed to the process.

User response

Refer to the documentation for the tool creating the dump process.

JVMDUMP012E Error in %1$s dump:%2$s

Explanation

The JVM detected an error while attempting to produce a dump.

System action

The JVM continues, but the dump might not be usable.

User response

Refer to diagnostic information or contact your local IBM® service representative.

JVMDUMP013I Processed dump event \"%1$s\", detail "%3$.*2$s".

Explanation

A dump event occurred and has been handled.

System action

The JVM continues.

User response

Refer to other messages issued by the JVM for the location of the dump file, or for other actions required.

JVMDUMP014E VM Action unrecognized: ...%s

Explanation

A specified dump request action was not understood by the JVM.

System action

The JVM produces help information and ends.

User response

Use -Xdump:request to check that your request is valid.

JVMDUMP015I Aborting: Cannot open or read (%s)

Explanation

The JVM cannot open a dump file in read mode.

System action

INTERNAL USE ONLY

User response

INTERNAL USE ONLY

JVMDUMP016I Aborting: Cannot create file (%s)

Explanation

An attempt by the JVM to open a new file has failed.

System action

INTERNAL USE ONLY

User response

INTERNAL USE ONLY

JVMDUMP017I Aborting: Cannot compress file (%s)

Explanation

The JVM cannot compress a file.

System action

INTERNAL USE ONLY

User response

INTERNAL USE ONLY

JVMDUMP018W Requested event is not available: run with -Xdump:dynamic flag

Explanation

A dump has been requested on an event type that is not supported.

System action

INTERNAL USE ONLY

User response

INTERNAL USE ONLY

JVMDUMP019I JVM requesting %s dump

Explanation

A dump file of the type specified has been requested.

System action

The JVM attempts to produce a dump of the specified type.

User response

Wait for a message indicating that the dump is complete.

JVMDUMP020I %s dump has been written

Explanation

A dump file of the type specified has been written.

System action

The JVM continues.

User response

To understand how to interpret the dump file, refer to Java diagnostic information.

JVMDUMP022W The requested heap compaction has not been performed because exclusive access was not requested or could not be obtained.

Explanation

The garbage collector could not run because the gc thread did not have exclusive access to the heap.

System action

The dump file is not produced.

User response

Modify the -Xdump option to request exclusive access. See the Java diagnostic information for valid dump request types.

JVMDUMP023W The requested heap preparation has not been performed because exclusive access was not requested or could not be obtained.

Explanation

The dump thread must lock the heap to prevent changes while the dump is taken. Either no attempt was made to obtain the lock or the lock could not be obtained.

System action

The JVM does not produce the specified dump.

User response

Modify the -Xdump option to request exclusive access. See the Java diagnostic information for valid dump request types.

JVMDUMP024W Multiple heapdumps were requested but %%id is missing from file label:. Dumps will overwrite

Explanation

The JVM replaces the %%id insertion point with a unique number. Because %%id is missing the replacement cannot take place, causing a potential file name clash and file overwrite.

System action

The JVM informs the user and produces dumps as requested.

User response

If you do not want files overwritten, specify a file label that includes the %%id.

JVMDUMP025I IEATDUMP failure for DSN='%s' RC=0x%08X RSN=0x%08X

Explanation

An IEATDUMP was requested but could not be produced.

System action

The JVM will output the message on the operator console.

User response

Check the response code provided in the error using the Diagnostics Guide or the z/OS® V1R7.0 MVS Authorized Assembler Services Reference, 36.1.10 Return and Reason Codes.

JVMDUMP026 IEATDUMP Name exceeding maximum allowed length. Default name used.

Explanation

The file label exceeded the maximum length for file names on z/OS.

System action

The dump file is not produced.

User response

Refer to Java diagnostic information for information about producing dumps on z/OS.

JVMDUMP027W The requested heapdump has not been produced because another component is holding the VM exclusive lock.

Explanation

The exclusive VM lock must be held to produce a usable heapdump. Although the VM exclusive lock was requested by the user, the VM could not obtain the lock in a reasonable time. This behavior avoids risking a deadlock.

System action

The VM does not produce a heapdump.

User response

Wait for 1 minute and try taking the heapdump again when the VM exclusive lock might be free.

JVMDUMP028W The VM exclusive lock could not be acquired before taking the system dump.

Explanation

Although the VM exclusive lock was requested by the user, the VM could not obtain the lock in a reasonable time before taking the system dump. This behavior avoids risking a deadlock.

System action

The VM produces a system dump without taking the VM exclusive lock. The dump might show an inconsistent view of the VM data structures and heap.

User response

Wait for 1 minute and try taking the system dump again when the VM exclusive lock might be free.

JVMDUMP029W The request for prepwalk or compact before taking a system dump will be ignored because the VM exclusive lock was not requested.

Explanation

The user requested the prepwalk or compact options before taking a system dump, but did not request the VM exclusive lock. These actions require the exclusive VM lock.

System action

The system dump is taken without running prepwalk or compact.

User response

Modify the -Xdump:system parameter to include the exclusive request option. For example:
-Xdump:system:events=user,request=exclusive+
compact+prepwalk

JVMDUMP030W Cannot write dump to file %s: %s

Explanation

The JVM was unable to write a dump to the specified file. There might be multiple causes, including insufficient file system permissions or specifying a file path that does not exist.

System action

The JVM uses a default file name. The name and location of the file are indicated by the messages produced when the dump is written.

User response

Correct the problem with the specified file path or change the target dump file with the file= option.

JVMDUMP031W The requested heapdump has not been produced because the VM exclusive lock was not requested. Add request=exclusive+prepwalk+compact to your -Xdump:heap: command line option.

Explanation

A heapdump dump agent was configured using the -Xdump option or JVMTI without requesting that the exclusive VM lock.

System action

The JVM does not take the heapdump because the dump might be corrupted without the VM exclusive lock in place.

User response

Change the -Xdump:heap: option to include the request=exclusive option. For example:
-Xdump:heap:events=user,request=exclusive

JVMDUMP032I JVM requested %1$s dump using '%2$s' in response to an event

Explanation

The JVM writes a dump because an event, such as an exception, was triggered.

System action

The JVM attempts to write the dump. A second message is produced when the dump is complete.

User response

Review the dump and take appropriate action.

JVMDUMP033I JVM requested %1$s dump in response to an event

Explanation

The JVM writes a dump because an event, such as an exception, has been triggered.

System action

The JVM attempts to write the dump. A second message is produced when the dump is complete.

User response

Review the dump and take appropriate action.

JVMDUMP034I User requested %1$s dump using '%2$s' through %3$s

Explanation

The JVM writes a dump in response to a request through an API, such as JVMTI, or through the -Xtrace:trigger option.

System action

The JVM attempts to write the dump. A second message is produced when the dump is complete.

User response

Review the dump and take appropriate action.

JVMDUMP035I User requested %1$s dump through %2$s

Explanation

The JVM writes a dump in response to a user request through an API, such as JVMTI, or through the -Xtrace:trigger option.

System action

The JVM attempts to write the dump. A second message is produced when the dump is complete.

User response

Review the dump and take appropriate action.

JVMDUMP036I Invalid or missing -Xdump filter

Explanation

A valid -Xdump filter must be supplied.

System action

The dump agent is not loaded.

User response

Modify the dump option to include a valid filter.

JVMDUMP037E Error in %1$s dump: %2$s failed, error code: %3$d

Explanation

An error has occurred in a JVM dump agent. An operating system call used by the agent has failed.

System action

The JVM continues.

User response

Check preceding JVM messages. The JVMDUMP007I message includes the command string supplied for tool dumps. Check that the command string is correct.

JVMDUMP038E Snap dump is not written because tracing to file: %1$s

Explanation

Snap dumps are not produced when a trace output file is in use.

System action

The JVM continues.

User response

Use the trace file specified in the message.

JVMDUMP039I Processing dump event \"%1$s\", detail \"%3$.*2$s\" at %4$s - please wait.

Explanation

A dump event is being handled.

System action

The JVM generates dumps as configured for the event by the -Xdump option.

User response

No action is required.

JVMDUMP040I %1$s dump written to dataset(s) using name template %2$s

Explanation

The dump is written using the specified data set name template.

System action

The JVM continues.

User response

Locate the dump data set, or data sets, and take appropriate action.

JVMDUMP041I Incorrect use of -Xdump msg_filter

Explanation

The suboption msg_filter is applicable only to events throw, systhrow, catch, and uncaught.

System action

The dump agent is not loaded.

User response

Modify the dump option to apply the msg_filter suboption to applicable events.

JVMDUMP042W Abort signal received while running on Java stack. The JVM dump agents could not be run.

Explanation

The JVM abort signal handler was called on a thread that is running on a Java stack. The JVM dump agents are not run to avoid further problems.

System action

The JVM ends. The abort signal is passed on to the operating system.

User response

No specific action is required. Look for other messages that are produced to assist you with problem determination. Refer to operating system documentation for information about obtaining dumps on abort signals.

JVMDUMP043E %s not supported on this platform

Explanation

The option that is specified is not supported on the current platform.

System action

The JVM ends.

User response

Remove the option and try again.

JVMDUMP044E Invalid or reserved valid value for %s

Explanation

The value for the option is out of the allowed range or is reserved for other purposes.

System action

The JVM ends.

User response

Select a different value for the option and try again.

JVMDUMP045E The number of dump options must be less than %d, including options set by default.

Explanation

The number of -Xdump: options exceeds the VM limit.

System action

The JVM ends.

User response

Combine dump types, event types, and filters using the '+' symbol into a single option and try again.

JVMDUMP046I VM is shutting down. Reason: %2$.*1$s.

Explanation

User requested to exit

System action

The JVM ends.

User response

This exit was requested by the user.

JVMDUMP047I VM is shutting down. Reason: Unknown.

Explanation

User requested to exit.

System action

The JVM ends.

User response

This exit was requested by the user.

JVMDUMP048I JIT dump method being compiled is an ordinary method.

Explanation

The dump has reported that the method the unhandled exception occurred in is an ordinary method.

System action

The JVM continues.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP049I JIT dump notified all waiting threads of the current method to be compiled.

Explanation

The compilation threads waiting on the method to be compiled monitor will be notified.

System action

The JVM continues.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP050I JIT dump could not allocate a new optimization plan.

Explanation

The dump could not allocate a new optimization plan for recompilation.

System action

The JVM will not recompile the current method and will continue.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP051I %1$s dump occurred in '%2$s' thread 0x%3$p.

Explanation

The dump is reporting which thread caused the unhandled exception.

System action

The JVM continues.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP052I JIT dump recursive crash occurred on diagnostic thread.

Explanation

The dump is reporting a reproduction of the original unhandled exception, with tracing.

System action

The JVM continues.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP053I JIT dump is recompiling %.*s.%.*s%.*s.

Explanation

The dump is recompiling the specified method signature.

System action

The JVM continues.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP054I JIT dump is tracing the IL of the method on the crashed compilation thread.

Explanation

The dump is tracing the IL of the crashed thread in its current state before recompiling the method for tracing.

System action

The JVM continues.

User response

Diagnostic information, provide this information to your service representative.

JVMDUMP055I Processing dump event \"%1$s\", detail \"%3$.*2$s\", exception \"%5$.*4$s\" at %6$s - please wait.

Explanation

A dump event has occurred and is being handled.

System action

The JVM generates dumps as configured for the event by the -Xdump option.

User response

No response is required.

JVMDUMP056I Processed dump event \"%1$s\", detail \"%3$.*2$s\" at %4$s (%5$d.%6$03d seconds).

Explanation

A dump event has occurred and has been handled.

System action

The JVM continues.

User response

Refer to other messages issued by the JVM for the location of the dump file, or for other actions required.