IBM SDK, Java Technology Edition Version 1
IBM VM messages
IBM
Note Before you use this information and the product it supports, read the information in “Notices” on page 89.
Copyright information This edition of the IBM® VM messages guide applies to the IBM SDK and Runtime Environment, Java™ Technology Edition, for all versions, releases, modifications, and fix packs, unless otherwise indicated. Portions © Copyright 1997, 2020, Oracle and/or its affiliates. © Copyright International Business Machines Corporation 2011, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents
Preface...... v
Chapter 1. IBM VM messages...... 1 CDRT messages...... 1 DUMP messages...... 2 EXEL messages...... 7 EXEX messages...... 8 J9CL messages...... 9 J9GC messages...... 10 J9RI messages...... 14 J9TI messages...... 16 J9VM messages...... 19 JITM messages...... 29 JNCK messages...... 31 MECK messages...... 33 OFFC messages...... 34 PORT messages...... 36 SHRC messages...... 39 TRCE messages...... 81 VERB messages...... 84 VMUT messages...... 86 ZIPS messages...... 87
Notices...... 89 Trademarks...... 90 Terms and conditions for product documentation...... 90 IBM Online Privacy Statement...... 91
iii iv Preface
This guide lists messages that are generated by the IBM Java Virtual Machine (JVM).
© Copyright IBM Corp. 2011, 2020 v vi IBM SDK, Java Technology Edition: IBM VM messages Chapter 1. IBM VM messages
The Java virtual machine (VM) that is used by the IBM Software Developers Kit (SDK) is the Eclipse OpenJ9 VM. Messages are issued by the VM in response to certain conditions. These messages, error codes, and exit codes apply to multiple versions of the SDK. There are three main types of message: Information Information messages provide information about VM processing. For example, a dump information message is typically issued when a dump agent requests a Java dump. Warning Warning messages are issued by the VM to indicate conditions that might need user intervention. Error Error messages are issued by the VM when normal processing cannot proceed, because of unexpected conditions. VM messages have the following format: JVMTYPENUM&, where: • JVM is a standard prefix. • TYPE refers to the VM subcomponent that issued the message. • NUM is a numerical number. • & is one of the following codes: – I Information message – W Warning message – E Error message VM messages can help you with problem determination. Refer to diagnostic information for more detailed information about diagnosing problems with the Eclipse OpenJ9 VM.
CDRT messages Codert module messages. JVMCDRT000E Unable to locate JIT stack map - System action: aborting VM The JVM ends. Explanation: User response: JIT metadata could not be found when traversing Java Contact your IBM service representative. stacks. JVMCDRT002E Failing PC: %1$p (offset %2$p), System action: metaData = %3$p The JVM ends. Explanation: User response: JIT metadata could not be found when traversing Java Contact your IBM service representative. stacks. JVMCDRT001E Method: %2$.*1$s.%4$.*3$s System action: %6$.*5$s (%7$p) The JVM ends. Explanation: User response: JIT metadata could not be found when traversing Java Contact your IBM service representative. stacks.
© Copyright IBM Corp. 2011, 2020 1 DUMP messages Dump agent messages. JVMDUMP000E Dump option unrecognized: - Explanation: Xdump:%s The executable file for the tool could not be found. Explanation: System action: An option used with the -Xdump parameter is The tool cannot run. unknown. User response: System action: Provide a valid path and filename for the executable The JVM ends. file. User response: JVMDUMP006I Processing dump event \"%1$s\", Use -Xdump:help to find the correct syntax for the - detail \"%3$.*2$s\" - please Xdump options. wait. JVMDUMP001E Dump event unrecognized: ...%s Explanation: A dump event has occurred and is being handled. Explanation: The event name provided with the -Xdump parameter System action: is unknown. The JVM attempts to process the event. System action: User response: The JVM ends. No response is required. User response: JVMDUMP007I JVM Requesting %1$s dump using Use -Xdump:events to find the supported set of '%2$s' event names. Explanation: JVMDUMP002 Token unrecognized: %%%1$c The JVM is about to write a dump. The dump might W have been triggered by an event, such as an exception, or requested using JVMTI, JVMRI, -Xtrace:trigger Explanation: or the com.ibm.jvm.Dump Java API. An unidentified token was found in the dump label. System action: System action: The JVM attempts to write the dump. A second The JVM ends. message is generated when the dump is complete. User response: User response: Use -Xdump:tokens to find the supported set of Review the dump and take appropriate action. tokens. JVMDUMP009I %s dump not available JVMDUMP003E Dump agent unrecognized: %s Explanation: Explanation: The specified dump type is not currently available. For An unsupported dump type has been requested. example, a JVM trace snap dump has been requested, System action: but JVM trace is not enabled. The JVM ends. System action: User response: The JVM does not write the dump. Use -Xdump:help to find the supported set of dump User response: types. This message is only for information. JVMDUMP004E Missing file name JVMDUMP010I %1$s dump written to %2$s Explanation: Explanation: The dump file name could not be found. The dump was written to the specified location. System action: System action: The dump cannot be written. The JVM continues. User response: User response: Provide a valid filename for the dump. To understand how to interpret a Java dump file, refer JVMDUMP005E Missing external tool to diagnostic information.
2 IBM SDK, Java Technology Edition: IBM VM messages JVMDUMP011I %1$s dump created process %2$d System action: INTERNAL USE ONLY Explanation: A tool dump process has been created. User response: INTERNAL USE ONLY System action: The JVM runs the executable process specified for the JVMDUMP017I Aborting: Cannot compress file tool dump. Any parameters are passed to the process. (%s) User response: Explanation: Refer to the documentation for the tool creating the The JVM cannot compress a file. dump process. System action: JVMDUMP012E Error in %1$s dump:%2$s INTERNAL USE ONLY Explanation: User response: The JVM detected an error while attempting to INTERNAL USE ONLY produce a dump. JVMDUMP018 Requested event is not available: System action: W run with -Xdump:dynamic flag The JVM continues, but the dump might not be usable. Explanation: User response: A dump has been requested on an event type that is Refer to diagnostic information or contact your local not supported. IBM service representative. System action: JVMDUMP013I Processed dump event \"%1$s\", INTERNAL USE ONLY detail "%3$.*2$s". User response: Explanation: INTERNAL USE ONLY A dump event occurred and has been handled. JVMDUMP019I JVM requesting %s dump System action: Explanation: The JVM continues. A dump file of the type specified has been requested. User response: System action: Refer to other messages issued by the JVM for the The JVM attempts to produce a dump of the specified location of the dump file, or for other actions required. type. JVMDUMP014E VM Action unrecognized: ...%s User response: Explanation: Wait for a message indicating that the dump is A specified dump request action was not understood complete. by the JVM. JVMDUMP020I %s dump has been written System action: Explanation: The JVM produces help information and ends. A dump file of the type specified has been written. User response: System action: Use -Xdump:request to check that your request is The JVM continues. valid. User response: JVMDUMP015I Aborting: Cannot open or read To understand how to interpret the dump file, refer to (%s) Java diagnostic information. Explanation: JVMDUMP022 The requested heap compaction The JVM cannot open a dump file in read mode. W has not been performed because System action: exclusive access was not INTERNAL USE ONLY requested or could not be obtained. User response: INTERNAL USE ONLY Explanation: The garbage collector could not run because the gc JVMDUMP016I Aborting: Cannot create file (%s) thread did not have exclusive access to the heap. Explanation: System action: An attempt by the JVM to open a new file has failed. The dump file is not produced.
Chapter 1. IBM VM messages 3 User response: Explanation: Modify the -Xdump option to request exclusive access. The file label exceeded the maximum length for file See the Java diagnostic information for valid dump names on z/OS. request types. System action: JVMDUMP023 The requested heap preparation The dump file is not produced. W has not been performed because User response: exclusive access was not Refer to Java diagnostic information for information requested or could not be about producing dumps on z/OS. obtained. JVMDUMP027 The requested heapdump has not Explanation: W been produced because another The dump thread must lock the heap to prevent component is holding the VM changes while the dump is taken. Either no attempt exclusive lock. was made to obtain the lock or the lock could not be obtained. Explanation: The exclusive VM lock must be held to produce a System action: usable heapdump. Although the VM exclusive lock was The JVM does not produce the specified dump. requested by the user, the VM could not obtain the User response: lock in a reasonable time. This behavior avoids risking Modify the -Xdump option to request exclusive access. a deadlock. See the Java diagnostic information for valid dump System action: request types. The VM does not produce a heapdump. JVMDUMP024 Multiple heapdumps were User response: W requested but %%id is missing Wait for 1 minute and try taking the heapdump again from file label:. Dumps will when the VM exclusive lock might be free. overwrite JVMDUMP028 The VM exclusive lock could not be Explanation: W acquired before taking the system The JVM replaces the %%id insertion point with a dump. unique number. Because %%id is missing the replacement cannot take place, causing a potential file Explanation: name clash and file overwrite. Although the VM exclusive lock was requested by the user, the VM could not obtain the lock in a reasonable System action: time before taking the system dump. This behavior The JVM informs the user and produces dumps as avoids risking a deadlock. requested. System action: User response: The VM produces a system dump without taking the If you do not want files overwritten, specify a file label VM exclusive lock. The dump might show an that includes the %%id. inconsistent view of the VM data structures and heap. JVMDMP025I IEATDUMP failure for DSN='%s' User response: RC=0x%08X RSN=0x%08X Wait for 1 minute and try taking the system dump Explanation: again when the VM exclusive lock might be free. An IEATDUMP was requested but could not be JVMDUMP029 The request for prepwalk or produced. W compact before taking a system System action: dump will be ignored because the The JVM will output the message on the operator VM exclusive lock was not console. requested. User response: Explanation: Check the response code provided in the error using The user requested the prepwalk or compact options the Diagnostics Guide or the z/OS® V1R7.0 MVS™ before taking a system dump, but did not request the Authorized Assembler Services Reference, 36.1.10 VM exclusive lock. These actions require the exclusive Return and Reason Codes. VM lock. JVMDUMP026 IEATDUMP Name exceeding System action: maximum allowed length. Default The system dump is taken without running prepwalk name used. or compact.
4 IBM SDK, Java Technology Edition: IBM VM messages User response JVMDUMP033I JVM requested %1$s dump in Modify the -Xdump:system parameter to include the response to an event exclusive request option. For example: Explanation: -Xdump:system:events=user,request=exclusive+ The JVM writes a dump because an event, such as an compact+prepwalk exception, has been triggered.
JVMDUMP030 Cannot write dump to file %s: %s System action: W The JVM attempts to write the dump. A second message is produced when the dump is complete. Explanation: The JVM was unable to write a dump to the specified User response: file. There might be multiple causes, including Review the dump and take appropriate action. insufficient file system permissions or specifying a file JVMDUMP034I User requested %1$s dump using path that does not exist. '%2$s' through %3$s System action: Explanation: The JVM uses a default file name. The name and The JVM writes a dump in response to a request location of the file are indicated by the messages through an API, such as JVMTI, or through the - produced when the dump is written. Xtrace:trigger option. User response: System action: Correct the problem with the specified file path or The JVM attempts to write the dump. A second change the target dump file with the file= option. message is produced when the dump is complete. JVMDUMP031 The requested heapdump has not User response: W been produced because the VM Review the dump and take appropriate action. exclusive lock was not requested. Add request=exclusive JVMDUMP035I User requested %1$s dump +prepwalk+compact to your - through %2$s Xdump:heap: command line Explanation: option. The JVM writes a dump in response to a user request Explanation: through an API, such as JVMTI, or through the - A heapdump dump agent was configured using the - Xtrace:trigger option. Xdump option or JVMTI without requesting that the System action: exclusive VM lock. The JVM attempts to write the dump. A second System action: message is produced when the dump is complete. The JVM does not take the heapdump because the User response: dump might be corrupted without the VM exclusive Review the dump and take appropriate action. lock in place. JVMDUMP036I Invalid or missing -Xdump filter User response Explanation: Change the -Xdump:heap: option to include the A valid -Xdump filter must be supplied. request=exclusive option. For example: System action: -Xdump:heap:events=user,request=exclusive The dump agent is not loaded. User response: JVMDUMP032I JVM requested %1$s dump using Modify the dump option to include a valid filter. '%2$s' in response to an event JVMDUMP037E Error in %1$s dump: %2$s failed, Explanation: error code: %3$d The JVM writes a dump because an event, such as an exception, was triggered. Explanation: An error has occurred in a JVM dump agent. An System action: operating system call used by the agent has failed. The JVM attempts to write the dump. A second message is produced when the dump is complete. System action: The JVM continues. User response: Review the dump and take appropriate action. User response:
Chapter 1. IBM VM messages 5 Check preceding JVM messages. The JVMDUMP007I Explanation: message includes the command string supplied for The JVM abort signal handler was called on a thread tool dumps. Check that the command string is correct. that is running on a Java stack. The JVM dump agents are not run to avoid further problems. JVMDUMP038E Snap dump is not written because tracing to file: %1$s System action: The JVM ends. The abort signal is passed on to the Explanation: operating system. Snap dumps are not produced when a trace output file is in use. User response: No specific action is required. Look for other messages System action: that are produced to assist you with problem The JVM continues. determination. Refer to operating system User response: documentation for information about obtaining dumps Use the trace file specified in the message. on abort signals. JVMDUMP039I Processing dump event \"%1$s\", JVMDUMP043E %s not supported on this platform detail \"%3$.*2$s\" at %4$s - Explanation: please wait. The option that is specified is not supported on the Explanation: current platform. A dump event is being handled. System action: System action: The JVM ends. The JVM generates dumps as configured for the event User response: by the -Xdump option. Remove the option and try again. User response: JVMDUMP044E Invalid or reserved valid value for No action is required. %s JVMDUMP040I %1$s dump written to dataset(s) Explanation: using name template %2$s The value for the option is out of the allowed range or Explanation: is reserved for other purposes. The dump is written using the specified data set name System action: template. The JVM ends. System action: User response: The JVM continues. Select a different value for the option and try again. User response: JVMDUMP045E The number of dump options must Locate the dump data set, or data sets, and take be less than %d, including options appropriate action. set by default. JVMDUMP041I Incorrect use of -Xdump Explanation: msg_filter The number of -Xdump: options exceeds the VM limit. Explanation: System action: The suboption msg_filter is applicable only to The JVM ends. events throw, systhrow, catch, and uncaught. User response: System action: Combine dump types, event types, and filters using The dump agent is not loaded. the '+' symbol into a single option and try again. User response: Modify the dump option to apply the msg_filter suboption to applicable events. JVMDUMP042 Abort signal received while W running on Java stack. The JVM dump agents could not be run.
6 IBM SDK, Java Technology Edition: IBM VM messages EXEL messages EXE library messages. JVMEXEL058E Internal VM error: Out of memory JVMEXEL063E Class %s does not implement main() Explanation: There is not enough virtual memory to satisfy a Explanation: memory allocation request. The main() method is not found. System action: System action: The JVM ends. The JVM ends. User response: User response: Contact your IBM Service representative. Ensure that the target class implements the main() method. JVMEXEL059E Internal VM error: Failed to find class java/lang/String JVMEXEL064E The method main must be declared public, static and void. Explanation: The java/lang/String class is not found in the Explanation: class path. The main() method should always be public, static, and void. System action: The JVM ends. System action: The JVM ends. User response: Contact your IBM Service representative. User response: Ensure that the main() method is declared correctly. JVMEXEL060E Internal VM error: Failed to create byte array for class name %s JVMEXEL065E Internal VM error: Failed to create argument array Explanation: Byte array creation failed. Explanation: An internal JVM error occurred. System action: The JVM ends. System action: The JVM ends. User response: Contact your IBM Service representative. User response: Contact your IBM Service representative. JVMEXEL061E Internal VM error: Failed to create java/lang/String for class name JVMEXEL066E Internal VM error: Failed to create %s byte array for argument %s Explanation: Explanation: Creation of java/lang/String failed. An internal JVM error occurred. System action: System action: The JVM ends. The JVM ends. User response: User response: Contact your IBM Service representative. Contact your IBM Service representative. JVMEXEL062E Internal VM error: Out of memory JVMEXEL067E Internal VM error: Failed to create converting string to UTF java/lang/String for argument %s characters for class name %s Explanation: Explanation: An internal JVM error occurred. The amount of available memory is too low to perform System action: the conversion. The JVM ends. System action: User response: The JVM ends. Contact your IBM Service representative. User response: JVMEXEL068E Internal VM error: Failed to set Contact your IBM Service representative. array element for %s
Chapter 1. IBM VM messages 7 Explanation: Ensure that the target file is accessible. An internal JVM error occurred. JVMEXEL084W Unable to make a backup copy of System action: file: %s The JVM ends. Explanation: User response: The JVM failed to back up the file. Contact your IBM Service representative. System action: JVMEXEL074E Unable to redirect console to: The JVM continues without backing up the file. %1$s:%2$d User response: Explanation: Ensure that the target file has the correct access Failed to establish a socket connection to the target permission. remote console. JVMEXEL085W WARNING: The command line System action: argument "%s" has been The JVM console output is not redirected to the target deprecated. WARNING: Use "-jxe console.
EXEX messages JVM EXE messages JVMEXEX010E %s requires a parameter Explanation: The Java virtual machine could not be created. Explanation: The specified command-line option requires a System action: parameter. The JVM ends. System action: User response: The JVM ends. Inspect previous JVM messages for the error details. User response: JVMEXEX014I Run %s -help for usage Add the required parameter to the JVM command-line Explanation: option. You used an invalid command-line option. JVMEXEX012E -jar option is not available for this System action: class library The JVM ends. Explanation: User response: This JVM does not support the -jar command-line Run the JVM with the -help command-line option. option. JVMEXEX015E VM startup error: Out of memory System action: The JVM ends. Explanation: The JVM ran out of memory during the startup User response: sequence. Remove the -jar command-line option or use a different JVM. System action: The JVM ends. JVMEXEX013E Internal VM error: Failed to create Java VM User response:
8 IBM SDK, Java Technology Edition: IBM VM messages Contact your IBM service representative. JVMEXEX023E Could not initialize JXE utilities. JVMEXEX016E Invalid jxespace parameters. Explanation: Explanation: The JVM failed to initialize the JXE utilities library. The parameters supplied to the -jxespace option Some of the JVM files might be corrupt. were not valid. System action: System action: The JVM ends. The JVM ends. User response: User response: Reinstall the JVM from a package that you know to be Use different parameters for the -jxespace option. valid. JVMEXEX017E Error mapping jxe in flash JVMEXEX024E JXE %s did not contain a startup class. Explanation: The JVM failed to map the memory space specified by Explanation: the -jxespace option. The specified JXE file did not contain a startup class. System action: System action: The JVM ends. The JVM ends. User response: User response: Use different parameters for the -jxespace option. Recompile the JXE with a startup class.
J9CL messages IBM virtual machine Class library messages. JVMJ9CL000E Incompatible class library User response: Ensure that the class library is compatible with the Explanation: JVM. The class library .jar file is not compatible with the class library native code. JVMJ9CL003E Incompatible class library version: JCL %1$x, VM %2$x System action: The JVM fails to start. Explanation: The class library is not from the same release as the User response: JVM. Ensure that the vm.jar file has the same version as the JVM. System action: The JVM fails to start. JVMJ9CL001I Try running with -jcl:%s User response: Explanation: Ensure that the JVM and the class libraries are from The class library .jar file is not compatible with the the same release. class library native code or the JVM. JVMJ9CL004E Incompatible class library version: System action: expected JCL v%1$i, found v%2$i The JVM fails to start. Explanation: User response: The class library is not from the same release as the Ensure that the class library native code and the JVM JVM. are compatible with the specified class library .jar file. System action: The JVM fails to start. JVMJ9CL002I Classes are from a non-J9 library, or an incorrectly reduced JXE User response: Ensure that the JVM and the class libraries are from Explanation: the same release. The class library .jar file is not compatible with this virtual machine. JVMJ9CL005E Incompatible class library version: requires VM v%1$i, found v%2$i System action: The JVM fails to start. Explanation:
Chapter 1. IBM VM messages 9 The class library is not from the same release as the System action: JVM. The JVM attempts to start. System action: User response: The JVM fails to start. Contact your IBM Service representative. User response: JVMJ9CL033W Could not register %s as bootstrap Ensure that the JVM and the class libraries are from library. Error code = %zu the same release. Explanation: JVMJ9CL031W Could not register dbgwrapper.dll The file indicated by the message could not be loaded. as bootstrap library. Error code = System action: %zu The JVM attempts to start. Explanation: User response: The file dbgwrapper.dll could not be loaded. Contact your IBM Service representative.
J9GC messages Garbage collector messages. JVMJ9GC017E %1$s too small, must be at least User response: %2$zu %3$sbytes Adjust the garbage collector options. Explanation: JVMJ9GC021E %1$s must equal %2$s The value for the specified option is smaller than the Explanation: minimum permitted value. If both of these options are specified together, the System action: values must be the same. The JVM ends. System action: User response: The JVM ends. Use a larger value for the specified option. User response: JVMJ9GC018E %1$s too small for %2$s Update the garbage collector options. Explanation: JVMJ9GC022E Sum of %1$s and %2$s too large The value for the specified option is smaller than the for %3$s minimum permitted value. Explanation: System action: The sum of the values specified for these options is The JVM ends. larger than the maximum permitted value. User response: System action: Adjust your garbage collector options. The JVM ends. JVMJ9GC019E %1$s too large for %2$s User response: Adjust the garbage collector options. Explanation: The value for the specified option is larger than the JVMJ9GC023E Sum of %1$s and %2$s must maximum permitted value. equal %3$s System action: Explanation: The JVM ends. The sum of the values specified for these options is not equal to the third option. User response: Adjust your garbage collector options. System action: The JVM ends. JVMJ9GC020E %s too large for heap User response: Explanation: Adjust the garbage collector options. The value for the specified option is larger than the maximum permitted value. JVMJ9GC024E Sum of %1$s and %2$s too large for heap System action: The JVM ends. Explanation:
10 IBM SDK, Java Technology Edition: IBM VM messages The sum of the values specified for these options is JVMJ9GC032E System configuration does not larger than the maximum permitted value. support option '%s' System action: Explanation: The JVM ends. The specified option is not supported by the current User response: hardware or operating system configuration. Adjust the garbage collector options. System action: JVMJ9GC027E Malformed option: '%s' The JVM ends. Explanation: User response: The option could not be parsed. Remove the option or adjust your hardware or operating system configuration. System action: The JVM ends. JVMJ9GC033E %1$s value must be between %2$.2f and %3$.2f (inclusive) User response: Check the garbage collector options and correct any Explanation: errors before trying again. The value specified for this option is not within the permitted range. JVMJ9GC028E Option too large: '%s' System action: Explanation: The JVM ends. The value specified for this option is larger than the maximum permitted value. User response: Adjust the garbage collector options. System action: The JVM ends. JVMJ9GC034E %1$s value must be between %2$zu and %3$zu (inclusive) User response: Adjust the garbage collector options. Explanation: The value specified for this option is not within the JVMJ9GC029E Option error: '%s' permitted range. Explanation: System action: This option is not valid. The JVM ends. System action: User response: The JVM ends. Adjust the garbage collector options. User response: JVMJ9GC035E %s must be followed by a number Check the garbage collector options and correct any errors before trying again. Explanation: The option specified must be directly followed by a JVMJ9GC030E %1$s value of %2$.2f must be at numeric value. least %3$s less than %4$s value System action: of %5$.2f The JVM ends. Explanation: The values specified for these options are too close. User response: Adjust the garbage collector options. For example, System action: instead of "-Xmx 100m", use "-Xmx100m". The JVM ends. JVMJ9GC036E %1$s value must be above %2$zu User response: Adjust the garbage collector options. Explanation: The value specified for the option is too small. JVMJ9GC031E %1$s and %2$s cannot both be System action: specified The JVM ends. Explanation: You cannot specify both of these options together. User response: Use a larger value for the garbage collector option and System action: try again. The JVM ends. JVMJ9GC038E %s value specified is too large User response: Remove one of the options and try again. Explanation:
Chapter 1. IBM VM messages 11 The value specified for the option is too large. The JVM uses the default large page size instead of the size you specified. System action: The JVM ends. User response: If the default large page size is not appropriate, update User response: the garbage collector options with a supported page Use a smaller value for this garbage collector option size. and try again. JVMJ9GC057E %1$s must be no greater than JVMJ9GC039E %1$s is deprecated; use %2$s %2$s instead Explanation: Explanation: The first option cannot be used because the value The option is deprecated and no longer supported. specified must not be greater than the value of the System action: second option. The JVM ends. System action: User response: The JVM ends. Replace the deprecated option and try again. User response: JVMJ9GC040E Unknown option: %s Adjust the garbage collector options. Explanation: JVMJ9GC059E -Xgcpolicy:metronome is not The option is not recognized. allowed without -Xrealtime System action: Explanation: The JVM ends. The metronome garbage collection policy requires the -Xrealtime option, but this option was not specified. User response: Check the garbage collector options and correct any System action: errors before trying again. The JVM ends. JVMJ9GC041E Unknown fvtest type: %s User response: Adjust the garbage collector options. Explanation: The option is not recognized . JVMJ9GC062E %s value must be a power of two System action: Explanation: The JVM ends. The value of the specified option must be a power of 2, for example: 2, 4, 8, 16, and so on. User response: Check the garbage collector options and correct any System action: errors before trying again. The JVM ends. JVMJ9GC042E Sum of %1$s and %2$s too small User response: for %3$s Adjust the garbage collector options. Explanation: JVMJ9GC063E Unable to open file '%s' for writing The sum of the values specified for the options is Explanation: smaller than the minimum permitted value. The specified file could not be opened for writing. System action: System action: The JVM ends. A log file is not produced. User response: User response: Adjust the garbage collector options. Check the permissions on the file system or specify a JVMJ9GC054E Large page size %1$zu%2$s is not location and file name that you have write access to. a supported page size; using JVMJ9GC069E Failed to initialize Finalize thread %3$zu%4$s instead Explanation: Explanation: The finalize thread could not be created. The large page size specified is not supported by the operating system. A further message is issued System action: detailing the supported page sizes. The JVM ends. System action: User response:
12 IBM SDK, Java Technology Edition: IBM VM messages Check that the system has enough native memory to User response: run the JVM. Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJ9GC070E Failed to startup the Garbage Collector JVMJ9GC075E An error occurred in parsing '-Xlp' option Explanation: The Garbage Collector failed to start. Explanation: An error occurred when parsing the -Xlp option. System action: The JVM ends. System action: The JVM ends. User response: Check that the system has enough native memory to User response: run the JVM. Correct the -Xlp option and try again. JVMJ9GC071E Value for '%s' is not correct JVMJ9GC076E System configuration does not support requested %1$zu%2$s Explanation: large page size The value that is specified for the option is not correct. Explanation: System action: The large page size that is specified is not supported The JVM ends. by the operating system. User response: System action: Correct the option and try again. The JVM ends. JVMJ9GC072I Large page size %1$zu%2$s is not User response: a supported page size; using Adjust the -Xlp option to specify a page size that is %3$zu%4$s %5$s instead supported by the operating system. Explanation: JVMJ9GC077E System configuration does not The specified page size is not supported by the support requested %1$zu%2$s operating system. A suitable page size is used instead. %3$s large page size System action: Explanation: The JVM is started with a different page size. The large page size that is specified is not supported User response: by the operating system. Adjust the -Xlp option to specify a page size that is System action: supported by the operating system. The JVM ends. JVMJ9GC073I Large page size %1$zu%2$s %3$s User response: is not a supported page size; using Adjust the -Xlp option to specify a page size that is %4$zu%5$s instead supported by the operating system. Explanation: JVMJ9GC078E '%1$s' is not specified as the first The specified large page size is not supported by the parameter in '%2$s' option operating system. A suitable page size is used instead. Explanation: System action: A parameter is missing, or the parameters are not in The JVM starts using a different page size. the correct order. User response: System action: Adjust the -Xlp option to specify a page size that is The JVM ends. supported by the operating system. User response: JVMJ9GC074I Large page size %1$zu%2$s %3$s Correct the -Xlp parameters and try again. is not a supported page size; using %4$zu%5$s %6$s instead JVMJ9GC079E '%1$s' option is not complete, must specify '%2$s' parameter. Explanation: The specified large page size is not supported by the Explanation: operating system. A suitable page size is used instead. The option is missing one or more parameters. System action: System action: The JVM starts using a different page size. The JVM ends.
Chapter 1. IBM VM messages 13 User response: command line option - Specify all the required parameter for the -Xlp option Xgc:overrideHiresTimerCheck and try again. Explanation: JVMJ9GC080E System configuration does not The operating system returned a clock resolution that support parameter '%.*s' in option is larger than requested. However, the JVM continues '-Xlp' to start because the option - Xgc:overrideHiresTimerCheck is requested. Explanation: The parameter that is used with the -Xlp option is not System action: recognized. The JVM starts, but garbage collection pause time management remains subject to operating system System action: performance, which might not provide adequate timer The JVM ends. resolution. User response: User response: Remove or correct the parameter and try again. Use this option with caution, and only when you are JVMJ9GC081I Extra comma characters are unable to use a supported operating system. discovered in '-Xlp' option - JVMJ9GC088I Requested objectheap page size ignored %1$zu%2$s could not be Explanation: satisfied; using %3$zu%4$s The -Xlp option contains comma characters that are instead not needed. Explanation: System action: The requested object heap page size is supported by The JVM ignores the extra characters. the operating system, but is not currently available. User response: System action: Remove the extra commas from the -Xlp option. The JVM starts with a different object heap page size, instead of the specified size. JVMJ9GC082I Requested for %1$s page size %2$zu%3$s%4$s is not a User response: supported page size; using %5$zu No action is required. %6$s%7$s instead JVMJ9GC089W The -Xgc:preferredHeapBase Explanation: option is not supported on z/OS. The specified page size is not supported by the Explanation: operating system. A suitable page size is used instead. The JVM was started with the - System action: Xgc:preferredHeapBase option, which has no The JVM starts using a different page size. effect on z/OS. User response: System action: Adjust the -Xlp or -Xgc options to specify page size The JVM ignores the -Xgc:preferredHeapBase that is supported by the operating system. option. JVMJ9GC084I OS clock resolution claims to not User response: support the requested target For a list of supported options, refer to the IBM SDK pause time. Overriding due to documentation.
J9RI messages JVMRI interface messages. JVMJ9RI000E jvmri->CreateThread cannot The thread is not created. Error code JNI_ERR is allocate thread arguments returned. memory User response: Explanation: Investigate process memory usage and try again. The JVM could not allocate the memory required to JVMJ9RI002E jvmri->DumpRegister called with process a JVMRI CreateThread call. NULL callback, function not System action: registered.
14 IBM SDK, Java Technology Edition: IBM VM messages Explanation: User response: The JVM could not process a JVMRI DumpRegister Investigate process memory usage and try again. call because the supplied callback function parameter JVMJ9RI010E jvmri->GetRasInfo unable to was null. allocate memory. System action: Explanation: A callback function is not registered. Error code The JVM could not allocate the memory required to JNI_EINVAL is returned. process a JVMRI GetRasInfo call. User response: System action: Correct the JVMRI DumpRegister call by providing a None. Error code JNI_ENOMEM is returned. callback function parameter. User response: JVMJ9RI003E Can't allocate dump agent in Investigate process memory usage and try again. jvmri->DumpRegister, function not registered. JVMJ9RI011E RasInfo structure has unsupported type field. Explanation: The JVM could not allocate the memory required to Explanation: process a JVMRI DumpRegister call. The RasInfo structure that was supplied as a parameter to a JVMRI GetRasInfo call had a request System action: type that is not valid. A callback function is not registered. Error code JNI_ERR is returned. System action: None. Error code JNI_EINVAL is returned. User response: Investigate process memory usage and try again. User response: Correct the request type in the supplied RasInfo JVMJ9RI005E jvmri->GetComponentDataArea structure and try again. component %s does not have dataArea under this vm. JVMJ9RI012E jvmri->ReleaseRasInfo called with NULL RasInfo structure. Explanation: The JVMRI GetComponentDataArea call is not Explanation: supported by this JVM. The JVM could not process a JVMRI ReleaseRasInfo call because the supplied System action: info_ptr parameter was null. Error code JNI_ERR is returned. System action: User response: None. Error code JNI_EINVAL is returned. Remove the JVMRI GetComponentDataArea call from the JVMRI agent code. User response: Correct the JVMRI ReleaseRasInfo call by providing JVMJ9RI006E jvmri->GetRasInfo called with a valid pointer as the info_ptr parameter. NULL RasInfo structure. JVMJ9RI013E jvmri->ReleaseRasInfo: structure Explanation: has unsupported type field. The JVM could not process a JVMRI GetRasInfo call because the supplied info_ptr parameter was null. Explanation: The RasInfo structure that was supplied as a System action: parameter to a JVMRI ReleaseRasInfo call had a Error code JNI_EINVAL is returned. request type that is not valid. User response: System action: Correct the JVMRI GetRasInfo call by providing a None. Error code JNI_EINVAL is returned. valid pointer as the info_ptr parameter. User response: JVMJ9RI007E jvmri->GetRasInfo unable to Correct the request type in the supplied RasInfo allocate memory. structure and try again. Explanation: JVMJ9RI016E jvmri->SetOutOfMemoryHook The JVM could not allocate the memory required to called with NULL callback, process a JVMRI GetRasInfo call. function not registered. System action: Explanation: Error code JNI_ENOMEM is returned.
Chapter 1. IBM VM messages 15 The JVM could not process a JVMRI User response: SetOutOfMemoryHook call because the supplied Investigate process memory usage and try again. callback function parameter was null. JVMJ9RI021E jvmri->RunDumpRoutine not System action: supported. A callback function is not registered. Error code Explanation: JNI_EINVAL is returned. The JVMRI RunDumpRoutine call is not supported by User response: this JVM. Correct the JVMRI SetOutOfMemoryHook call by System action: providing a callback function parameter. None. Error code JNI_ERR is returned. JVMJ9RI017E Can't allocate dump agent in User response: jvmri->SetOutOfMemoryHook, Remove the JVMRI RunDumpRoutine call from the function not registered. JVMRI agent code. Explanation: JVMJ9RI022E initialise JVMRI unable to allocate The JVM could not allocate the memory required to jvmri dump monitor process a JVMRI SetOutOfMemoryHook call. Explanation: System action: The JVM failed to initialize the JVMRI interface A callback function is not registered. Error code because the JVM was unable to allocate a monitor. JNI_ERR is returned. System action: User response: The JVM ends. Investigate process memory usage and try again. User response: JVMJ9RI018I jvmri->NotifySignal raising signal Investigate process memory usage and try again. %d. JVMJ9RI023E jvmri->TraceRegister, jvmri- Explanation: >TraceDeregister and The JVM is about to raise a signal as requested by a TraceListener no longer JVMRI NotifySignal call. supported, use new versions in System action: JVMRAS_VERSION_1_5 The JVM raises the requested signal. Explanation: User response: The JVMRI TraceRegister and TraceDeregister This message is an information message. No action is calls are not supported by this JVM. required. System action: JVMJ9RI020E jvmri->CreateThread unable to The trace listener is not registered or unregistered. allocate private monitor Error code JNI_ERR is returned. Explanation: User response: A call to the JVMRI CreateThread function failed Change the JVMRI agent code to use the JVMRI because the JVM was unable to allocate a monitor. TraceRegister50 and TraceDeregister50 calls instead. System action: The thread is not created. Error code JNI_ERR is returned.
J9TI messages JVMTI interface messages. JVMJ9TI000E Out of memory attempting to load Increase the amount of available native memory. agent library %s JVMJ9TI001E Agent library %1$s could not be Explanation: opened (%2$s) The system ran out of native memory. Explanation: System action: The agent shared library could not be found or opened. The JVM fails to load the agent library, then ends. System action: User response: The JVM fails to load the agent library, then ends.
16 IBM SDK, Java Technology Edition: IBM VM messages User response: Explanation: Verify the existence of the agent shared library, and An internationalized description of a JVMTI extension. check that the file read permissions allow access. System action: JVMJ9TI002E Agent_OnLoad not found in library None. %s User response: Explanation: None. The specified agent does not follow the JVMTI JVMJ9TI011I Add a dynamic -Xtrace option specification. Explanation: System action: An internationalized description of a JVMTI extension. The JVM fails to load the agent library, then ends. System action: User response: None. Add an Agent_OnLoad function to the agent library. User response: JVMJ9TI003E Agent_OnLoad failed for library %s None. Explanation: JVMJ9TI012I Add a dynamic -Xdump option The initialization of the agent failed in the Agent_OnLoad function. Explanation: An internationalized description of a JVMTI extension. System action: The JVM fails to load the agent library, then ends. System action: None. User response: Correct the Agent_OnLoad failure. User response: None. JVMJ9TI004I Returns via the capabilities_ptr the extended capabilities JVMJ9TI014I Controls Java Lock Monitor (JLM) available at this time. (COM_IBM_JLM_START, COM_IBM_JLM_START_TIME_STA Explanation: MP, COM_IBM_JLM_STOP, An internationalized description of a JVMTI extension. COM_IBM_JLM_STOP_TIME_STAM System action: P). None. Explanation: User response: An internationalized description of a JVMTI extension. None. System action: JVMJ9TI005I Add the new extended capabilities None. from capabilities_ptr. User response: Explanation: None. An internationalized description of a JVMTI extension. JVMJ9TI015I Request a Java Lock Monitor (JLM) System action: dump. None. Explanation: User response: An internationalized description of a JVMTI extension. None. System action: JVMJ9TI006I Relinquish the extended None. capabilities from capabilities_ptr. User response: Explanation: None. An internationalized description of a JVMTI extension. JVMJ9TI016I Allow inlining in the presence of System action: method enter and exit events None. (resulting in possibly inaccurate reporting of enter and exit) User response: None. Explanation: An internationalized description of a JVMTI extension. JVMJ9TI007I Get the current set of extended capabilities via capabilities_ptr. System action:
Chapter 1. IBM VM messages 17 None. An internationalized description of a JVMTI extension. User response: System action: None. None. JVMJ9TI017I Controls various VM and compiling User response: options. None. Explanation: JVMJ9TI025I Allow direct JNI in the presence of An internationalized description of a JVMTI extension. method enter and exit events (resulting in possibly inaccurate System action: reporting of enter and exit) None. Explanation: User response: An internationalized description of a JVMTI extension. None. System action: JVMJ9TI018I Sets a method for selective entry None. and exit notification. User response: Explanation: None. An internationalized description of a JVMTI extension. JVMJ9TI026I Trigger a dump using the given System action: RAS configuration. None. Explanation: User response: An internationalized description of a JVMTI extension. None. System action: JVMJ9TI019I Sets notification mode for None. extended events, allowing thread- level selectivity User response: None. Explanation: An internationalized description of a JVMTI extension. JVMJ9TI030I Signal the async event on a single thread or all threads System action: None. Explanation: An internationalized description of a JVMTI extension. User response: None. System action: None. JVMJ9TI020I Gets the OS thread ID from a jthread User response: None. Explanation: An internationalized description of a JVMTI extension. JVMJ9TI031I Cancel the async event on a single thread or all threads System action: None. Explanation: An internationalized description of a JVMTI extension. User response: None. System action: None. JVMJ9TI021I Get extended frame information User response: Explanation: None. An internationalized description of a JVMTI extension. JVMJ9TI070E Agent initialization function %s System action: failed for library %s, return code None. %d User response: Explanation: None. Agent_OnLoad or Agent_OnAttach failed to JVMJ9TI022I Get extended frame information initialize the agent. for all stack traces. System action: Explanation: The JVM fails to load the agent library and ends.
18 IBM SDK, Java Technology Edition: IBM VM messages User response: System action: The agent library must be updated to correct the agent The JVM fails to load the agent library and ends. initialization failure. User response: JVMJ9TI071E Agent initialization function %s The agent library must be updated to add the missing not found in library %s initialization function. Explanation: The specified agent library does not correctly follow the JVMTI specification.
J9VM messages General JVM messages. JVMJ9VM000E Malformed value for on other libraries. This message is produced when a IBM_JAVA_OPTIONS library cannot be loaded. Explanation: System action: The JVM has found an error when parsing the The JVM ends environment variable IBM_JAVA_OPTIONS. This User response: problem can be caused by syntax errors such as Check your system to ensure that the libraries unmatched quotes. indicated are available and accessible. If this problem System action: occurs with an application that has run successfully The JVM ends. before, check for any recent changes to your environment. Contact your IBM service representative User response: if the problem continues. Check the syntax of the environment variable IBM_JAVA_OPTIONS JVMJ9VM005E Invalid value for environment variable: %s JVMJ9VM002E Options file not found Explanation: Explanation: The value entered for the environment variable is not The file specified using the option -Xoptionsfile cannot valid. be found. System action: System action: The JVM ends. The JVM ends. User response: User response: Correct the value for the environment variable and try Correct the command line option for -Xoptionsfile and again. try again. JVMJ9VM006E Invalid command-line option: %s JVMJ9VM003 JIT compiler "%s" not found. Will W use interpreter. Explanation: The command-line option is not valid. Explanation: The value specified for the -Djava.compiler option is System action: not valid. The JVM ends. System action: User response: The JVM continues without a compiler. The Correct or remove the command-line option and try performance might be slower. again. User response: JVMJ9VM007E Command-line option Correct the value for -Djava.compiler and try again. unrecognised: %s JVMJ9VM004E Cannot load library required by: Explanation: %s The command-line option is not recognized. Explanation: System action: JVM initialization uses system services to load The JVM ends. numerous libraries, including libraries that are User response: specified by the user. Libraries can have dependencies
Chapter 1. IBM VM messages 19 Correct or remove the command-line option and try System action: again. The JVM continues. JVMJ9VM008E J9VMDllMain not found User response: Contact your IBM service representative if the problem Explanation: continues. J9VMDllMain is the main module entry point for system libraries. If J9VMDllMain is not found the JVMJ9VM013 Initialization error in function module cannot be used. W %1$s(%2$d): %3$s System action: Explanation: The JVM ends. This is typically an internal error within the JVM. User response: System action: Contact your IBM service representative. The JVM continues but might end later if the error occurred in a critical area. JVMJ9VM009E J9VMDllMain failed User response: Explanation: Contact your IBM service representative if the problem J9VMDllMain is the main module entry point for continues. system libraries. There has been a failure using J9VMDllMain. JVMJ9VM014 Shutdown error in function W %1$s(%2$d): %3$s System action: The JVM ends. Explanation: An internal error occurred during shutdown User response: processing. Further information about the error is Contact your IBM service representative. provided. JVMJ9VM010 Failed to initialize %s System action: W The JVM continues. Explanation: User response: The identified library cannot be initialized. This Contact your IBM service representative if the problem message is typically associated with JVMPI function. continues. System action: JVMJ9VM015 Initialization error for library The JVM continues but the function might be affected. W %1$s(%2$d): %3$s User response: Explanation: Contact your IBM service representative. A problem occurred when the JVM tried to initialize JVMJ9VM011 Unable to load %1$s: %2$s the library. This can happen when the JVM is started W with incorrect options, giving rise to additional messages. Explanation: The JVM failed to load the library named in the first System action: parameter. The second parameter gives further The JVM ends. information about the failure. User response: System action: Check preceding messages for an indication of the The JVM continues but might end later if the library problem. Correct the problem and try again. contained core JVM function. JVMJ9VM016 Shutdown error for library User response: W %1$s(%2$d): %3$s Check the libraries are available and can be accessed. Explanation: Contact your IBM service representative if the problem An internal error occurred during shutdown continues. processing. Further information about the error is JVMJ9VM012 Unable to unload %1$s: %2$s provided. W System action: Explanation: The JVM continues. The JVM failed to unload the library named in the first User response: parameter. The second parameter gives further Contact your IBMM service representative if the information about the failure. problem continues.
20 IBM SDK, Java Technology Edition: IBM VM messages JVMJ9VM017E Could not allocate memory for System action: command line option array The JVM ends with exit code 600 or 601. Explanation: User response: During JVM initialization the command line options are Contact your IBM Service representative. stored in memory. There was not enough memory JVMJ9VM023I This may indicate that available for the JVM to complete the process. JAVA_HOME is incorrect, or that System action: class libraries are not installed The JVM ends. Explanation: User response: A required class could not be found or could not be This is unlikely to be a problem caused by starting the initialized. The value set for JAVA_HOME might be JVM. Check your system for hardware or software incorrect, or the class library might not be installed faults and correct them. Restart your system and try correctly. again. Contact your IBM service representative if the System action: problem continues. The JVM ends. JVMJ9VM018E Could not allocate memory for User response: shared library load table pool Check that the JAVA_HOME environment variable is Explanation: properly set. This error is issued when memory cannot be allocated JVMJ9VM031E Required class %2$.*1$s must be to expand an internal table. This is unlikely to be a in the boot classpath, but was problem caused by the JVM. found in the application class path System action: in %4$.*3$s The JVM continues but is likely to fail. Explanation: User response: A required class was found on the application class Check your system for hardware or software faults and path, not on the boot classpath. For security reasons correct them. Restart your system and try again. this class must be found on the boot classpath. Contact your IBM service representative if the problem System action: continues. The JVM ends. JVMJ9VM019E Fatal error: Unable to find and User response: initialize required class %.*s Check your command line options to ensure that you Explanation: have not placed boot classes on the application A required class could not be found or could not be classpath. initialized. JVMJ9VM034E JVMRI requires trace engine: run System action: with -Xtrace flag The JVM ends. Explanation: User response: Tracing must be enabled to use the JVMRI Contact your IBM service representative. environment requested. JVMJ9VM020I Searched in %.*s System action: The JVMRI environment is not returned with the Explanation: GetEnv() JNI function. This message lists a class path entry that was searched while trying to find a required class. User response: Add the appropriate -Xtrace option to the command System action: line. The JVM ends. JVMJ9VM035E Unable to allocate User response: OutOfMemoryError Contact your IBM service representative. Explanation: JVMJ9VM022E Stack map failed, result = %p - The JVM tried to issue an OutOfMemoryError but aborting VM failed. Explanation: System action: An internal error occurred. The JVM ends.
Chapter 1. IBM VM messages 21 User response: System action: Exceeding the maximum value for the -Xmca and - The JVM ignores the -Xscminaot command-line Xmco options causes this error. Check your use of option and continues. these options, the memory usage of your application User response: and try again (possibly using the -Xmx option on Determine if -Xscminaot should be removed, or if - startup). If the problem persists then contact your IBM Xshareclasses should be added. service representative. JVMJ9VM059I -Xscmaxaot is ignored if - JVMJ9VM038E -Xthr: unrecognized option --> Xshareclasses is not specified \'%s\' Explanation: Explanation: The command-line option -Xscmaxaot is not The value specified for the -Xthr option was not meaningful unless -Xshareclasses is specified. recognized. System action: System action: The JVM ignores the -Xscmaxaot command-line The JVM ends. option and continues. User response: User response: Correct or remove the -Xthr option and try again. Determine if -Xscmaxaot should be removed, or if - JVMJ9VM039I -Xscmx is ignored if - Xshareclasses should be added. Xshareclasses is not specified JVMJ9VM061 insertDumpAgent requires %s Explanation: W The -Xscmx option is not meaningful unless shared Explanation: class support is active. An internal VM function called via the JVMTI System action: SetVmDump() API has failed because the required DLL The JVM continues. has not been loaded. User response: System action: Remove the -Xscmx option or activate shared classes The dump options are not changed, JNI_ERR is by using the -Xshareclasses option. returned. JVMJ9VM050E -Xjni: unrecognized option --> User response: \'%s\' Check whether the JVM dump functions have been disabled via the -Xdump:none option. Explanation: The option specified with the -Xjni command-line JVMJ9VM062 removeDumpAgent requires %s parameter is not recognized. W System action: Explanation: The JVM ends. An internal VM function called via the JVMTI SetVmDump() API has failed because the required DLL User response: has not been loaded. Correct the option specified with -Xjni. System action: JVMJ9VM053E Malformed option %s found in - The dump options are not changed, JNI_ERR is Xoptionsfile returned. Explanation: User response: The options file contains an option that is not correctly Check whether the JVM dump functions have been specified. disabled via the -Xdump:none option. System action: JVMJ9VM063 seekDumpAgent requires %s The JVM ends. W User response: Explanation: Correct the option in the options file. An internal VM function called via the JVMTI JVMJ9VM058I -Xscminaot is ignored if - SetVmDump() API has failed because the required DLL Xshareclasses is not specified has not been loaded. Explanation: System action: The command-line option -Xscminaot is not The dump options are not changed, JNI_ERR is meaningful unless -Xshareclasses is specified. returned.
22 IBM SDK, Java Technology Edition: IBM VM messages User response: JVMJ9VM079 triggerOneOffDump(%1$s) Check whether the JVM dump functions have been W requires %2$s disabled via the -Xdump:none option. Explanation: JVMJ9VM064 setDumpOption requires %s An internal JVM function, called by the JVMTI W TriggerVmDump() API, failed because the required Explanation: DLL is not loaded. An internal JVM function, called by the JVMTI System action: SetVmDump() API, has failed because the required The requested dump is not triggered. JNI_ERR is DLL is not loaded. returned. System action: User response: The dump options are not changed. JNI_ERR is Check whether the JVM dump functions have been returned. turned off with the -Xdump:none option. User response: JVMJ9VM080 queryVmDump requires %s Check whether the JVM dump functions have been W turned off with the -Xdump:none option. Explanation: JVMJ9VM067 -Xshareclasses not enabled, - An internal VM function, called by the JVMTI W Xzero:sharezip option ignored QueryVmDump() API, failed because the required DLL is not loaded. Explanation: The -Xzero:sharezip option is ignored if shared System action: classes are not enabled. An empty list of dump option specifications is returned. System action: The JVM ignores the -Xzero:sharezip option. User response: Check whether the JVM dump functions have been User response: turned off with the -Xdump:none option. This warning message can be ignored if you do not want to use the -Xzero:sharezip option. If you do JVMJ9VM081 Malformed option value, option want to use the -Xzero:sharezip option, enable W "%1$s%3$.*2$s" contains trailing shared classes. characters "%4$s" which have JVMJ9VM068 -Xshareclasses not enabled, - been ignored W Xzero:sharestring option ignored Explanation: Explanation: The command-line option contained extra characters The -Xzero:sharestring option is ignored if shared that were ignored. These extra characters might have classes are not enabled. been intended to be other command-line options. System action: System action: The JVM ignores the -Xzero:sharestring option. The JVM ignores the extra characters. User response: User response: This warning message can be ignored if you do not Correct the command-line option and try again. want to use the -Xzero:sharestring option. If you JVMJ9VM082E Unable to switch to IFA processor do want to use the -Xzero:sharestring option, - issue "extattr +a libj9ifa%s.so" enable shared classes. Explanation: JVMJ9VM078E Malformed value for The JVM failed to switch to an IFA (Integrated Facility JAVA_TOOL_OPTIONS for Applications) processor because the JVM library Explanation: file libj9ifa%s.so requires APF authorization. An option found in the environment variable System action: JAVA_TOOLS_OPTIONS is not specified correctly. The JVM continues but prevents further attempts to System action: switch between IFA and standard processors. The JVM ends. User response: User response: Set extended attributes for the libj9ifa%s.so file Correct the option in the environment variable using the command extattr +a. JAVA_TOOLS_OPTIONS.
Chapter 1. IBM VM messages 23 JVMJ9VM083 Error switching to IFA processor Dump options are not reset. JNI_ERR is returned. W rc: %08x User response: Explanation: Check whether the JVM dump functions have been The JVM failed to switch to an IFA (Integrated Facility turned off with the -Xdump:none option. for Applications) processor. The return code indicates JVMJ9VM090I Slow response to network query the error condition. (%d secs), check your IP DNS System action: configuration The JVM continues but prevents further attempts to Explanation: switch between IFA and standard processors. A network query used by the JVM to populate User response: diagnostic data took longer than expected. Contact your IBM service representative for further System action: information. The JVM continues but the diagnostic data is not JVMJ9VM084 IFA Error: unexpected return code available. W %08x from IFA switch service User response: Explanation: Check your IP DNS configuration. For example, on AIX® The JVM failed to switch to an IFA (Integrated Facility and UNIX systems, check the file /etc/ for Applications) processor. The return code indicates resolv.conf. the error condition. JVMJ9VM091I Adaptive spinning supported System action: Explanation: The JVM continues but prevents further attempts to This information message is shown when - switch between IFA and standard processors. Xthr:what is used on the command line. User response: System action: Contact your IBM service representative for further The JVM prints this information message when - information. Xthr:what is used on the command line and adaptive JVMJ9VM085 Malformed option: '%s' spinning is enabled. W User response: Explanation: No action is required. The specified option cannot not be parsed. JVMJ9VM092I Adaptive spinning not supported System action: Explanation: The JVM ignores the option and continues. The JVM optimization, adaptive spinning, is not User response: enabled. This information message is shown when the Correct the command-line option. option -Xthr:what is specified on the command line. JVMJ9VM086 Option too large: '%s' System action: W The JVM continues. Explanation: User response: The specified option is larger than the maximum No action is required. permitted value. JVMJ9VM093E This version of Java requires a System action: CPU that supports SSE2 or later The JVM ignores the option and continues. extensions. See the 'Supported Environments' information in the User response: IBM Java User Guide for more Adjust the command-line option. details. JVMJ9VM087 resetDumpOption requires %s Explanation: W The processor does not support the SSE2 instruction Explanation: set. An internal JVM function, called by the JVMTI System action: ResetVmDump() API, failed because the required DLL The JVM ends. is not loaded. User response: System action:
24 IBM SDK, Java Technology Edition: IBM VM messages Run this version of Java on a system that supports JVMJ9VM111E Invalid lockword option SSE2 or later extensions. For more details, see the specified:%s Supported Environments information in the IBM SDK for Java User Guide. Explanation: This option used with -Xlockword: is not valid. JVMJ9VM094I Thread "%s" is still alive after running the shutdown hooks. System action: The JVM ends. Explanation: The JVM cannot shut down because a thread is still User response: alive. Use a supported -Xlockword option and start the JVM again. System action: DestroyJavaVM() returns JNI_ERR. JVMJ9VM117I -Xitsn is ignored if - Xshareclasses is not specified User response: Add a shutdown hook to end the thread when the JVM Explanation: shuts down. -Xitsn is valid only when shared classes are enabled. JVMJ9VM096I -Xscdmx is ignored if - System action: Xshareclasses is not specified The JVM continues and ignores the -Xitsn option. Explanation: User response: Enable shared classes with the -Xshareclasses The option -Xscdmx specifies the size of the class debug area in a shared class cache. If - option, or remove the -Xitsn option. Xshareclasses is not specified, -Xscdmx is ignored. JVMJ9VM120I -Xscminjitdata is ignored if - System action: Xshareclasses is not specified The option -Xscdmx is ignored. Explanation: User response: -Xscminjitdata is valid only for shared classes. This warning message can be ignored if you do not System action: want to use the -Xscdmx option. If you do want to use The JVM continues, but the -Xscminjitdata value is the -Xscdmx option, enable shared classes. ignored. JVMJ9VM109E Unsupported operating system User response: (%s): Windows XP or newer is If you want to specify a value for -Xscminjitdata, required. enable shared classes using the -Xshareclasses Explanation: option. The operating system is too old to run this version of JVMJ9VM121I -Xscmaxjitdata is ignored if - the JVM. Xshareclasses is not specified System action: Explanation: The JVM ends. -Xscmaxjitdata is valid only for shared classes. User response: System action: Run the JVM on a system with a supported operating The JVM ignores the -Xscmaxjitdata option and system. For information about supported hardware continues. and software, see the IBM SDK for Java User guides. User response: JVMJ9VM110E Invalid lockword mode If you want to specify a value for -Xscmaxjitdata, specified:%s enable shared classes using the -Xshareclasses Explanation: option. The mode specified with the option - JVMJ9VM122E Failed to get user32.dll address Xlockword:mode= is not valid. range required for - System action: Xprotectcontiguous. The JVM ends. Explanation: User response: The JVM failed to find the address range of Use a supported value for the mode, and start the JVM user32.dll. again. System action: The JVM ends.
Chapter 1. IBM VM messages 25 User response: The JVM detects an unrecoverable condition and ends Run the JVM without the -Xprotectcontiguous the process using the z/OS specific system call, option. CEE3AB2, which causes an abend. JVMJ9VM123E Attempting to run on a non- System action: supported processor, JVM will The JVM prints the error message and ends the terminate. process. Explanation: User response: The processor is not supported. Check the console and operator console messages. If further assistance is required, contact your IBM System action: Service representative. The JVM ends. JVMJ9VM133 The system core size hard ulimit is User response: W set to %d, system dumps may be See the information about supported environments in truncated. the IBM SDK for Java User Guide to determine the minimum system requirements. Explanation: The JVM started with the -Xcheck:dump option, and JVMJ9VM129E Application resumed execution detected that the core dump file size is limited by the after handling a fatal condition system hard ulimit. and illegally returned to, or called back into, Java System action: The JVM continues. Explanation: After handling an unrecoverable condition, the User response: application continues, illegally returning to, or calling Refer to the IBM SDK documentation. back into Java. JVMJ9VM134 The system fullcore option is set to System action: W FALSE, system dumps may be The JVM prints the error message and ends the truncated. process using the z/OS specific system call, Explanation: CEE3AB2(). The JVM started with the -Xcheck:dump option, and User response: detected that the system fullcore option is set to Change the user condition handler so that the FALSE. application does not continue when there is an System action: unrecoverable condition on a Java thread. The JVM continues. JVMJ9VM130E Application resumed execution User response: after handling a fatal condition Refer to the IBM SDK documentation. and illegally returned to, or called back into, Java (JIT'ed code) JVMJ9VM135 /proc/sys/kernel/core_pattern W setting "%s" specifies that core Explanation: dumps are to be piped to an After handling an unrecoverable condition, the external program. The JVM may be application continues, illegally returning to, or calling unable to locate core dumps and back into Java. rename them. System action: Explanation: The JVM prints the error message and ends the The JVM started on a system with /proc/sys/ process using the z/OS specific system call, kernel/core_pattern set to pipe core dumps to CEE3AB2(). the command specified after the | character. The JVM User response: might be unable to locate core dumps and rename Change the user condition handler so that the them. application does not continue when there is an System action: unrecoverable condition on a Java thread. The JVM continues. Message JVMPORT030W is issued JVMJ9VM131E Terminating process using when a system dump is taken. CEE3AB2() with abend %1$u, User response: reason %2$u, cleanup %3$u. Refer to the product documentation for the IBM SDK, Explanation: Java Technology Edition.
26 IBM SDK, Java Technology Edition: IBM VM messages JVMJ9VM136 /proc/sys/kernel/core_pattern The specified command-line option is not supported. W setting "%s" specifies a format System action: string for renaming core dumps. The JVM fails to start. The JVM may be unable to locate core dumps and rename them. User response: Remove the option from the command line. Explanation: The JVM started on a system with /proc/sys/ JVMJ9VM167E GC optimizations on idle are not kernel/core_pattern set to rename core dumps. supported The JVM might be unable to locate the core dump. Explanation: System action: The JVM idle tuning options are not supported on The JVM continues. some platforms and Garbage Collection (GC) policies. User response: System action: Refer to the product documentation for the IBM SDK, The JVM fails to start. Java Technology Edition. User response: JVMJ9VM138 The -Xdiagnosticscollector option Refer to the documentation for supported platforms W is not supported by this JVM. and GC policies. Explanation: JVMJ9VM170E Attempt to set static final field The JVM started with the - %2$.*1$s.%4$.*3$s from method Xdiagnosticscollector option, which is no longer "%6$.*5$s" that is not
Chapter 1. IBM VM messages 27 JVMJ9VM173E Class %2$.*1$s and its nest host Examine the use of ClassLoaders to determine why %4$.*3$s must have the same a class of the same name is loaded in two different package loaders. Explanation: JVMJ9VM177E Class %2$.*1$s must be able to The class and nest host class were loaded with load its nest host %4$.*3$s. different class loaders. Explanation: System action: The class and nest host class were loaded with The VM throws a java/lang/VerifyError different class loaders. exception. System action: User response: The VM throws a java/lang/IllegalAccessError Load the class and nest host class with the same class error. loader. User response: JVMJ9VM174E Class %2$.*1$s must be claimed Load the class and nest host class with the same class by its nest host %4$.*3$s loader. Explanation: JVMJ9VM178E Module is null. The class was not claimed by its nest host class. Explanation: System action: Incoming module cannot be NULL. The VM throws a java/lang/VerifyError System action: exception. The VM throws a java/lang/ User response: NullPointerExceptions exception. Contact the provider of the class file for a corrected User response: version. You must not pass a NULL module. JVMJ9VM175 Failed to load library %1$s JVMJ9VM179E Module is null. W required by module: %2$s Explanation: Explanation: Incoming module cannot be unnamed. The VM failed to load the library required by the specified module. System action: The VM throws a java/lang/ System action: IllegalArgumentExceptions exception. The JVM continues. User response: User response: You must not pass an unnamed module. No action required if the specified library won't be referenced. JVMJ9VM180E Module name is invalid. JVMJ9VM176E loading constraint violation when Explanation: overriding method Incoming module name is not valid. \"%2$.*1$s.%4$.*3$s%6$.*5$s System action: \" during creation of class The VM throws a java/lang/ \"%18$.*17$s\": loader IllegalArgumentExceptions exception. \"%8$.*7$s@%9$x\" of class \"%11$.*10$s\" and loader User response: \"%13$.*12$s@%14$x\" of class You must not pass a module with an invalid name. \"%16$.*15$s\" have different JVMJ9VM181E Only bootstrap classloader can types for the method signature define module java.base. Explanation: Explanation: A class loading constraint has been violated. The two Non-bootstrap class loaders cannot define the module class loaders have different classes for one of the java.base. class names in the signature. System action: System action: The VM throws a java/lang/ A java/lang/LinkageError error is thrown. LayerInstantiationException exception. User response: User response: You must not define the module java.base.
28 IBM SDK, Java Technology Edition: IBM VM messages JVMJ9VM182E Only bootstrap or platform User response: classloader can define package Contact the provider of the class file for a corrected java or java.* version. Explanation: JVMJ9VM185E bad class %2$.*1$s: classref is A class loader other than bootstrap or platform class not a value type loader cannot define the package java or java.*. Explanation: System action: The class has specified a bytecode operation that can The VM throws a java/lang/ be performed only on a value type, but the supplied LayerInstantiationException exception. classref is not of a value type. User response: System action: You must not define the package java or java.*. The VM throws an IncompatibleClassChangeError error. JVMJ9VM183E Nest member %2$.*1$s must be able to load nest host %4$.*3$s User response: Contact the provider of the class file for a corrected Explanation: version. The nest member class and nest host class were loaded with different class loaders. JVMJ9VM186E bad object type %2$.*1$s: object on stack is not a value type System action: The VM throws an Explanation: IncompatibleClassChangeError error. The class has specified a bytecode operation that can be performed only on a value type but the object on User response: the stack is not a value type. You must load the class and nest host class with the same class loader. System action: The VM throws an JVMJ9VM184E bad class %2$.*1$s: Qtype IncompatibleClassChangeError error. instance field is not a value type User response: Explanation: Contact the provider of the class file for a corrected The class has a field with a q signature, which is not a version. value type. System action: The VM throws an IncompatibleClassChangeError error.
JITM messages JIT compiler messages. JVMJITM000E Unsupported hardware [%d]. System action: The compiler stops generating AOT code. The AOT Explanation: code already stored in the shared class cache The current hardware is not supported by the continues to be used. compiler. User response: System action: Increase the size of the AOT section of the shared The compiler does not generate code for this class cache using the -Xscmaxaot option. hardware. JVMJITM002W Failure storing AOT code in shared User response: class cache. Shared class cache Check the IBM Java documentation for a list of might be corrupted. Ignoring AOT supported hardware. code in shared class cache. JVMJITM001W No more space for AOT code in Explanation: shared class cache. New AOT code An error occurred storing AOT code in the shared class will not be generated. cache. Explanation: System action: The AOT section of the shared class cache is full.
Chapter 1. IBM VM messages 29 The compiler stops generating AOT code. AOT code Explanation: from the shared class cache is not used. The AOT code in the shared class cache was created using a different garbage collection policy. User response: Destroy and re-create the AOT code in the shared System action: class cache using the -Xshareclasses:reset The compiler does not generate AOT code. AOT code option. from the shared class cache is not used. JVMJITM003W Failure during AOT runtime User response: initialization. Ignoring AOT code in Destroy and re-create the AOT code in the shared shared class cache. class cache for the current garbage collection policy using the -Xshareclasses:reset option. Explanation: An error occurred initializing AOT. JVMJITM007W AOT code in shared class cache cannot run with current JVMPI or System action: JVMTI settings. Ignoring AOT code The compiler does not generate AOT code. AOT code in shared class cache. from the shared class cache is not used. Explanation: User response: AOT code cannot be used with JVMPI or JVMTI. If the error occurs again, destroy and re-create the AOT code in the shared class cache using the - System action: Xshareclasses:reset option. The compiler does not generate AOT code. AOT code from the shared class cache is not used. JVMJITM004W AOT code in shared class cache cannot execute on current User response: processor. Ignoring AOT code in To use AOT code, disable JVMTI. JVMPI is replaced by shared class cache. JVMTI in Java 6. Explanation: JVMJITM009E System configuration does not The AOT code in the shared class cache is not support parameter '%.*s' in option compiled for this platform. '-Xlp' System action: Explanation: The compiler does not generate AOT code. AOT code The specified parameter is not recognized for the -Xlp from the shared class cache is not used. option. User response: System action: Destroy and re-create the AOT code in the shared The JVM ends. class cache for the current platform using the - User response: Xshareclasses:reset option. Remove the unrecognized parameter from the -Xlp JVMJITM005W AOT code in the shared class option and try again. cache cannot run on current JVM JVMJITM010E %s must be followed by a number release. Ignoring AOT code in shared class cache. Explanation: The specified option must be followed immediately by Explanation: a number. The AOT code in the shared class cache was created using a different JVM release. System action: The JVM ends. System action: The compiler does not generate AOT code. AOT code User response: from the shared class cache is not used. Adjust the JIT option. For example, replace - Xlp:objectheap:pagesize
30 IBM SDK, Java Technology Edition: IBM VM messages Adjust the JIT options and try again. The JVM starts using the default large page size. JVMJITM012E Value for '%s' is not correct User response: Adjust the -Xlp option to a specify page size that is Explanation: supported by the operating system. The value specified for the option is not correct. JVMJITM016I Large page size %1$zu%2$s is not System action: a supported page size; using The JVM ends. %3$zu%4$s %5$s instead User response: Explanation: Correct the option and try again. The specified page size is not supported by the JVMJITM013E '%1$s' option is not complete, operating system. A suitable page size is used instead. must specify '%2$s' parameter. System action: Explanation: The JVM starts using a different page size. The option specified is not complete. More parameters User response: are required. Adjust the -Xlp option to specify a page size that is System action: supported by the operating system. The JVM ends. JVMJITM017I Large page size %1$zu%2$s %3$s User response: is not a supported page size; using Specify all the required parameters for the -Xlp %4$zu%5$s instead option. Explanation: JVMJITM014I Extra comma characters are The specified large page size is not supported by the discovered in '-Xlp' option - operating system. A suitable page size is used instead. ignored System action: Explanation: The JVM starts using a different page size. The -Xlp option specified contains extra comma User response: characters. Adjust the -Xlp option to specify a page size that is System action: supported by the operating system. The JVM ignores the extra characters and continues. JVMJITM018I Large page size %1$zu%2$s %3$s User response: is not a supported page size; using Remove the extra commas from the -Xlp option for %4$zu%5$s %6$s instead any future invocation. Explanation: JVMJITM015I Large page size %1$zu%2$s is not The specified large page size is not supported by the a supported page size; using operating system. A suitable page size is used instead. %3$zu%4$s instead System action: Explanation: The JVM starts using a different page size. The specified large page size is not supported by the User response: operating system. A default size is used instead. Adjust the -Xlp option to specify a page size that is System action: supported by the operating system.
JNCK messages JNI messages. JVMJNCK000E -Xcheck:jni: unrecognized option User response: --> \'%s\' Correct the -Xcheck:jni command-line option. Explanation: JVMJNCK001I JNI check utility installed. Use - You specified an unrecognized -Xcheck:jni Xcheck:jni:help for usage command-line option. Explanation: System action: The JNI check utility has been installed. The JVM prints usage information for the - System action: Xcheck:jni option and ends. The JVM performs additional checks on JNI calls.
Chapter 1. IBM VM messages 31 User response: The JVM continues. This message is an information message. No action is User response: required. Check and correct the JNI application code. JVMJNCK002E JNI check utility: unable to hook JVMJNCK077E Error detected in event %2$.*1$s.%4$.*3$s%6$.*5$s Explanation: Explanation: Initialization of the JNI check utility failed because it This message provides additional information about was unable to intercept native method calls. the Java class and method that were used in the JNI System action: function identified in a previous error message. The JVM ends. System action: User response: The JVM continues. Contact your IBM service representative. User response: JVMJNCK023E JNI error detected. Continuing... Investigate the previous error message. Explanation: JVMJNCK078 Warning detected in The JNI check utility has detected a recoverable JNI W %2$.*1$s.%4$.*3$s%6$.*5$s error. Explanation: System action: This message provides additional information about The JVM continues. the Java class and method that were used in the JNI function identified in a previous warning message. User response: Investigate the JNI check error that was reported in System action: the previous message. The JVM continues. JVMJNCK024E JNI error detected. Aborting. User response: Investigate the previous warning message. Explanation: The JNI check utility detected an unrecoverable JNI JVMJNCK079I Advice detected in error. %2$.*1$s.%4$.*3$s%6$.*5$s System action: Explanation: The JVM ends. This message provides additional information about the Java class and method that were used in the JNI User response: function identified in a previous advice message. Investigate the JNI check error that was reported in the previous message. System action: The JVM continues. JVMJNCK025I Use -Xcheck:jni:nonfatal to continue running when errors are User response: detected. Investigate the previous advice message. Explanation: JVMJNCK080E Error detected in the outermost The JVM detected a JNI error and ended. You can use frame of an attached thread the -Xcheck:jni:nonfatal parameter to change Explanation: this behaviour. This message provides additional information about System action: the frame context of the JNI function that was The JVM ends. identified in a previous error message. User response: System action: If required, rerun with the -Xcheck:jni:nonfatal The JVM continues. parameter. User response: JVMJNCK062 JNI warning in %s: This function Investigate the previous error messages. W should not be called inside of a JVMJNCK081 Warning detected in the outermost critical section W frame of an attached thread Explanation: Explanation: A JNI function was called within a JNI critical section. System action:
32 IBM SDK, Java Technology Edition: IBM VM messages This message provides additional information about Explanation: the frame context of the JNI function that was This message provides additional information about identified in a previous warning message. the JNI function that was identified in a previous advice message. System action: The JVM continues. System action: The JVM continues. User response: Investigate the previous warning messages. User response: Investigate the previous advice message. JVMJNCK082I Advice detected in the outermost frame of an attached thread JVMJNCK089E Error detected in the handler frame of a JVMPI or JVMTI event Explanation: This message provides additional information about Explanation: the frame context of the JNI function that was This message provides additional information about identified in a previous advice message. the frame context of the JNI function that was identified in a previous error message. System action: The JVM continues. System action: The JVM continues. User response: Investigate the previous advice messages. User response: Investigate the previous error messages. JVMJNCK083E Error detected in JNI_OnLoad of library %.*s JVMJNCK090 Warning detected in handler W frame of a JVMPI or JVMTI event Explanation: This message provides additional information about Explanation: the JNI function that was identified in a previous error This message provides additional information about message. the frame context of the JNI function that was identified in a previous warning message. System action: The JVM continues. System action: The JVM continues. User response: Investigate the previous error message. User response: Investigate the previous warning messages. JVMJNCK084 Warning detected in JNI_OnLoad W of library %.*s JVMJNCK091I Advice detected in handler frame of a JVMPI or JVMTI event Explanation: This message provides additional information about Explanation: the JNI function that was identified in a previous This message provides additional information about warning message. the frame context of the JNI function that was identified in a previous advice message. System action: The JVM continues. System action: The JVM continues. User response: Investigate the previous warning message. User response: Investigate the previous advice messages. JVMJNCK085I Advice detected in JNI_OnLoad of library %.*s
MECK messages Memory checking messages. JVMMECK000E An error occurred initializing the - System action: Xcheck:memory utility The requested memory check is not performed. Explanation: User response: The memory check utility could not locate the required Verify that your Java runtime environment is correctly virtual machine resources. installed.
Chapter 1. IBM VM messages 33 JVMMECK001E Unrecognized -Xcheck:memory Explanation: option: %s The memory check utility could not store information about the source code locations of memory requests. Explanation: The memory check that you requested is not a System action: recognized type. The JVM performs the memory checks without recording memory requestor information. System action: The Java application runs but no memory checks are User response: performed. Check that your system is configured with sufficient memory. User response: Run the JVM with the -Xcheck:memory:help option to list the valid checks. JVMMECK002E An error occurred creating the call site data structure. Call site information will not be displayed
OFFC messages JNI control messages. JVMOFFC000E -Xoffload:sim: unrecognized JVMOFFC003E Offload Simuator: Applying %d option --> \'%s\' microsecond tax to each JNI call. Explanation: Explanation: You specified an invalid option for the - You started the JVM with the -Xoffload:sim:delay Xoffload:sim parameter. option with microseconds specified. System action: System action: The JVM ends. The JVM applies the tax that you specified. User response: User response: Use a valid option for the -Xoffload:sim parameter. This message is for information only. No action is required. JVMOFFC001I Offload simulator utility installed. Use -Xoffload:sim:help for usage JVMOFFC004E Offload Simuator: Delay tax using spin. Explanation: You specified the -Xoffload:sim parameter when Explanation: you started the JVM. You started the JVM with the -Xoffload:sim:delay option, and spinning is used to delay tax. System action: The JVM runs with the -Xoffload:sim parameter System action: options that you supplied. The JVM uses spinning to apply the tax that you specified. User response: This message is for information only. No action is User response: required. This message is for information only. No action is required. JVMOFFC002E Offload Simuator: Applying %d millisecond tax to each JNI call. JVMOFFC005E Offload Simuator: Delay tax using sleep. Explanation: You specified the -Xoffload:sim:delay option Explanation: when you started the JVM. You started the JVM with the -Xoffload:sim:delay option, and sleeping is used to delay tax. System action: The JVM runs, applying the tax that you specified. System action: The JVM uses sleeping to apply the tax that you User response: specified. This message is for information only. No action is required. User response:
34 IBM SDK, Java Technology Edition: IBM VM messages This message is for information only. No action is You started the JVM with the -Xoffload:trace required. option. JVMOFFC007E Offload Simuator: Clock frequency System action: is %llu ticks/second, The JVM performs offload tracing. have_nanosleep=%d User response: Explanation: This message is for information only. No action is You started the JVM with the -Xoffload:sim:delay required. option, which displays the clock frequency and JVMOFFC023E Offload Trace: Tuning Fork logging whether nanosleep is supported. The to %s have_nanosleep value is 0 when nanosleep is supported and nonzero otherwise. Explanation: You specified the -Xoffload:trace:tuningfork System action: option. The JVM displays the clock frequency and whether nanosleep is supported. System action: The JVM logs offload tracing to tuning fork. User response: This message is for information only. No action is User response: required. This message is for information only. No action is required. JVMOFFC008E Offload Simulator: Invalid sleep time, please choose a time >= 1 JVMOFFC024I Offload: JNI Isolation enabled for millisecond. library group {%s}. Explanation: Explanation: You specified an invalid sleep time in the - You started the JVM with the -Xoffload:isolate Xoffload:sim:delay=Xms option. option, specifying one or more libraries. System action: System action: The JVM ends. The native code in the libraries is run in external quarantines. User response: Start the JVM again, specifying a sleep time that is User response: greater than or equal to 1 millisecond. This message is for information only. No action is required. JVMOFFC009E Offload: Fatal error, unable to hook event JVMOFFC025E Offload:Failed to start quarantine controller with url=%s. Explanation: You ran the JVM with the -Xoffload:sim option, and Explanation: the JVM encountered an internal error. Java offload was requested, but the Java process could not connect to the remote process. System action: The JVM ends. System action: The JVM ends. User response: Contact your IBM service representative. User response: Ensure that there are no firewalls or other JVMOFFC010E Unrecognized time units -> %s impediments to communication between the machine Explanation: on which you invoked the Java process and the The value of xx specified in - machine to which it is being offloaded. Then start the Xoffload:sim:delay=Yxx is not a valid time unit. JVM again. System action: JVMOFFC026E Offload:Invalid connection The JVM ends. information for remote isolation. User response: Explanation: Start the JVM again, specifying either ms or µs as the You specified remote isolation on the command line, time units. but the connection information that you supplied is not valid. JVMOFFC022I Offload Trace utility installed. Use -Xoffload:trace:help for usage System action: The JVM ends. Explanation:
Chapter 1. IBM VM messages 35 User response: System action: Correct the connection information that you specified The JVM ends. on the command line, then start the JVM again. User response: JVMOFFC027E Offload:Connection information Contact your IBM service representative. missing for remote isolation. JVMOFFC030E Offload:Could not find local Explanation: natives properties file {%s}. You specified remote isolation on the command line, Explanation: but did not supply connection information. The file specifying the native code that is run locally System action: could not be found. The message includes the location The JVM ends. and name of the expected file. User response: System action: Add the connection information on the command line The JVM ends. then start the JVM again. User response: JVMOFFC028E Offload:Failed to start local Restore the file from a copy of the JVM, then start the quarantine controller. JVM again. Explanation: JVMOFFC031E Offload:Local natives properties An internal error occurred when trying to start the JVM file has invalid format {%s}. in offload mode. Explanation: System action: The content of the file specifying the native code that The JVM ends. is run locally is not valid. The message includes the name of the file from which the content is read. User response: Contact your IBM service representative. System action: The JVM ends. JVMOFFC029E Offload:Failed to create offload manager. User response: Restore the file from a copy of the JVM, then start the Explanation: JVM again. An internal error occurred when trying to start the JVM in offload mode.
PORT messages Port library messages. JVMPORT001E Failed to allocate memory while User response: attempting to write to a file. This message is accompanied by another message that provides more detail. Check that the shared Explanation: library exists. If the library exists, contact your IBM The system was unable to satisfy a memory allocation service representative. request. JVMPORT003E Dependent module %s could not System action: be loaded Subsequent memory allocation attempts are likely to fail, resulting in the termination of the process. Explanation: The named dependent module could not be loaded. User response: Increase the amount of memory available to the System action: process, or contact your IBM service representative. If the module was critical to the JVM, the process ends. JVMPORT002E Unknown error loading shared library User response: If the JVM ends, contact your IBM service Explanation: representative. There was an unknown error loading a shared library. JVMPORT004E Symbol resolution failure System action: The process shuts down. Explanation:
36 IBM SDK, Java Technology Edition: IBM VM messages There was a problem with symbol resolution while The maximum amount of data that can be dumped in a looking for a particular symbol. single IEATDUMP file is 2 GB. For address spaces larger than 2 GB, the z/OS operating system generates System action: multiple dump files. To enable this behavior, the suffix If the symbol was critical to the JVM, the JVM ends, &DS is required in the dump name. The suffix is and more information is provided. replaced with a counter that identifies which part of User response: the dump is in the file. If you do not add the suffix, the If the JVM ends, contact your IBM service JVM appends it to the dump template. representative. System action: JVMPORT015E Unable to resolve shared library The JVM adds .X&DS to the dump template, then references - a prerequisite shared continues to run. library may be missing User response: Explanation: You can ignore this message, and allow the JVM to The operating system could not resolve a shared alter the dump file name, unless the extended dump library reference. A prerequisite shared library might file name is too long. If the file name is too long, the be missing. JVM uses the default dump template instead. Avoid the message by including the &DS suffix in your dump System action: template or by using the default dump template. If the library is critical to the JVM, the process ends. JVMPORT023 IEATDUMP failed because user- User response: W specified dump template was too If the process ends, check that the library exists. If the long. Retrying dump with default library exists, contact your IBM service representative. template. JVMPORT016E Internal Error %i Explanation: Explanation: You specified a dump template, by using the - An internal error occurred while looking for a shared Xdump:system:file= parameter or the library. JAVA_DUMP_TDUMP_PATTERN environment variable. When the system tried to take a dump by using the System action: template, the IEATDUMP routine returned with return If the library is critical to the JVM, the process ends. code 0x8 and reason code 0x22, indicating that the User response: dump failed because the name was too long. If the process ends, check that the library exists. If the System action: library exists, contact your IBM service representative. The JVM tries to take the dump again using the default JVMPORT019 Unable to create directory %s. dump template. W Shared classes will be disabled User response: until this directory is created. Specify a shorter dump template. Note that, on the Explanation: z/OS 64 operating system, the JVM appends .X&DS to You included a directory when you provided the name the user-specified dump template, to enable multi- of the shared classes cache. This directory could not part z/OS dumps (required to store a full 64-bit be created. address space). If the template you specified was close to 44 characters long, the addition of .X&DS System action: might make it too long. If you specified the -Xshareclasses:nonfatal parameter, the JVM continues without using shared JVMPORT024E IEATDUMP failed because we classes. If you did not specify that parameter, the JVM couldn't allocate the dump dataset ends. (likely disk full). User response: Explanation: Contact your IBM service representative. The JVM attempted to take an IEATDUMP, but the dump routine returned with return code 0x8 and JVMPORT022I Appending .X&DS to user- reason code 0x26, indicating that the dump failed specified dump template to enable because the dump data set could not be allocated. multi-part dumps. System action: Explanation: The JVM continues, but fails to create a dump. You specified a dump template, by using the - Xdump:system:file= parameter or the User response: JAVA_DUMP_TDUMP_PATTERN environment variable.
Chapter 1. IBM VM messages 37 The most common cause for this error message is that The normal operation of the JVM is affected, possibly you have run out of space for dump data sets. Check resulting in a failure to load one or more libraries. your available dump storage. User response: JVMPORT025E Invalid lock type for file lock Contact your IBM service representative. operation. lockFlags: %1$d JVMPORT030 %s setting "%s" specifies that the Explanation: W core dump is to be piped to an A file lock operation failed because the value of the external program. Attempting to flag that specifies the lock type was not valid. rename either core or core.%d. System action: Explanation: The normal operation of the JVM is affected, possibly Linux tools such as ABRT and Apport use the resulting in a failure to load one or more libraries. information in the /proc/sys/kernel/ core_pattern file to redirect the core file to an User response: external program, for example to create bug reports. Contact your IBM service representative. System action: JVMPORT026E File specified is a directory The virtual machine looks in the current directory for a Explanation: file called either core or core.process ID, A file-open operation failed when the system depending on the contents of the /proc/sys/ attempted to open a directory as a file. kernel/core_uses_pid file. System action: User response: The normal operation of the JVM is affected, possibly Refer to the documentation for the external program resulting in a failure to load one or more libraries. specified in the /proc/sys/kernel/core_pattern file. User response: Contact your IBM service representative. JVMPORT031E The LE condition %s%i, which corresponds to a software-raised JVMPORT027E mmap failed due to invalid POSIX signal, was received memory protection parameter. Explanation: Explanation: The JVM was instructed at startup to run with The value for the memory protection parameter is not Language Environment® (LE) condition handlers valid. instead of POSIX signal handlers. A LE condition that System action: corresponds to a software-raised POSIX signal was The normal operation of the JVM is affected, possibly received. resulting in a failure to load one or more libraries. System action: User response: The JVM creates a dump containing diagnostic data Contact your IBM service representative. and ends. JVMPORT028E mmap failed due to invalid User response: mapping options. Contact your IBM service representative. Explanation: JVMPORT034 Attempted to attach shared The value for the flag parameter that specifies W memory created in storage mapping options is not valid. protection key %lu, but currently running in key %lu. System action: The normal operation of the JVM is affected, possibly Explanation: resulting in a failure to load one or more libraries. Shared memory could not be opened because the z/OS storage protection key used to create the shared User response: memory is not compatible with the current storage Contact your IBM service representative. protection key. JVMPORT029E Invalid handle. file handle: %1$d. System action: Explanation: None. A file map operation failed because a file handle was User response: not valid. Any problems are reported using a different message. System action: Check for other error messages.
38 IBM SDK, Java Technology Edition: IBM VM messages JVMPORT035E __malloc31 failed to allocate Explanation: buffer on z/OS The executable file could not be opened. Explanation: System action: The __malloc31 process failed to allocate a buffer. The process shuts down. System action: User response: The JVM continues, but hypervisor related information This message is accompanied by another message is not provided. that provides more detail. User response: JVMPORT048E Failed to create system dump Contact your IBM service representative. because a non-regular file \"%s\" exists with the same name as the JVMPORT036E Unexpected return code from expected system dump file CSRSI service on z/OS Explanation: Explanation: The JVM did not produce a system dump because a An unexpected return code is received from the CSRSI non-regular file exists with the same name as the service on z/OS. expected system dump file. The non-regular file might System action: be a directory, symbolic link, pipe, or socket. The JVM continues, but hypervisor related information System action: is not provided. The JVM continues. User response: Contact your IBM service representative. User response JVMPORT038E Malformed value for Check whether the name of a non-regular file in the IBM_JAVA_HYPERVISOR_SETTIN current working directory of the Java application GS clashes with one of the following names or settings: Explanation: • The default system dump file name, which is core or The IBM_JAVA_HYPERVISOR_SETTINGS core.
SHRC messages Shared classes messages. JVMSHRC004E Cannot destroy cache "%s" There are no shared class caches on the system that can be processed by the command requested. Explanation: The shared class cache could not be destroyed. System action: Processing continues. System action: Processing continues. User response: No action is required. User response: Other messages might indicate the reason why the JVMSHRC006I Number of caches expired within cache has not been destroyed. Investigate these last %1$d minutes is %2$d messages. Explanation: JVMSHRC005I No shared class caches available This is an information message. Explanation: System action:
Chapter 1. IBM VM messages 39 Processing continues. JVMSHRC014E Shared cache "%s" semaphore User response: remove failed No action is required. Explanation: JVMSHRC007I Failed to remove shared class The shared class cache cannot be removed because cache "%s" there is a shared semaphore associated with the cache that cannot be removed. Explanation: The shared class cache could not be removed. System action: The JVM ends, unless you have specified the nonfatal System action: option with -Xshareclasses:nonfatal, in which Processing continues. case the JVM continues without using shared classes. User response: User response: Other messages might indicate the reason why the Contact your IBM service representative. cache has not been removed. Investigate these messages. JVMSHRC015E Shared Class Cache Error: Invalid flag JVMSHRC010I Shared cache "%s" is destroyed Explanation: Explanation: An error occurred during shared class processing. The shared class cache has been destroyed as requested. System action: The JVM ends, unless you have specified the nonfatal System action: option with -Xshareclasses:nonfatal, in which A JVM is not created and a failure message is issued, case the JVM continues without using shared classes. as expected. User response: User response: Contact your IBM service representative. No action is required. This is an information message issued when you destroy a shared class cache. JVMSHRC017E Error code: %d Explanation: JVMSHRC012I Cannot remove shared cache "%s" This message shows the error code relating to a error as there are JVMs still attached to that will have been the subject of a previous message. the cache Explanation: System action: The shared class cache cannot be removed because a The JVM ends, unless you have specified the nonfatal process, or processes, are still attached. option with "-Xshareclasses:nonfatal", in which case the JVM continues without using shared classes. System action: The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which Contact your IBM service representative, unless case the JVM continues without using shared classes. previous messages indicate a different response. User response: JVMSHRC018E cannot allocate memory Wait until any processes using the shared class cache Explanation: have ended and then remove it. The system is unable to obtain sufficient memory. JVMSHRC013E Shared cache "%s" memory System action: remove failed The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which The shared class cache cannot be removed because case the JVM continues without using shared classes. there is shared memory associated with the cache that User response: cannot be removed. The system might be low on resources. Try again when System action: the system is more lightly loaded. If the situation The JVM ends, unless you have specified the nonfatal persists, contact your IBM service representative. option with -Xshareclasses:nonfatal, in which JVMSHRC019E request length is too small case the JVM continues without using shared classes. Explanation: User response: The size requested for the shared class cache is too Contact your IBM service representative. small.
40 IBM SDK, Java Technology Edition: IBM VM messages System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: Contact your IBM service representative. Increase the size for the shared class cache using the JVMSHRC024E shared memory detach error -Xscmx parameter or allow it to take the default value by not specifying the -Xscmx option. Explanation: An error has occurred during shared class processing. JVMSHRC020E An error has occurred while opening semaphore System action: The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred during shared class processing. case the JVM continues without using shared classes. Further messages might follow, providing more detail. User response: System action: Contact your IBM service representative. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which JVMSHRC025E error attaching shared memory case the JVM continues without using shared classes. Explanation: User response: An error has occurred during shared class processing. Contact your IBM service representative, unless System action: subsequent messages indicate otherwise. If the cache is damaged, the JVM attempts to re- JVMSHRC021E An unknown error code has been create it. Otherwise the JVM ends, unless you have returned specified the nonfatal option with - Xshareclasses:nonfatal, in which case the JVM Explanation: continues without using shared classes. An error has occurred during shared class processing. This message is followed by details of the numeric User response: error code returned. The system might be low on resources. Try again when the system is more lightly loaded. If the situation System action: persists, contact your IBM service representative. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which JVMSHRC026E Cannot create cache of requested case the JVM continues without using shared classes. size: Please check your SHMMAX and SHMMIN settings User response: Contact your IBM service representative. Explanation: The system cannot create a shared class cache of the JVMSHRC022E Error creating shared memory size requested by the -Xscmx parameter. If -Xscmx is region not specified the default is 16MB. Explanation: System action: An error has occurred during shared class processing. The JVM ends, unless you have specified the nonfatal System action: option with -Xshareclasses:nonfatal, in which The JVM ends, unless you have specified the nonfatal case the JVM continues without using shared classes. option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. Refer to the product documentation for information User response: about shared memory size limits for your operating The system might be low on resources. Try again when system. Restart the JVM with an acceptable shared the system is more lightly loaded. If the situation cache size. persists, contact your IBM service representative. JVMSHRC027E Shared cache name is too long JVMSHRC023E Cache does not exist Explanation: Explanation: The name specified for the shared class cache is too An attempt has been made to open a shared class long for the operating system. cache that does not exist. System action: System action:
Chapter 1. IBM VM messages 41 The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which The value specified for the expire parameter of - case the JVM continues without using shared classes. Xshareclasses is invalid. User response: System action: Specify a shorter name for the shared class cache and The JVM ends, unless you have specified the nonfatal restart the JVM. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC028E Permission Denied User response: Explanation: Correct the value for the expire option and restart The system does not have permission to access a the JVM. The value must be a positive integer. system resource. JVMSHRC058E Cannot allocate memory for System action: ClasspathItem in The JVM ends, unless you have specified the nonfatal shrinit::hookStoreSharedClass option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Explanation: An error has occurred in shared class processing. User response: Check earlier messages to find the resource that System action: cannot be accessed. Only the user who creates the The JVM ends, unless you have specified the nonfatal shared class cache has access to it, unless the - option with -Xshareclasses:nonfatal, in which Xshareclasses:groupAccess option is specified. case the JVM continues without using shared classes. In this case, a user must belong to the same group as User response: the user who created the shared class cache. The system might be low on resources. Try again when JVMSHRC029E Not enough memory left on the the system is more lightly loaded. If the situation system persists, contact your IBM service representative. Explanation: JVMSHRC059E Cannot allocate memory for There is not enough memory available to create the ClasspathItem in shared cache memory or semaphore. A previous shrinit::hookFindSharedClass message indicates the shared cache memory or Explanation: semaphore concerned. An error has occurred in shared class processing. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: The system might be low on resources. Try again when The system might be low on resources. Try again when the system is more lightly loaded. If the situation the system is more lightly loaded. If the situation persists, contact your IBM service representative. persists, contact your IBM service representative. JVMSHRC030E The Shared Class Cache you are JVMSHRC060E Cannot allocate memory for string attaching has invalid header. buffer in Explanation: shrinit::hookFindSharedClass The shared class cache you are trying to use is invalid. Explanation: System action: An error has occurred during shared class processing. If the cache is damaged, the JVM attempts to re- System action: create it. Otherwise the JVM ends, unless you have The JVM ends, unless you have specified the nonfatal specified the nonfatal option with - option with -Xshareclasses:nonfatal, in which Xshareclasses:nonfatal, in which case the JVM case the JVM continues without using shared classes. continues without using shared classes. User response: User response: The system might be low on resources. Try again when Contact your IBM service representative. the system is more lightly loaded. If the situation JVMSHRC057E Wrong parameters for expire persists, contact your IBM service representative. option
42 IBM SDK, Java Technology Edition: IBM VM messages JVMSHRC061E Cache name should not be longer Explanation: than 64 chars. Cache not created. This message confirms that locking of local hashtables for the shared class cache has been disabled as Explanation: requested. The name of the shared class cache specified to the JVM exceeds the maximum length. System action: The JVM continues. System action: The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which No action is required. The message is issued when case the JVM continues without using shared classes. verbose messages are requested. User response: JVMSHRC067I Timestamp checking disabled Change the shared class cache name so that it does Explanation: not exceed the maximum allowed length. This message confirms that shared classes timestamp JVMSHRC063E Cannot allocate memory for checking has been disabled as requested. sharedClassConfig in shrinit System action: Explanation: The JVM continues. An error has occurred during shared class processing. User response: System action: No action is required. The message is issued when The JVM ends, unless you have specified the nonfatal verbose messages are requested. option with -Xshareclasses:nonfatal, in which JVMSHRC068I Local caching of classpaths case the JVM continues without using shared classes. disabled User response: Explanation: The system might be low on resources. Try again when This message indicates that the caching of classpaths the system is more lightly loaded. If the situation in the shared class cache has been disabled as persists, contact your IBM service representative. requested. JVMSHRC064E Failed to create configMonitor in System action: shrinit The JVM continues. Explanation: User response: An error has occurred during shared class processing. No action is required. The message is issued when System action: verbose messages are requested. The JVM ends, unless you have specified the nonfatal JVMSHRC069I Concurrent store contention option with -Xshareclasses:nonfatal, in which reduction disabled case the JVM continues without using shared classes. Explanation: User response: This message confirms that shared classes concurrent This might be due to problems with the operating store contention reduction has been disabled as system. Restart the JVM. If the situation persists, requested. contact your IBM service representative. System action: JVMSHRC065E Cannot allocate pool in shrinit The JVM continues. Explanation: User response: An error has occurred during shared class processing. No action is required. The message is issued when System action: verbose messages are requested. The JVM ends, unless you have specified the nonfatal JVMSHRC070I Incremental updates disabled option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Explanation: This message confirms that shared classes User response: incremental updates have been disabled as requested. The system might be low on resources. Try again when the system is more lightly loaded. If the situation System action: persists, contact your IBM service representative. The JVM continues. JVMSHRC066I Locking of local hashtables User response: disabled No action is required. The message is issued when verbose messages are requested.
Chapter 1. IBM VM messages 43 JVMSHRC071E Command-line option "%s" Explanation: requires sub-option An error has occurred in shared class processing. Explanation: System action: The specified command-line option requires further The JVM ends, unless you have specified the nonfatal information. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. System action: The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which The system might be low on resources. Try again when case the JVM continues without using shared classes. the system is more lightly loaded. If the situation persists, contact your IBM service representative. User response: Update the command-line option and try again. JVMSHRC083E Cannot allocate memory for identifiedClasspaths array in JVMSHRC072E Command-line option "%s" SH_ClasspathManagerImpl2 unrecognized Explanation: Explanation: An error has occurred during shared class processing. The specified command-line option is not recognized. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: The system might be low on resources. Try again when Correct or remove the invalid command-line option the system is more lightly loaded. If the situation and try again. persists, contact your IBM service representative. JVMSHRC077E Failed to create linkedListImpl JVMSHRC084E Cannot allocate memory for linked pool in list item SH_ClasspathManagerImpl2 Explanation: Explanation: An error has occurred during shared class processing. An error has occurred during shared class processing. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: The system might be low on resources. Try again when The system might be low on resources. Try again when the system is more lightly loaded. If the situation the system is more lightly loaded. If the situation persists, contact your IBM service representative. persists, contact your IBM service representative. JVMSHRC086E Cannot enter ClasspathManager JVMSHRC080E Cannot allocate memory for hashtable mutex hashtable entry Explanation: Explanation: An error has occurred during shared class processing. An error has occurred during shared class processing. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: The system might be low on resources. Try again when The system might be low on resources. Try again when the system is more lightly loaded. If the situation the system is more lightly loaded. If the situation persists, contact your IBM service representative. persists, contact your IBM service representative. JVMSHRC087E MarkStale failed during JVMSHRC082E Cannot create identifiedMutex in ClasspathManager::update() SH_ClasspathManagerImpl2 Explanation:
44 IBM SDK, Java Technology Edition: IBM VM messages An error has occurred during shared class processing. User response: Contact your IBM service representative. System action: The JVM ends, unless you have specified the nonfatal JVMSHRC092E ADD failure when reading cache option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error has occurred during shared class processing. User response: System action: Contact your IBM service representative. The JVM ends, unless you have specified the nonfatal JVMSHRC088E Failed to create cache as option with -Xshareclasses:nonfatal, in which ROMImageSegment in case the JVM continues without using shared classes. SH_CacheMap User response: Explanation: Contact your IBM service representative. An error has occurred during shared class processing. JVMSHRC093I Detected unexpected termination System action: of another JVM during update The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which The JVM detected that another JVM ended case the JVM continues without using shared classes. unexpectedly while updating the shared class cache. User response: System action: Contact your IBM service representative. The JVM continues. JVMSHRC089E Cannot create refresh mutex in User response: SH_CacheMap No action required. This message is for information Explanation: only. An error has occurred during shared class processing. JVMSHRC095E Attempts to call markStale on System action: shared cache items have failed The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred during shared class processing. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you have specified the nonfatal The system might be low on resources. Try again when option with -Xshareclasses:nonfatal, in which the system is more lightly loaded. If the situation case the JVM continues without using shared classes. persists, contact your IBM service representative. User response: JVMSHRC090E Failed to get cache mutex in Contact your IBM service representative. SH_CacheMap startup JVMSHRC096I Shared cache "%s" is full. Use - Explanation: Xscmx to set cache size. An error has occurred during shared class processing. Explanation: System action: The named shared class cache is full and no further The JVM ends, unless you have specified the nonfatal classes can be added to it. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. System action: The JVM continues. The named shared cache is still User response: operational and continues to provide increased The system might be low on resources. Try again when performance for loading the classes it contains. the system is more lightly loaded. If the situation However, classes not contained in the cache are persists, contact your IBM service representative. loaded from their source. JVMSHRC091E Read corrupt data for item 0x%p User response: (invalid dataType) To gain the full benefit of shared classes, delete and Explanation: re-create the named cache. Specify a larger shared An error has occurred during shared class processing. class cache size using the -Xscmx parameter. System action: JVMSHRC097E Shared cache "%s" is corrupt. No The cache is marked as corrupt and the JVM new JVMs will be allowed to continues. connect to the cache. Existing
Chapter 1. IBM VM messages 45 JVMs can continue to function, but Warning: your cache may be cannot update the cache. corrupt. Explanation: Explanation: The shared class cache named in the message is An error has occurred while trying to update the damaged. shared class cache. System action: System action: The JVM attempts to re-create the cache before The JVM ends. starting. If the cache cannot be re-created the JVM User response: ends, unless you have specified the nonfatal option Contact your IBM service representative. with -Xshareclasses:nonfatal. JVMSHRC129E Attempt to set readerCount to -1! User response: Remove the shared class cache named in the message Explanation: and restart the JVM. If the situation persists, contact An error has occurred while trying to update the your IBM service representative. shared class cache. JVMSHRC125E Could not allocate memory for System action: string buffer in SH_CacheMap The JVM continues. Explanation: User response: An error has occurred during shared class processing. Contact your IBM service representative. System action: JVMSHRC130E Attempt to allocate while commit The JVM ends, unless you have specified the nonfatal is still pending option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error has occurred while updating the shared class User response: cache. The system might be low on resources. Try again when System action: the system is more lightly loaded. If the situation Processing continues, if possible. persists, contact your IBM service representative. User response: JVMSHRC126E Request made to add too many Contact your IBM service representative. items to ClasspathItem JVMSHRC134E Failed to create pool in Explanation: SH_ROMClassManagerImpl An error has occurred during shared class processing. Explanation: System action: An error has occurred during shared class processing. The JVM continues. System action: User response: The JVM ends, unless you have specified the nonfatal Contact your IBM service representative. option with -Xshareclasses:nonfatal, in which JVMSHRC127E SH_CompositeCache::enterMutex case the JVM continues without using shared classes. failed with return code %d. User response: Warning: your cache may be The system might be low on resources. Try again when corrupt. the system is more lightly loaded. If the situation Explanation: persists, contact your IBM service representative. An error has occurred while trying to update the JVMSHRC137E SAFE MODE: Warning: ROMClass shared class cache. %.*s does not match ROMClass in System action: cache The JVM ends. Explanation: User response: This message is issued when running shared classes in The system might be low on resources. Try again when safe mode and a mismatch in ROMClass bytes is the system is more lightly loaded. If the situation detected. This message will be followed by further persists, contact your IBM service representative. details of the class sizes and details of the mismatched bytes. JVMSHRC128E SH_CompositeCache::exitMutex failed with return code %d. System action: The JVM continues.
46 IBM SDK, Java Technology Edition: IBM VM messages User response: User response: None required. This message is for information only. Contact your IBM service representative. The mismatch in bytes does not mean that an error JVMSHRC157I Unable to allocate %1$d bytes of has occurred, but could indicate, for example, that the shared memory requested. class has changed since originally stored in the cache. Succesfully allocated maximum JVMSHRC147E Character %.*s not valid for cache shared memory permitted (%2$d name bytes). (To increase available shared memory, modify system Explanation: SHMMAX value) The shared class cache name specified to the JVM contains invalid characters. Explanation: The system could not create a shared class cache of System action: the size requested (1$). The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. A cache of the maximum size permitted for the system is created. The JVM continues. User response: Correct the shared class cache name so that all User response: characters are valid and restart the JVM. If you require a larger cache, remove and re-create the cache, increasing the value of SHMMAX. JVMSHRC154E Escape character %.*s not valid for cache name JVMSHRC158I Created shared class cache "%1$s" Explanation: An invalid escape character has been specified in a Explanation: shared class cache name. A shared class cache with the given name has been created. System action: The JVM ends, unless you have specified the nonfatal System action: option with -Xshareclasses:nonfatal, in which The JVM continues. case the JVM continues without using shared classes. User response: User response: No action is required. This message is issued when Specify a valid escape character. Valid escape verbose shared class messages are requested. characters are %%u for username and %%g for group JVMSHRC159I Opened shared class cache name. Group name is not valid for Windows. "%1$s" JVMSHRC155E Error copying username into cache Explanation: name An existing shared class cache has been opened. Explanation: System action: The system could not obtain the username for The JVM continues. inclusion in the shared class cache name. User response: System action: No action is required. This message is issued when The JVM ends, unless you have specified the nonfatal verbose shared class messages are requested. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC160E The wait for the creation mutex while opening semaphore has User response: timed out Contact your IBM service representative. Explanation: JVMSHRC156E Error copying groupname into An error has occurred with shared classes processing. cache name System action: Explanation: The JVM ends, unless you have specified the nonfatal The system could not obtain the groupname for option with -Xshareclasses:nonfatal, in which inclusion in the shared class cache name. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you have specified the nonfatal If the condition persists, contact your IBM service option with -Xshareclasses:nonfatal, in which representative. case the JVM continues without using shared classes.
Chapter 1. IBM VM messages 47 JVMSHRC161E The wait for the creation mutex Explanation: while creating shared memory has A change is detected in classpath 2$, causing 3$ timed out classes to be marked as "stale" in the shared classes cache. Explanation: An error has occurred with shared classes processing. System action: The JVM continues. System action: The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which No action is required. This message is issued when case the JVM continues without using shared classes. verbose shared class messages are requested. User response: JVMSHRC171E z/OS cannot create cache of If the condition persists, contact your IBM service requested size: Please check your representative. z/OS system BPXPRMxx settings JVMSHRC162E The wait for the creation mutex Explanation: while opening shared memory has z/OS cannot create a shared classes cache of the timed out requested size. Explanation: System action: An error has occurred with shared classes processing. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. If you need a cache of this size, ask your system programmer to increase the z/OS system BPXPRMxx User response: settings. If the condition persists, contact your IBM service representative. JVMSHRC172E Cannot create cache of requested size due to Operating System JVMSHRC166I Attached to cache "%1$s", size= restrictions %2$d bytes Explanation: Explanation: The size of the cache you requested cannot be created The JVM is attached to the cache named 1$, which is by the operating system. 2$ bytes in size. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM continues. option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. No action is required. This message is issued when User response: verbose shared class messages are requested. Refer to information about cache size limits in the Java JVMSHRC168I Total shared class bytes read= documentation. %1$lld. Total bytes stored=%2$d JVMSHRC179E The ROMClass segment has been Explanation: corrupted. Error reading ROMClass This message details the number of bytes read from at 0x%p the shared classes cache (1$), and the number of Explanation: bytes stored in the cache (2$). An error has occurred during shared class processing. System action: System action: The JVM continues. The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which No action is required. This message is issued when case the JVM continues without using shared classes. verbose shared class messages are requested, and the User response: JVM ends. Contact your IBM service representative. JVMSHRC169I Change detected in JVMSHRC180E Cannot allocate memory for %2$.*1$s...... marked %3$d hashtable entry in cached classes stale ScopeManagerImpl
48 IBM SDK, Java Technology Edition: IBM VM messages Explanation: No action is required. The value is changed An error has occurred during shared class processing. automatically. System action: JVMSHRC202E Failed to initialize pools in shared The JVM continues. class Manager User response: Explanation: The system might be low on resources. Try again when An error has occurred while initializing shared classes. the system is more lightly loaded. If the situation System action: persists, contact your IBM service representative. The JVM ends. JVMSHRC181E Cannot enter ScopeManagerImpl User response: hashtable mutex The system might be low on resources. Try again when Explanation: the system is more lightly loaded. If the situation An error has occurred during shared class processing. persists, contact your IBM service representative. System action: JVMSHRC203E Cannot create hashtable in shared The JVM continues. class Manager User response: Explanation: The system might be low on resources. Try again when An error has occurred while initializing shared classes. the system is more lightly loaded. If the situation System action: persists, contact your IBM service representative. The JVM ends. JVMSHRC190E -Xscminaot value should not be User response: greater than -Xscmaxaot value The system might be low on resources. Try again when Explanation: the system is more lightly loaded. If the situation The value for -Xscminaot cannot be greater than - persists, contact your IBM service representative. Xscmaxaot. JVMSHRC204E Cannot create hashtable mutex in System action: shared class Manager The JVM ends. Explanation: User response: An error has occurred while initializing shared classes. Change the value of -Xscminaot to be less than - System action: Xscmaxaot. The JVM ends. JVMSHRC191I -Xscminaot value is greater than - User response: Xscmx value, so it has been set to The system might be low on resources. Try again when equal -Xscmx value the system is more lightly loaded. If the situation Explanation: persists, contact your IBM service representative. The value for -Xscminaot cannot be greater than - JVMSHRC220E Port layer error code = %1$d Xscmx. Explanation: System action: This message shows the last portable error code The JVM continues. stored in the J9 Port layer. It indicates the last error User response: encountered. No action is required. The value is changed System action: automatically. The JVM ends, unless -Xshareclasses:nonfatal is JVMSHRC192I -Xscmaxaot value is greater than - specified, in which case it continues without using Xscmx value, so it has been set to shared classes. unlimited User response: Explanation: Contact your IBM service representative. The value for -Xscmaxaot cannot be greater than - JVMSHRC221E Platform error message: %1$s Xscmx. Explanation: System action: This message shows the last portable error code The JVM continues. stored in the J9 Port layer, indicating the last error User response: encountered.
Chapter 1. IBM VM messages 49 System action: JVMSHRC227E Error acquiring shared class cache The JVM ends, unless you have specified the nonfatal file header write lock option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Explanation: An error has occurred during shared class processing. User response: Contact your IBM service representative. System action: The JVM ends, unless you have specified the nonfatal JVMSHRC222E Persistent shared class caches option with -Xshareclasses:nonfatal, in which cannot be created/used as case the JVM continues without using shared classes. memory mapping does not support the required capabilities User response: Contact your IBM service representative. Explanation: An error has occurred during shared class processing. JVMSHRC228E Error updating shared class cache last attached time System action: The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred during shared class processing. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you have specified the nonfatal Contact your IBM service representative. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC223E Persistent shared class caches User response: cannot be created/used as file Contact your IBM service representative. locking is not supported Explanation: JVMSHRC229E Error: shared class cache file has An error has occurred during shared class processing. an invalid header System action: Explanation: The JVM ends, unless you have specified the nonfatal An error has occurred during shared class processing. option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which Contact your IBM service representative. case the JVM continues without using shared classes. User response: JVMSHRC225E Error obtaining cache file path Contact your IBM service representative. Explanation: An error has occurred during shared class processing. JVMSHRC230E Error initialising shared cache data header System action: The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred during shared class processing. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you have specified the nonfatal Contact your IBM service representative. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC226E Error opening shared class cache User response: file Contact your IBM service representative. Explanation: An error has occurred during shared class processing. JVMSHRC231E Error setting shared class cache file length System action: The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred during shared class processing. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you have specified the nonfatal Contact your IBM service representative. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes.
50 IBM SDK, Java Technology Edition: IBM VM messages User response: Shared cache %1$s has been created as a persistent Contact your IBM service representative. cache. This message is produced when - Xshareclasses:verbose is specified. JVMSHRC232E Cannot create a cache in readonly mode System action: The JVM continues. Explanation: An error has occurred within shared classes User response: processing. No action is required. System action: JVMSHRC237I Opened shared classes persistent The JVM ends, unless you have specified the nonfatal cache %1$s option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. Shared classes persistent cache %1$s has been User response: opened. This message is produced when - Remove the read-only option from the command-line Xshareclasses:verbose is specified. and restart the JVM. System action: JVMSHRC233E Error creating shared class cache The JVM continues. file header User response: Explanation: No action is required. An error has occurred during shared class processing. JVMSHRC241E Error: unable to delete shared System action: class cache file The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred during shared class processing. case the JVM continues without using shared classes. System action: User response: The JVM ends. Contact your IBM service representative. User response: JVMSHRC234E Error acquiring shared class cache Contact your IBM service representative. file attach read lock JVMSHRC242E Error updating shared class cache Explanation: file last detached time An error has occurred during shared class processing. Explanation: System action: An error has occurred during shared class processing. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. The JVM ends. User response: User response: Contact your IBM service representative. Contact your IBM service representative. JVMSHRC235E Error releasing shared class cache JVMSHRC244E Error obtaining shared class cache file attach read lock file length Explanation: Explanation: An error has occurred during shared class processing. An error has occurred during shared class processing. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: Contact your IBM service representative. Contact your IBM service representative. JVMSHRC236I Created shared classes persistent JVMSHRC245E Error mapping shared class cache cache %1$s file Explanation: Explanation: An error has occurred during shared class processing.
Chapter 1. IBM VM messages 51 System action: JVMSHRC255E Error updating shared class cache The JVM ends, unless you have specified the nonfatal file last detached time on JVM exit option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Explanation: An error has occurred during shared class processing. User response: Contact your IBM service representative. System action: The JVM ends, unless you have specified the nonfatal JVMSHRC246I Attached shared classes option with -Xshareclasses:nonfatal, in which persistent cache %1$s case the JVM continues without using shared classes. Explanation: User response: Shared classes persistent cache %1$s has been Contact your IBM service representative. successfully attached to the process. This message might appear multiple times in verbose output. JVMSHRC256I Persistent shared cache "%1$s" has been destroyed System action: The JVM continues. Explanation: The shared cache 1$ has been removed as requested. User response: This message is only issued if verbose shared classes No action is required. messages has been requested with - JVMSHRC247E Error shared class cache file Xshareclasses:verbose. header eyecatcher is invalid System action: When the cache is removed, the JVM ends. Explanation: An error has occurred during shared class processing. User response: No action is required. System action: The JVM ends, unless you have specified the nonfatal JVMSHRC257E Cannot allocate memory for linked option with -Xshareclasses:nonfatal, in which list item in Manager case the JVM continues without using shared classes. Explanation: User response: An error has occurred during shared class processing. Contact your IBM service representative. System action: JVMSHRC250E Cache cannot be opened read-only The JVM continues. as it has not yet initialized User response: Explanation: The system might be low on resources. Try again when The cache has not completed initialization and cannot the system is more lightly loaded. If the situation be opened in read-only mode. persists, contact your IBM service representative. System action: JVMSHRC258E Cannot allocate memory for The JVM ends, unless you have specified the nonfatal hashtable entry in Manager option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Explanation: An error has occurred during shared class processing. User response: Wait until the cache has initialized or remove the read- System action: only option. The JVM continues. User response: JVMSHRC254E Error setting length of shared class The system might be low on resources. Try again when cache file the system is more lightly loaded. If the situation Explanation: persists, contact your IBM service representative. An error has occurred during shared class processing. JVMSHRC259E Cannot enter Manager hashtable System action: mutex The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error has occurred during shared class processing. User response: System action: Contact your IBM service representative. The JVM continues. User response:
52 IBM SDK, Java Technology Edition: IBM VM messages The system might be low on resources. Try again when System action: the system is more lightly loaded. If the situation If any protected page of the cache is accessed persists, contact your IBM service representative. illegally, the JVM will end. JVMSHRC260E Failed to create pool in User response: ByteDataManager No action is required. Explanation: JVMSHRC274I Memory page protection disabled An error has occurred during shared class processing. for cache System action: Explanation: The JVM ends, unless you have specified the nonfatal The cache memory is not protected against accidental option with -Xshareclasses:nonfatal, in which corruption. case the JVM continues without using shared classes. System action: User response: The cache is not protected. The system might be low on resources. Try again when User response: the system is more lightly loaded. If the situation No action is required. persists, contact your IBM service representative. JVMSHRC277E To run "%s" utility on JVMSHRC269I The system does not support nonpersistent class cache "%s", memory page protection you must also use "nonpersistent" Explanation: suboption Memory page protection is not supported on the Explanation: runtime platform. This feature is disabled. The JVM cannot run the utility on the nonpersistent System action: cache because it needs the nonpersistent suboption Pages of the shared class cache are not protected set. against accidental corruption. System action: User response: The JVM ends. No action is required. User response: JVMSHRC271E Unrecognised sub-option for Add the nonpersistent suboption and restart the JVM. option mprotect= JVMSHRC278I Note that utility "%s" cannot Explanation: operate on incompatible class The sub-option you provided for mprotect= was not cache "%s". Please use a JVM of recognized. the correct level. System action: Explanation: The JVM ends. The JVM cannot run the utility on the cache because it is not compatible. User response: Provide a valid sub-option and restart the JVM. System action: The JVM continues. JVMSHRC272I Full memory page protection successfully enabled for cache User response: No action is required. Explanation: Every memory page of the cache has been protected. JVMSHRC282I The page size of the operating system is incompatible with this System action: cache. Attempting to re-create the If any page of the cache is accessed illegally, the JVM cache. ends. Explanation: User response: The cache is divided up on page boundaries. If there is No action is required. a page size mismatch, the cache is unusable. JVMSHRC273I Default memory page protection System action: successfully enabled for cache The JVM tries to remove and re-create the cache. Explanation: User response: All memory pages of the cache containing runtime No action is required. data have been protected.
Chapter 1. IBM VM messages 53 JVMSHRC284E Cannot create a cache in readonly An error has occurred during shared class processing. mode System action: Explanation: The JVM continues. An error has occurred with shared classes processing. User response: System action: The system might be low on resources. Try again when The JVM ends, unless you have specified the nonfatal the system is more lightly loaded. If the situation option with -Xshareclasses:nonfatal, in which persists, contact your IBM service representative. case the JVM continues without using shared classes. JVMSHRC292E Cannot enter User response: ROMClassResourceManager Remove the read-only option from your command-line hashtable mutex and restart the JVM. Explanation: JVMSHRC285I Opened shared class persistent An error has occurred during shared class processing. cache %1$s read-only System action: Explanation: The JVM continues. Shared classes persistent cache %1$s has been User response: opened for read-only access. This message is The system might be low on resources. Try again when produced when -Xshareclasses:verbose is the system is more lightly loaded. If the situation specified. persists, contact your IBM service representative. System action: JVMSHRC296I Running with option The JVM continues. "noCoreMmap" will mean that IBM User response: will be unlikely to assist with any No action is required. crashes as class data will be missing from system dumps JVMSHRC286I Opened shared class cache %1$s read-only Explanation: Without CORE_MMAP set to "yes", the system dumps Explanation: do not contain the required class data. Shared classes cache %1$s has been opened for read- only access. This message is produced when - System action: Xshareclasses:verbose is specified. The JVM continues. System action: User response: The JVM continues. If possible, run with the environment variable CORE_MMAP set to "yes" and remove the User response: "noCoreMmap" option. No action is required. JVMSHRC297I To use persistent shared class JVMSHRC287E Persistent cache cannot be caches on AIX, environment located on a networked file variable CORE_MMAP must be set system. Either select to "yes" "nonpersistent" or a different cacheDir. Explanation: Without CORE_MMAP set to "yes", the system dumps Explanation: will not contain the required class data. An error has occurred with shared classes processing. System action: System action: The JVM ends. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. Set CORE_MMAP or use nonpersistent caches. User response: JVMSHRC298E To run "%s" utility on persistent Use the "nonpersistent" option. class cache "%s", use the "persistent" suboption JVMSHRC291E Cannot allocate memory for hashtable entry in Explanation: ROMClassResourceManager The JVM cannot run the utility on the persistent cache, because the expected type is nonpersistent. Explanation:
54 IBM SDK, Java Technology Edition: IBM VM messages System action: shared cache, you may need to The JVM ends. destroy and re-create it. User response: Explanation: Add the persistent suboption. An error has occurred during shared class processing. JVMSHRC318E Error recovery: destroying shared System action: memory. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error has occurred during shared class processing. User response: System action: Contact your IBM service representative. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which JVMSHRC323E ERROR: Entering the shared class case the JVM continues without using shared classes. cache header mutex failed. Warning: your cache may be User response: corrupt. If you experience Contact your IBM service representative. problems using the shared cache, JVMSHRC319E Error recovery: closing shared you may need to destroy and re- memory. create it. Explanation: Explanation: An error has occurred during shared class processing. An error has occurred during shared class processing. System action: System action: The JVM ends, unless you have specified the nonfatal The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: Contact your IBM service representative. Contact your IBM service representative. JVMSHRC320E Error recovery: destroying shared JVMSHRC324E ERROR: Exiting the shared class memory semaphores. cache header mutex failed. Warning: your cache may be Explanation: corrupt. If you experience An error has occurred during shared class processing. problems using the shared cache, System action: you may need to destroy and re- The JVM ends, unless you have specified the nonfatal create it. option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error has occurred during shared class processing. User response: System action: Contact your IBM service representative. The JVM ends, unless you have specified the nonfatal JVMSHRC321E Error recovery: closing shared option with -Xshareclasses:nonfatal, in which memory semaphores. case the JVM continues without using shared classes. Explanation: User response: An error has occurred during shared class processing. Contact your IBM service representative. System action: JVMSHRC327E SH_OSCachesysv::acquireWriteLo The JVM ends, unless you have specified the nonfatal ck() call to j9shsem_wait has option with -Xshareclasses:nonfatal, in which failed with error %d. case the JVM continues without using shared classes. Explanation: User response: An error occurred waiting on a semaphore. Contact your IBM service representative. System action: JVMSHRC322E Failed initializing semaphores for The JVM ends. shared class cache. Warning: your User response: cache may be corrupt. If you experience problems using the
Chapter 1. IBM VM messages 55 The system might be low on resources. Try again when JVMSHRC335E Error recovery failed: Destroying the system is more lightly loaded. If the situation shared semaphore has failed. persists, contact your IBM service representative. Explanation: JVMSHRC328E System V IPC reported the An error has occurred during shared class processing. following error '%s' System action: Explanation: The JVM ends, unless you have specified the nonfatal An error occurred during the use of System V IPC option with -Xshareclasses:nonfatal, in which functions in the JVM. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you have specified the nonfatal Consult the diagnostic information in the Java option with -Xshareclasses:nonfatal, in which documentation. case the JVM continues without using shared classes. JVMSHRC336E Port layer error code = %1$d User response: Contact your IBM service representative if this Explanation: problem persists. This message shows the last portable error code stored in the J9 Port layer, indicating the last error JVMSHRC329E SH_CompositeCacheImpl:: encountered. enterReadWriteAreaMutex failed to acquire the string table mutex System action: (return code %d). The JVM ends, unless -Xshareclasses:nonfatal is specified, in which case processing continues Explanation: without using shared classes. An error has prevented updates to the shared class User response: cache. Contact your IBM service representative. System action: The JVM attempts to continue. JVMSHRC337E Platform error message: %1$s User response: Explanation: Contact your IBM service representative if this This message shows the platform specific error code problem persists. and message related to the last error that was stored in the J9 Port layer. If the message does not indicate JVMSHRC330E SH_CompositeCacheImpl::runExit an error, there is probably no platform error associated Code failed to acquire the write with this port layer error. area mutex (return code %d). System action: Explanation: The JVM ends, unless -Xshareclasses:nonfatal An error has prevented updates to the shared class is specified, in which case processing continues cache during shutdown. without using shared classes. System action: User response: The JVM attempts to continue the shutdown process. Contact your IBM service representative. User response: JVMSHRC338E Port layer error code = %1$d Contact your IBM service representative if this problem persists. Explanation: This message shows the last portable error code JVMSHRC334E Error recovery failed: Destroying stored in the J9 Port layer, indicating the last error shared memory has failed. encountered. Explanation: System action: An error has occurred during shared class processing. The JVM failed to clean up a System V IPC resource System action: during error recovery. The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which Consult the diagnostic information in the Java case the JVM continues without using shared classes. documentation. User response: JVMSHRC339E Platform error message: %1$s Consult the diagnostic information in the Java documentation. Explanation:
56 IBM SDK, Java Technology Edition: IBM VM messages This message shows the platform specific error code JVMSHRC364E SH_OSCachesysv::acquireWriteLo and message related to the last error that was stored ck() call to j9shsem_wait on semid in the J9 Port layer. If the message does not indicate %d has failed with error %d. an error, there is probably no platform error associated with this port layer error. Explanation: An error occurred while waiting on a semaphore. System action: The JVM failed to clean up a System V IPC resource System action: during error recovery. The JVM ends. User response: User response: Consult the diagnostic information in the Java The system might be low on resources. Try again when documentation. the system is more lightly loaded. If the situation persists, contact your IBM service representative. JVMSHRC340E Shared Cache CRC check failed. Stored CRC %1$x, calculated CRC JVMSHRC375E The cache name is too long when %2$x the user name is included. There are %d bytes left in this buffer, Explanation: and your user name is %d bytes. This message shows the CRC values when the cache startup CRC check fails Explanation: The system cannot include the username in the System action: shared class cache name. The JVM attempts to re-create the cache before starting. If this process fails, the JVM ends, unless you System action: have specified the nonfatal option with - The JVM ends, unless you have specified the nonfatal Xshareclasses:nonfatal. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. User response: Contact your IBM service representative. User response: Contact your IBM service representative. JVMSHRC361E Error while attaching to the shared JVMSHRC404E memory during open/create Failed to get a directory for the cache Explanation: An error has occurred in shared class processing. Explanation: The directory path requested is bigger than the System action: internal buffer space. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. The system might be low on resources. Try again when the system is more lightly loaded. If the situation User response: persists, contact your IBM service representative. Use a shorter path or cache name. JVMSHRC405E JVMSHRC363E Cannot allocate api for shared Failed to create a directory for the classes in shrinit cache Explanation: Explanation: An error has occurred in shared class initialization. The directory specified for the shared cache could not be created. System action: The JVM ends, unless you have specified the nonfatal System action: option with -Xshareclasses:nonfatal, in which The JVM ends, unless you have specified the nonfatal case the JVM continues without using shared classes. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. User response: The system might be low on resources. Try again when User response: the system is more lightly loaded. If the situation Make sure that you have the correct file permissions persists, contact your IBM service representative. for the controldir or cachedir chosen. JVMSHRC428I Removed older generation of shared class cache "%s"
Chapter 1. IBM VM messages 57 Explanation: System action: The older generation of the shared class cache was A new Shared Intern Table size is calculated, successfully removed. proportional to the shared cache size. Processing continues. System action: Processing continues. User response: Check the shared cache size. Check the intern string User response: table node count, which is specified by the -Xitsn No action is required. option. JVMSHRC429I Failed to remove older generation JVMSHRC436E Error acquiring shared class cache of shared class cache "%s" file header write lock Explanation: Explanation: The older generation of the shared class cache cannot An error has occurred in shared class processing. be removed. System action: System action: The JVM ends, unless you have specified the nonfatal Processing continues. option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. Run with the option -Xshareclasses:verbose User response: enabled to see other messages that might indicate Contact your IBM service representative. why the cache is not removed. JVMSHRC437E Error releasing shared class cache JVMSHRC430I Failed to remove current file header read lock generation of shared class cache "%s" Explanation: An error has occurred in shared class processing. Explanation: The current generation of the shared class cache System action: cannot be removed. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. Processing continues. User response: User response: Contact your IBM service representative. Other messages might be issued indicating the reason why the cache is not removed. Investigate these JVMSHRC442E Shared cache "%s" is corrupt. messages. Corruption code is %d. Corrupt value is 0x%x. No new JVMs will JVMSHRC434E Value=%d passed by -Xitsn option be allowed to connect to the is outside of the range of prime cache. Existing JVMs can continue number values supported by the to function, but cannot update the VM. Supported range = 0 - %u cache. Explanation: Explanation: The value specified for the -Xitsn option is larger The shared class cache is corrupt. than the biggest prime number supported by the JVM. System action: System action: The JVM attempts to re-create the cache before The JVM ends. starting. If this process fails, the JVM ends unless you User response: have specified the nonfatal option with - Check the value specified by the -Xitsn option on the Xshareclasses:nonfatal. command line. The supported range is shown in the User response: error message. Remove the shared class cache and try again. If the JVMSHRC435I -Xitsn%2$u uses %1$u bytes of situation persists, contact your IBM service memory, which is larger than the representative. shared classes cache size of %3$u JVMSHRC443I Cache CRC is incorrect indicating a bytes corrupt cache. Incorrect cache Explanation: CRC: 0x%x. The Shared Intern Table is part of the shared cache, Explanation: therefore it cannot be larger than the shared cache.
58 IBM SDK, Java Technology Edition: IBM VM messages An error has occurred in shared class processing. An error has occurred in shared class processing. System action: System action: The cache is marked as corrupt and the JVM The cache is marked as corrupt and the JVM continues. continues. User response: User response: Contact your IBM service representative. Contact your IBM service representative. JVMSHRC444I Read corrupt data for cache entry JVMSHRC449E Padding is non zero. Padding bytes header 0x%p (invalid item length) in cache header are: %u. Explanation: Explanation: An error has occurred in shared class processing. An error has occurred in shared class processing. System action: System action: The cache is marked as corrupt and the JVM The cache is marked as corrupt and the JVM continues. continues. User response: User response: Contact your IBM service representative. Contact your IBM service representative. JVMSHRC445E Size of cache is too small to be JVMSHRC450E Data length field in cache header useful. Invalid cache size: 0x%x. is not valid. Data length in cache header is: %u. Explanation: An error has occurred in shared class processing. Explanation: An error has occurred in shared class processing. System action: The cache is marked as corrupt and the JVM System action: continues. The cache is marked as corrupt and the JVM continues. User response: Contact your IBM service representative. User response: Contact your IBM service representative. JVMSHRC446E Failed to acquire header write lock during cache startup with error JVMSHRC451E Data start field in cache header is code: %d. not valid. Data start address in cache header is: 0x%p. Explanation: An error has occurred in shared class processing. Explanation: An error has occurred in shared class processing. System action: The cache is marked as corrupt and the JVM System action: continues. The cache is marked as corrupt and the JVM continues. User response: Contact your IBM service representative. User response: Contact your IBM service representative. JVMSHRC447E Cache header eyecatcher is not valid. Address of eyecatcher string JVMSHRC457E Invalid cache name, the cache in cache header: 0x%p. name "%.*s" contains only whitespace or is empty Explanation: An error has occurred in shared class processing. Explanation: The specified shared class cache name contains only System action: white space characters, or no characters. The cache is marked as corrupt and the JVM continues. System action: The JVM ends, unless you have specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which Contact your IBM service representative. case the JVM continues without using shared classes. JVMSHRC448E Cache size field in cache header is User response: not valid. Cache size in cache Change the shared class cache name to include non- header is: 0x%x. whitespace characters, and start the JVM again. Explanation:
Chapter 1. IBM VM messages 59 JVMSHRC461E -Xscminjitdata value should not JVMSHRC500E The debug area is corrupt because be greater than -Xscmaxjitdata free space low address %p, is value greater than free space high address %p Explanation: The value for -Xscminjitdata cannot be larger than Explanation: -Xscmaxjitdata. An error has occurred in shared class processing. System action: System action: The JVM ends. The cache is marked as corrupt and the JVM continues. User response: Change the value of -Xscminjitdata to be less than User response: or equal to the value of -Xscmaxjitdata. Contact your IBM service representative. JVMSHRC462I -Xscminjitdata value is greater JVMSHRC501E The debug area is corrupt because than -Xscmx value, so it has been the 'line number table data' low set to equal -Xscmx value address %p, is greater than the high address %p Explanation: The value specified for the -Xscminjitdata option Explanation: cannot be greater than the value for the -Xscmx An error has occurred in shared class processing. option. System action: System action: The cache is marked as corrupt and the JVM The value for the -Xscminjitdata option is changed continues. and the JVM continues. User response: User response: Contact your IBM service representative. No action is required. JVMSHRC502E The debug area is corrupt because JVMSHRC463I -Xscmaxjitdata value is greater the 'local variable table data' low than -Xscmx value, so it has been address %p, is greater than the set to unlimited high address %p Explanation: Explanation: The value specified for the -Xscmaxjitdata option An error has occurred in shared class processing. cannot be greater than the value specified for the - System action: Xscmx option. The cache is marked as corrupt and the JVM System action: continues. The value of the -Xscmaxjitdata option is changed User response: automatically and the JVM continues. Contact your IBM service representative. User response: JVMSHRC503E The debug area is corrupt because No action is required. storing 'line number table' %d JVMSHRC488E Total of -Xscminaot and - bytes, and 'local variable table' Xscminjitdata values should not %d bytes, will result in a 'line be greater than available cache number table data' high address of size %p, which will be greater than the new 'local variable table data' low Explanation: address %p The total value of the -Xscminaot and - Xscminjitdata options cannot be greater than the Explanation: available cache size. An error has occurred in shared class processing. System action: System action: The JVM ends. The cache is marked as corrupt and the JVM continues. User response: Change the values of the -Xscminaot and - User response: Xscminjitdata options so that the total of these Contact your IBM service representative. values does not exceed the available cache size.
60 IBM SDK, Java Technology Edition: IBM VM messages JVMSHRC504E Cache data start is null. data start: System action: %p The cache is marked as corrupt and the JVM continues. Explanation: An error has occurred in shared class processing. User response: Contact your IBM service representative. System action: The cache is marked as corrupt and the JVM JVMSHRC514E Invalid setting for cacheDirPerm continues. option. This must be unix style file permission in the range of 0700 - User response: 0777 or 1700 - 1777 (in octal Contact your IBM service representative. representation). JVMSHRC505E The debug area is corrupt because Explanation: free space high address %p minus The value specified for the cacheDirPerm parameter the free space low address %p is not in a valid format. exceeds the debug region size of %lu bytes System action: The JVM ends. Explanation: An error has occurred in shared class processing. User response: Run the command again with a valid cacheDirPerm System action: value. Use UNIX-style file permissions in octal The cache is marked as corrupt and the JVM representation in the range of 0700 - 0777 or 1700 - continues. 1777. User response: JVMSHRC517E Unrecognised sub-option for Contact your IBM service representative. option printallstats= . Use JVMSHRC506E The debug area is corrupt because printallstats=help to see available its size of %lu is larger than the options. total cache size of %u stored in Explanation: the cache header The suboption provided for printallstats= is not Explanation: recognized. An error has occurred in shared class processing. System action: System action: The JVM ends. The cache is marked as corrupt and the JVM User response: continues. Run printallstats=help to see a list of valid User response: options and try again. Contact your IBM service representative. JVMSHRC547E Cannot allocate memory for JVMSHRC508E Acquired a different semaphore character array in shrinit than previously used with this Explanation: cache. old semid=%d, new semid= An error has occurred when parsing shared class %d command-line options. Explanation: System action: An error has occurred in shared class processing. The JVM ends, unless you have specified the nonfatal System action: option with -Xshareclasses:nonfatal, in which The cache is marked as corrupt and the JVM case the JVM continues without using shared classes. continues. User response: User response: The system might be low on resources. Try again when Contact your IBM service representative. the system is more lightly loaded. If the situation persists, contact your IBM service representative. JVMSHRC511I Composite cache has bad initialization flag value. The value JVMSHRC549E - of ccInitComplete is %lu Xshareclasses:checkStringTableR eset may fail. String table is not Explanation: large enough. It needs to be more The value of the initialization flag for the composite than to OS page size. Table size = cache is incorrect. %d, Page size = %d
Chapter 1. IBM VM messages 61 Explanation: JVMSHRC559E Failed to create a directory \"%s\" An error has occurred in shared class processing. for the shared class cache System action: Explanation: The JVM ends. The directory specified for the shared class cache User response: could not be created. Contact your IBM service representative. System action: JVMSHRC550E ROUND_TO_PAGE_SIZE runtime The JVM ends, unless you specified the nonfatal flag is missing. - option with -Xshareclasses:nonfatal, in which Xshareclasses:checkStringTableR case the JVM continues without using shared classes. eset requires string table be User response: rounded to page size. Make sure that you have the right permissions for the Explanation: controldir or cachedir chosen. An error has occurred in shared class processing. JVMSHRC560E Internal cache name is not proper. System action: Explanation: The JVM ends. An error has occurred in shared class processing. User response: System action: Contact your IBM service representative. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which JVMSHRC551E Cache \"%s\" is marked as full. case the JVM continues without using shared classes. Failed to allocate block size = %d. User response: Explanation: Contact your IBM service representative. The JVM is unable to store the requested data in the cache because the cache is marked as full. JVMSHRC561E Failed to initialize the shared System action: classes cache, there is not enough The JVM ends. space in the file system. Available free disk space bytes = %lld, User response: requested bytes = %lld. Contact your IBM service representative. Explanation: JVMSHRC552E Cannot allocate requested block An error has occurred in shared class processing. size for cache \"%s\". Available System action: bytes = %d, Requested bytes = %d The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which There is not enough free memory in the shared class case the JVM continues without using shared classes. cache to store the amount of data requested. User response: System action: Increase the amount of space available in your file The JVM ends. system and try again. User response: JVMSHRC562I Read corrupt data for cache entry Contact your IBM service representative. header 0x%p (invalid item length JVMSHRC557E Unrecognised sub-option for of %u bytes) option printstats= . Use Explanation: printstats=help to see available An error has occurred in shared class processing. options. System action: Explanation: The cache is marked as corrupt and the JVM The suboption provided for printstats= is not continues. recognized. User response: System action: Contact your IBM service representative. The JVM ends. JVMSHRC572E Opening a Realtime cache, which User response: is not compatible with this JVM, Run printstats=help for a list of valid options and use the -Xrealtime JVM option to try again. access this cache
62 IBM SDK, Java Technology Edition: IBM VM messages Explanation: JVMSHRC598E The raw class data area is corrupt A standard JVM is accessing a real-time cache. because its size of %lu is larger System action: than the total cache size of %lu. The JVM ends, unless you have specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error has occurred in shared class processing. case the JVM continues without using shared classes. System action: User response: The cache is marked as corrupt and the JVM To use a real-time JVM, specify the -Xrealtime continues. option. If you do not want to use a real-time JVM, use a different cache name. User response: Contact your IBM service representative. JVMSHRC590E The "enableBCI" sub-option was specified but the existing cache JVMSHRC599E The raw class data area free space was not created with the is corrupt ('free space start'=%p, "enableBCI" sub-option. 'free space end'=%p, 'free size'= %lu bytes) Explanation: An error occurred when processing shared class Explanation: options. An error has occurred in shared class processing. System action: System action: The JVM ends, unless you have specified the nonfatal The cache is marked as corrupt and the JVM option with -Xshareclasses:nonfatal, in which continues. case the JVM continues without using shared classes. User response: User response: Contact your IBM service representative. Remove the enableBCI suboption, which is JVMSHRC600E The raw class data area is corrupt incompatible with this shared classes cache and try because storing %u bytes will again. exceed the available area free JVMSHRC594E The - space ('free space start'=%p, 'free Xshareclasses:cacheRetransforme space end'=%p). d sub-option is incompatible with Explanation: a shared cache created with the An error has occurred in shared class processing. enableBCI sub-option System action: Explanation: The cache is marked as corrupt and the JVM An error occurred when processing shared class continues. options. User response: System action: Contact your IBM service representative. The JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal, in which JVMSHRC605E The memory size for \"%s\" is too case the JVM continues without using shared classes. large, or specifies units other than 'K','M', or 'G'. User response: Remove the cacheRetransformed suboption, which Explanation: is incompatible with this shared classes cache and try The memory size is too large, or specifies units other again. than K, M, or G. System action: JVMSHRC595E Command-line options \"%s\" and The JVM ends. \"%s\" are incompatible Explanation: User response: The JVM found incompatible suboptions when Correct or remove the incorrect command-line option processing the shared class options. and try again. System action: JVMSHRC611E The "disableBCI" sub-option is The JVM ends. specified but the existing cache was created with the "enableBCI" User response: sub-option. Remove one of the incompatible -Xshareclasses suboptions and try again. Explanation:
Chapter 1. IBM VM messages 63 An error occurred when processing shared class JVMSHRC616E An error has occurred while options. opening semaphore. Mismatch in System action: number of semaphores in the The JVM ends, unless you have specified the nonfatal semaphore set. option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error occurred during shared class processing. User response: System action: Remove the disableBCI suboption, which is The JVM ends, unless you specified the nonfatal incompatible with this shared classes cache and try option with -Xshareclasses:nonfatal, in which again. case the JVM continues without using shared classes. JVMSHRC613E An error has occurred while User response: opening semaphore. Control file is Check any messages that follow, which might indicate found to be corrupt. the problem. For further assistance, contact your IBM Explanation: service representative. An error occurred during shared class processing. JVMSHRC617E An error has occurred while System action: opening semaphore. Semaphore The JVM ends, unless you specified the nonfatal marker not found in the option with -Xshareclasses:nonfatal, in which semaphore set. case the JVM continues without using shared classes. Explanation: User response: An error occurred during shared class processing. Check any messages that follow, which might indicate System action: the problem. For further assistance, contact your IBM The JVM ends, unless you specified the nonfatal service representative. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC614E An error has occurred while opening semaphore. Mismatch in User response: semaphore ID. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM Explanation: service representative. An error occurred during shared class processing. System action: JVMSHRC618E Semaphore control file is not The JVM ends, unless you specified the nonfatal readable. option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. The JVM cannot read the semaphore control file. User response: System action: Check any messages that follow, which might indicate The JVM ends, unless you specified the nonfatal the problem. For further assistance, contact your IBM option with -Xshareclasses:nonfatal, in which service representative. case the JVM continues without using shared classes. JVMSHRC615E An error has occurred while User response: opening semaphore. Mismatch in Check that the semaphore control file has read/write semaphore key. permissions and try again. If the situation persists, Explanation: contact your IBM service representative. An error occurred during shared class processing. JVMSHRC619E Semaphore control file is read System action: only. The JVM ends, unless you specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which The semaphore control file has only read permission. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you specified the nonfatal Check any messages that follow, which might indicate option with -Xshareclasses:nonfatal, in which the problem. For further assistance, contact your IBM case the JVM continues without using shared classes. service representative. User response:
64 IBM SDK, Java Technology Edition: IBM VM messages Check that the semaphore control file has read/write User response: permissions and try again. If the situation persists, Check any messages that follow, which might indicate contact your IBM service representative. the problem. For further assistance, contact your IBM service representative. JVMSHRC620E Error opening shared memory region. Control file is found to be JVMSHRC624E Error opening shared memory corrupt. region. Check for user id failed. Explanation: Explanation: An error occurred during shared class processing. An error occurred during shared class processing. System action: System action: The JVM ends, unless you specified the nonfatal The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: Check any messages that follow, which might indicate Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM the problem. For further assistance, contact your IBM service representative. service representative. JVMSHRC621E Error opening shared memory JVMSHRC625E Error opening shared memory region. Mismatch in shared region. Check for shared memory memory ID. size failed. Explanation: Explanation: An error occurred during shared class processing. An error occurred during shared class processing. System action: System action: The JVM ends, unless you specified the nonfatal The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: Check any messages that follow, which might indicate Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM the problem. For further assistance, contact your IBM service representative. service representative. JVMSHRC622E Error opening shared memory JVMSHRC626I Recreation of shared memory region. Mismatch in shared control file is not allowed when memory key. retrieving cache stats. Explanation: Explanation: An error occurred during shared class processing. This message provides information only. System action: System action: The JVM ends, unless you specified the nonfatal The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response: User response: Check any messages that follow, which might indicate No action is required. the problem. For further assistance, contact your IBM JVMSHRC627I Recreation of shared memory service representative. control file is not allowed when JVMSHRC623E Error opening shared memory running in read-only mode. region. Check for group id failed. Explanation: Explanation: This message is for information only. An error occurred during shared class processing. System action: System action: The JVM ends, unless you specified the nonfatal The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. case the JVM continues without using shared classes. User response:
Chapter 1. IBM VM messages 65 No action is required. System action: The JVM continues. The named shared cache is still JVMSHRC628E Shared memory control file is not operational and continues to provide increased readable. performance for loading the classes that are stored. Explanation: However, no more AOT compiled methods can be The JVM cannot read the shared memory control file. added to the cache. System action: User response: The JVM ends, unless you specified the nonfatal To allow the JVM to store more AOT compiled option with -Xshareclasses:nonfatal, in which methods into the shared classes cache, increase the case the JVM continues without using shared classes. value that is specified by the -Xscminaot option. User response: JVMSHRC632I Space reserved for JIT data in Check that the shared memory control file has read/ shared cache \"%s\" is full. Use - write permissions and try again. If the situation Xscminjitdata to increase space persists, contact your IBM service representative. reserved for JIT data. JVMSHRC629E Shared memory control file is read Explanation: only. The available space for storing JIT data in the named shared classes cache is full. No further JIT data can be Explanation: added. The shared memory control file has only read permission. System action: The JVM continues. The named shared cache is still System action: operational and continues to provide increased The JVM ends, unless you specified the nonfatal performance for loading the classes that are stored. option with -Xshareclasses:nonfatal, in which However, no more JIT-related data can be added to case the JVM continues without using shared classes. the cache. User response: User response: Check that the shared memory control file has read/ To allow the JVM to store more JIT-related data into write permissions and try again. If the situation the shared classes cache, increase the value that is persists, contact your IBM service representative. specified by the -Xscminjitdata option. JVMSHRC630I Space is full for storing non-AOT/ JVMSHRC633E The "- non-JIT data, such as classes, in XX:+StoreIntermediateClassfile" shared cache \"%s\". option was specified but the Explanation: existing cache was not created The available space for storing non-AOT/non-JIT data, with the "- such as classes, in the named shared classes cache is XX:+StoreIntermediateClassfile" full. No further data can be added. option. System action: Explanation: The JVM continues. The named shared cache is still An error occurred when processing shared class operational and continues to provide increased options. performance for loading the classes that are stored. System action: However, classes that are not contained in the cache The JVM ends, unless you specified the nonfatal are always loaded from their source. option with -Xshareclasses:nonfatal, in which User response: case the JVM continues without using shared classes. To gain the full benefit of shared classes, delete and User response: re-create the named cache, specifying a larger shared Remove the incompatible option and try again. class cache size with the -Xscmx parameter. JVMSHRC634E The "-XX:- JVMSHRC631I Space reserved for AOT data in StoreIntermediateClassfile" shared cache \"%s\" is full. Use - option was specified but the Xscminaot to increase space existing cache was created with reserved for AOT data. the "- Explanation: XX:+StoreIntermediateClassfile" The available space for storing AOT data in the named option. shared classes cache is full. No further AOT data can Explanation: be added.
66 IBM SDK, Java Technology Edition: IBM VM messages An error occurred when processing shared class Replace the incompatible -Xshareclasses option options. with a -Xshareclasses utility option and try again. System action: JVMSHRC646E The JVM could not check the The JVM ends, unless you specified the nonfatal permissions of the semaphore set option with -Xshareclasses:nonfatal, in which associated with the shared cache. case the JVM continues without using shared classes. Explanation: User response: An error occurred during shared classes processing. Remove the option -XX:- System action: StoreIntermediateClassfile from the command The JVM ends, unless you specified the nonfatal line to use the existing shared classes cache. option with -Xshareclasses:nonfatal, in which JVMSHRC637E The - case the JVM continues without using shared classes. Xshareclasses:cacheRetransforme User response: d sub-option is incompatible with Contact your IBM service representative. an existing BCI enabled shared cache. JVMSHRC647E The JVM detected effective user id of the process is the owner but not Explanation: the creator of semaphore set An error occurred when processing shared class associated with the shared cache. options. JVM will not attach to the shared System action: cache to prevent accessing The JVM ends, unless you specified the nonfatal unintended shared cache. option with -Xshareclasses:nonfatal, in which Explanation: case the JVM continues without using shared classes. An error occurred during shared classes processing. User response: System action: Remove the incompatible suboption and try again. The JVM ends, unless you specified the nonfatal JVMSHRC638I Cache creation with the option with -Xshareclasses:nonfatal, in which cacheRetransformed option forces case the JVM continues without using shared classes. disableBCI mode. User response: Explanation: Delete the existing shared classes cache and restart to When you use the option - create a new shared classes cache. Xshareclasses:cacheRetransformed, the shared JVMSHRC648E The JVM is not configured to cache that is created does not support Byte Code access semaphore set associated Instrumentation (BCI). Using this option is equivalent with existing non-persistent to setting -Xshareclasses:disableBCI. shared class cache. To attach to System action: the non-persistent shared class The JVM continues. cache, use 'groupAccess' sub- option. User response: No action is required. This message is for information Explanation: only. An error occurred during shared classes processing. JVMSHRC639E Only shared cache utility options System action: can be used in combination with - The JVM ends, unless you specified the nonfatal Xmt. Put other shared cache option with -Xshareclasses:nonfatal, in which options in the javad.options file. case the JVM continues without using shared classes. Explanation: User response: Shared cache runtime options must be specified in the Modify the existing -Xshareclasses option to add a javad.options file. The javad process must be groupAccess sub option and start again. restarted before any shared classes cache options JVMSHRC649E The JVM does not permit access to take effect. the shared cache's semaphore set System action: created and owned by another The JVM ends. user not in its group. User response: Explanation: An error occurred during shared classes processing.
Chapter 1. IBM VM messages 67 System action: Modify the existing -Xshareclasses option to add The JVM ends, unless you specified the nonfatal the groupAccess sub option and try again. option with -Xshareclasses:nonfatal, in which JVMSHRC653E The JVM is not configured to case the JVM continues without using shared classes. access shared memory associated User response: with existing non-persistent Specify a different cache name or directory to avoid a shared class cache. To attach to conflict with the existing shared classes cache. This the non-persistent shared class cache was created by another user that is not in the cache, use 'groupAccess' and same group. 'readonly' sub-option. JVMSHRC650E The JVM could not check the Explanation: permissions of the shared memory An error occurred during shared classes processing. associated with the shared cache. System action: Explanation: The JVM ends, unless you specified the nonfatal An error occurred during shared classes processing. option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. System action: The JVM ends, unless you specified the nonfatal User response: option with -Xshareclasses:nonfatal, in which Modify the existing -Xshareclasses option to add case the JVM continues without using shared classes. the groupAccess and readOnly sub options and try again. User response: Contact your IBM service representative. JVMSHRC654E The JVM does not permit access to the shared cache's shared memory JVMSHRC651E The JVM detected effective user id region created and owned by of the process is the owner but not another user not in its group. the creator of shared memory associated with the shared cache. Explanation: JVM will not attach to the shared An error occurred during shared classes processing. cache to prevent accessing System action: unintended shared cache. The JVM ends, unless you specified the nonfatal Explanation: option with -Xshareclasses:nonfatal, in which An error occurred during shared classes processing. case the JVM continues without using shared classes. System action: User response: The JVM ends, unless you specified the nonfatal Specify a different cache name or directory to avoid a option with -Xshareclasses:nonfatal, in which conflict with an existing shared classes cache. This case the JVM continues without using shared classes. cache was created by another user that is not in the same group. User response: Delete the existing shared classes cache and restart to JVMSHRC656E The JVM is not configured to create a new shared classes cache. access shared cache file. To attach to the shared class cache, use JVMSHRC652E The JVM is not configured to 'groupAccess' suboption. access shared memory associated with existing non-persistent Explanation: shared class cache. To attach to An error occurred within shared classes processing. the non-persistent shared class System action: cache, use 'groupAccess' sub- The Java VM ends, unless you specified the nonfatal option. option by using the -Xshareclasses:nonfatal Explanation: parameter, in which case the Java VM continues An error occurred during shared classes processing. without using shared classes. System action: User response: The JVM ends, unless you specified the nonfatal Modify the existing -Xshareclasses: option to add option with -Xshareclasses:nonfatal, in which the groupAccess suboption, then restart the Java case the JVM continues without using shared classes. VM. User response: JVMSHRC657E The JVM does not permit access to the shared cache file because the
68 IBM SDK, Java Technology Edition: IBM VM messages JVM process's user ID and group The Java VM continues. ID are different from the shared User response: cache file owner's user ID and Use the ipcrm command to remove the semaphore group ID, and the JVM process's set that is indicated in the error message, if it still user ID does not belong to the exists and is not in use. shared cache file owner's group. JVMSHRC661E The JVM failed to associate shared Explanation: memory id=%d with the shared An error occurred within shared classes processing. class cache. System action: Explanation: The Java VM ends, unless you specified the nonfatal This message displays the ID of the shared memory option by using the -Xshareclasses:nonfatal that the Java VM failed to associate with the shared parameter, in which case the Java VM continues class cache due to an error that is indicated in previous without using shared classes. messages. User response: System action: Specify a different cache name or directory to avoid The Java VM continues. conflict with an existing shared cache that is created by another user who is in a different group. User response: Use the ipcrm command to remove the shared JVMSHRC658E The JVM could not check the memory that is indicated in the error message, if it still permissions of the shared cache exists and is not in use. file. JVMSHRC662E Error recovery: destroyed Explanation: semaphore set associated with An error occurred within shared classes processing. shared class cache. System action: Explanation: The Java VM ends, unless you specified the nonfatal An error occurred in shared class processing, and as option by using the -Xshareclasses:nonfatal part of error recovery the Java VM destroyed the parameter, in which case the Java VM continues semaphore set that was associated with the shared without using shared classes. class cache. User response: System action: Contact your IBM service representative. The Java VM detected an error during shared class JVMSHRC659E An error has occurred while processing and destroyed the semaphore set in an opening shared memory attempt to recover. Explanation: User response: An error occurred in shared class processing. Further Contact your IBM service representative. messages might follow, providing more detail. JVMSHRC663I Error recovery: destroyed System action: semaphore set with id=%d The Java VM ends, unless you specified the nonfatal associated with shared class option by using the -Xshareclasses:nonfatal cache. parameter, in which case the Java VM continues Explanation: without using shared classes. An error occurred in shared class processing, and as User response: part of error recovery the Java VM destroyed the Contact your IBM service representative, unless semaphore set that as associated with the shared subsequent messages indicate otherwise. class cache. JVMSHRC660E The JVM failed to associate System action: semaphore set id=%d with the The Java VM detected an error during shared class shared class cache. processing and destroyed the semaphore set in an attempt to recover. Explanation: This message displays the ID of the semaphore set User response: that the Java VM failed to associate with the shared Contact your IBM service representative. class cache due to an error that is indicated in previous JVMSHRC664E Error recovery failed: Failed to messages. destroy the semaphore set with System action: semid=%d associated with shared
Chapter 1. IBM VM messages 69 class cache. Only creator or owner An error occurred in shared class processing and as or user with administrative part of error recovery the Java VM destroyed the privileges can destroy the shared memory that was associated with the shared semaphore set. class cache. Explanation: System action: An error occurred in shared class processing. The Java The Java VM detected an error during shared class virtual machine's attempt to destroy the semaphore processing and destroyed the shared memory in an set as part of error recovery failed because the attempt to recover. operating system allows only the creator, owner, or a User response: user with administrative privileges to destroy the Contact your IBM service representative. semaphore set. JVMSHRC668E Error recovery failed: Failed to System action: destroy the shared memory with The Java VM ends, unless you specified the nonfatal shmid=%d associated with shared option by using the -Xshareclasses:nonfatal class cache. Only creator or owner parameter, in which case the Java VM continues or user with administrative without using shared classes. privileges can destroy the shared User response: memory. No action is required. Explanation: JVMSHRC665E Error recovery failed: Failed to An error occurred in shared class processing. The Java destroy the semaphore set with virtual machine's attempt to destroy the shared semid=%d associated with shared memory as part of error recovery failed because the class cache. operating system allows only the creator, owner, or a user with administrative privileges to destroy the Explanation: shared memory. An error occurred in shared class processing. The Java virtual machine's attempt to destroy the semaphore System action: set as part of error recovery failed. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal System action: parameter, in which case the Java VM continues The Java VM ends, unless you specified the nonfatal without using shared classes. option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM continues User response: without using shared classes. No action is required. User response: JVMSHRC669E Error recovery failed: Failed to Contact your IBM service representative. destroy the shared memory with shmid=%d associated with shared JVMSHRC666E Error recovery: destroyed shared class cache. memory associated with shared class cache. Explanation: An error occurred in shared class processing. The Java Explanation: virtual machine's attempt to destroy the shared An error occurred in shared class processing and as memory as part of error recovery failed. part of error recovery the Java VM destroyed the shared memory that was associated with the shared System action: class cache. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal System action: parameter, in which case the Java VM continues The Java VM detected an error during shared class without using shared classes. processing and destroyed the shared memory in an attempt to recover. User response: Contact your IBM service representative. User response: Contact your IBM service representative. JVMSHRC670I Error recovery: attempting to use shared cache in readonly mode if JVMSHRC667I Error recovery: destroyed shared the shared memory region exists, memory with id=%d associated in response to "- with shared class cache. Xshareclasses:nonfatal" option. Explanation: Explanation:
70 IBM SDK, Java Technology Edition: IBM VM messages An error occurred in shared class processing. The The operating system allows only the creator, owner, presence of the -Xshareclasses:nonfatal option or a user with administrative privileges to destroy the causes the Java VM to attempt to use the shared shared memory. cache in read-only mode. System action: System action: The Java VM continues. The Java VM attempts to attach to the shared memory User response: segment of the shared class cache in read-only mode No action is required. if it exists. JVMSHRC675E Failed to destroy shared memory User response: associated with shared class No action is required. cache. JVMSHRC671E User is not allowed to destroy the Explanation: semaphore set with semid=%d. An error occurred while destroying the shared memory Only creator or owner or user with that is associated with the shared class cache. administrative privileges can destroy the semaphore set. System action: The Java VM continues. Explanation: The operating system allows only the creator, owner, User response: or a user with administrative privileges to destroy the Contact your IBM service representative. semaphore set. JVMSHRC676E Failed to destroy shared memory System action: with shmid=%d associated with The Java VM continues. shared class cache. User response: Explanation: No action is required. An error occurred while destroying the shared memory that is associated with the shared class cache. JVMSHRC672E Failed to destroy semaphore set associated with shared class System action: cache. The Java VM continues. Explanation: User response: An error occurred while destroying the semaphore set Contact your IBM service representative. that is associated with the shared class cache. JVMSHRC677E Port layer error code = %1$d System action: Explanation: The Java VM continues. This message shows the last portable error code that User response: is stored in the J9 Port layer. This message indicates Contact your IBM service representative. the last error that was encountered. JVMSHRC673E Failed to destroy semaphore set System action: with semid=%d associated with The Java VM failed to clean up a System V IPC shared class cache. resource. Explanation: User response: An error occurred while destroying the semaphore set Contact your IBM service representative. that is associated with the shared class cache. JVMSHRC678E Platform error message: %1$s System action: Explanation: The Java VM continues. This message shows the platform-specific error code User response: and message that is related to the last error that was Contact your IBM service representative. stored in the J9 Port layer. JVMSHRC674E User is not allowed to destroy the System action: shared memory with shmid=%d. The Java VM failed to clean up a System V IPC Only creator or owner or user with resource. administrative privileges can User response: destroy the shared memory. Contact your IBM service representative. Explanation:
Chapter 1. IBM VM messages 71 JVMSHRC679E Error recovery failure: Failed to allocated to shared memory remove the semaphore set control regions has been reached. file %s associated with shared Explanation: class cache. The Java VM failed to create a new shared memory Explanation: region for the shared class cache because the system An error occurred during shared class processing. The limit was reached. Java virtual machine's attempt to remove the control System action: file as part of error recovery failed. If you specified the -Xshareclasses:nonfatal System action: option the Java VM continues without the shared class The Java VM continues. cache, otherwise the Java VM ends. User response: User response: If the Java VM fails to start, remove the control files Contact your system administrator to increase the manually. system limit on shared memory resources, or clean up any unused shared memory regions in the system then JVMSHRC680E Error recovery failure: Failed to restart the Java VM. remove the semaphore set control file %s associated with shared JVMSHRC683E System limit on the total number class cache. of open files has been reached. Explanation: Explanation: An error occurred during shared class processing. The The Java VM failed to create a new control file for the Java virtual machine's attempt to remove the control shared class cache because the system limit was file as part of error recovery failed. reached. System action: System action: The Java VM continues. If you specified the -Xshareclasses:nonfatal option and this error occurred when creating a User response: semaphore control file, the Java VM tries to use an If the Java VM fails to start, remove the control files existing shared class cache in read-only mode. If the manually. cache does not exist, the Java VM continues without JVMSHRC681E System limit for maximum number the shared class cache. If this error occurred when of semaphores or the system wide creating a shared memory control file, the Java VM maximum number of semaphores continues without the shared class cache. If you did has been reached. not specify the -Xshareclasses:nonfatal option, the Java VM ends. Explanation: The Java VM failed to create a new semaphore set for User response: the shared class cache because the system limit was Contact your system administrator to increase the reached. system limit on maximum open files, or close any unused files then restart the Java VM. System action: If you specified the -Xshareclasses:nonfatal JVMSHRC684E An error has occurred while option, the Java VM tries to use an existing shared opening semaphore. Control file class cache in read-only mode. If the cache does not could not be locked. exist, the Java VM continues without the shared class Explanation: cache. If you did not specify the - An error has occurred in shared class processing. Xshareclasses:nonfatal option, the Java VM Further messages might follow, providing more detail. ends. System action: User response: If you specified the -Xshareclasses:nonfatal Contact your system administrator to increase the option, the Java VM tries to use an existing shared system limit on semaphore resources, or clean up any class cache in read-only mode. If the cache does not unused semaphore sets in the system then restart the exist, the Java VM continues without the shared class Java VM. cache. If you did not specify the - JVMSHRC682E System limit for maximum number Xshareclasses:nonfatal option, the Java VM of shared memory regions or ends. system-wide limit on memory User response:
72 IBM SDK, Java Technology Edition: IBM VM messages Contact your IBM service representative, unless The directory path requested is bigger than the subsequent messages indicate otherwise. internal buffer space. JVMSHRC685E An error has occurred while System action: opening shared memory. Control The JVM fails to complete the operation of creating a file could not be locked. snapshot of the non-persistent shared cache. Explanation: User response: An error occurred in shared class processing. Further Use a shorter directory path or cache name. messages might follow, providing more detail. JVMSHRC698I Non-persistent shared cache \"%s System action: \" has been restored successfully If you specified the -Xshareclasses:nonfatal from the snapshot option, the Java VM continues without the shared Explanation: class cache, otherwise the Java VM ends. The non-persistent shared cache is successfully User response: restored from the snapshot. Contact your IBM service representative, unless System action: subsequent messages indicate otherwise. The JVM continues. JVMSHRC686I Failed to startup shared class User response: cache. Continue without using it No action is required. This message is only for as -Xshareclasses:nonfatal is information. specified JVMSHRC699E Failed to restore the non- Explanation: persistent shared cache \"%s\" An error occurred during shared class cache start. You from the snapshot specified the -Xshareclasses:nonfatal option, so the Java VM will continue without using the shared Explanation: class cache. An error occurred when the JVM attempted to restore the non-persistent cache. System action: The Java VM continues without the shared class System action: cache. The JVM fails to complete the operation of restoring a non-persistent shared cache from the snapshot. User response: Contact your IBM service representative to understand User response: why the shared class cache could not be started. Other messages might indicate the reason why the Previous error messages might indicate the reason. cache cannot be restored from the snapshot. JVMSHRC687E A new shared class cache cannot JVMSHRC700I Snapshot of non-persistent shared be created when running with - cache \"%s\" has been created Xshareclasses:readonly option Explanation: Explanation: The JVM successfully created the snapshot of an An error occurred during shared class cache start. The existing non-persistent shared cache. Java VM cannot create a new shared class cache when System action: the -Xshareclasses:readonly option is specified. The JVM continues. System action: User response: The Java VM ends unless you specified the - No action is required. This message is only for Xshareclasses:nonfatal option, in which case the information. Java VM continues without the shared class cache. JVMSHRC701E Failed to create a snapshot of non- User response: persistent shared cache \"%s\" Remove the readonly suboption from the - Xshareclasses option, then restart the Java VM. The Explanation: readonly suboption is useful only if the shared class An error occurred when the JVM attempted to create a cache already exists. snapshot of a non-persistent shared cache. JVMSHRC697E Failed to get a directory for the System action: shared cache The JVM fails to complete the operation of creating the snapshot of a non-persistent shared cache. Explanation: User response:
Chapter 1. IBM VM messages 73 Other messages might indicate the reason why the JVMSHRC706E Failed to acquire file lock on the snapshot failed to be created. shared cache snapshot file JVMSHRC702I Failed to get a directory for the Explanation: shared cache snapshot An error occurs when the JVM attempts to acquire a Explanation: file lock on the shared cache snapshot file. The directory path that is requested is bigger than the System action: internal buffer space. The JVM fails to complete the required operation on System action: the shared cache snapshot file. The JVM fails to complete the required operation on User response: the shared cache snapshot. Previous error messages might indicate the reason for User response: the failure. If not, contact your IBM service Use a shorter directory path or cache name. representative. JVMSHRC703E Failed to open the shared cache JVMSHRC707E Failed to acquire the mutex of snapshot file \"%s\" cache \"%s\" Explanation: Explanation: An error occurs when the JVM attempts to open the An error occurs when the JVM attempts to acquire a shared cache snapshot file. cache mutex. System action: System action: The JVM fails to complete the required operation on The JVM fails to complete the operation of creating the the shared cache snapshot file. snapshot of a non-persistent shared cache. User response: User response: Previous error messages might indicate the reason for Verify that the system has enough native resources for this failure. If this is not the case, contact your IBM the JVM. If the problem persists, contact your IBM service representative. service representative. JVMSHRC708E JVMSHRC704E Port layer error code = %1$d Failed to truncate the existing non-persistent shared cache Explanation: snapshot file \"%s\" This message shows the last portable error code that was encountered. Explanation: An error occurs when the JVM attempts to truncate System action: the non-persistent shared cache snapshot file. The JVM fails to complete the required operation on the shared cache snapshot. System action: The JVM fails to complete the operation. User response: A later message might provide more information about User response: this error code and the action that can be taken. If this Previous error messages might indicate the reason. is not the case, contact your IBM service Contact your IBM service representative. representative. JVMSHRC710E Failed to write into the non- JVMSHRC705E Platform error message: %1$s persistent shared cache snapshot file \"%s\" Explanation: This message shows the platform-specific error code Explanation: and message that relates to the last portable error An error occurs when the JVM attempts to write to a code that was encountered. This code might indicate a non-persistent shared cache snapshot file. success message, in which case there is probably no System action: associated platform error. The JVM fails to complete the operation. System action: User response: The JVM fails to complete the required operation on Previous error messages might indicate the reason for the shared cache snapshot file. the failure, for example, the disk might be full. If this is User response: not the case, contact your IBM service representative. If an appropriate action cannot be determined from JVMSHRC711E Failed to reposition the offset of the error message, contact your IBM service the file descriptor in the non- representative.
74 IBM SDK, Java Technology Edition: IBM VM messages persistent shared cache snapshot System action: file \"%s\" JVM processing continues. Explanation: User response: An error occurs when the JVM attempts to reposition Previous error messages might indicate the reason for the offset of the file descriptor in the non-persistent the failure. If this is not the case, contact your IBM shared cache snapshot file. service representative. System action: JVMSHRC717I Failed to remove current The JVM fails to complete the operation of creating the generation of shared cache snapshot of a non-persistent shared cache. snapshot \"%s\" User response: Explanation: Previous error messages might indicate the reason for The JVM is unable to remove the current generation of the failure. If this is not the case, contact your IBM the indicated shared cache snapshot. service representative. System action: JVMSHRC713E Failed to get the length of the The JVM fails to remove the snapshot of a shared shared cache snapshot file \"%s\" cache. Explanation: User response: An error occurs when the JVM attempts to obtain the Previous error messages might indicate the reason for length of the snapshot file. this failure. If this is not the case, contact your IBM service representative. System action: The JVM fails to complete the operation of destroying JVMSHRC718E Shared cache snapshot does not a shared cache snapshot. exist User response: Explanation: Previous error messages might indicate the reason for The JVM attempts to remove a shared cache snapshot the failure. If this is not the case, contact your IBM that does not exist. service representative. System action: JVMSHRC714I No shared cache snapshots The JVM ends. available User response: Explanation: No action is required. There are no snapshots present in the cacheDir that JVMSHRC719I Shared cache snapshot \"%s\" is can be processed by the command requested. destroyed System action: Explanation: Processing continues. The named shared cache snapshot is removed, as User response: requested. No action is required. System action: JVMSHRC715I Removed older generation of The JVM continues. shared cache snapshot \"%s\" User response: Explanation: No action is required. This message is only for The JVM successfully removes an older generation of information. the indicated shared cache snapshot. JVMSHRC720I Recreation of shared memory System action: control file is not allowed when JVM processing continues. creating a snapshot of the cache User response: Explanation: No action is required. This message is only for The JVM cannot create a snapshot of the shared cache information. because a valid shared cache does not exist. JVMSHRC716I Failed to remove older generation System action: of shared cache snapshot \"%s\" The JVM ends. Explanation: User response: The JVM is unable to remove the older generation of No action is required. the indicated shared cache snapshot.
Chapter 1. IBM VM messages 75 JVMSHRC721E The JVM is not configured to The JVM fails to restore a shared cache from the access the non-persistent shared snapshot. cache snapshot file \"%s\". To User response: open the file, use 'groupAccess' Contact your IBM service representative. sub-option. JVMSHRC725E The length of the non-persistent Explanation: shared cache snapshot file \"%s\" An error occurred during shared classes processing. is invalid. The length of the file is System action: %lld bytes. A valid snapshot file is The JVM fails to restore a non-persistent shared cache at least %d bytes and at most %lld from the snapshot. bytes. User response: Explanation: Modify your -Xshareclasses: option to add the The length of the file is not valid groupAccess suboption and try again. The snapshot System action: might have been created by another user in the same The JVM fails to restore a non-persistent shared cache group as the current user. from the snapshot. JVMSHRC722E The JVM does not permit access to User response: the shared cache snapshot file Check that the file is a valid shared cache snapshot \"%s\" because the JVM process's file. user ID and group ID are different from the shared cache snapshot JVMSHRC726E Non-persistent shared cache \"%s file owner's user ID and group ID, \" already exists. It cannot be and the JVM process's user ID restored from the snapshot. does not belong to the shared Explanation: cache snapshot file owner's group. Only a new non-persistent shared cache can be Explanation: restored from a snapshot. An error occurred during shared classes processing. System action: System action: The JVM fails to restore a non-persistent shared cache The JVM fails to restore a non-persistent shared cache from the snapshot. from the snapshot. User response: User response: Check that the non-persistent cache does not exist Specify a different cache name or directory. This before restoring the cache from the snapshot. action avoids a conflict with an existing shared cache JVMSHRC727E An error has occurred in creating snapshot that was created by another user that is not the new non-persistent shared in the same group. cache JVMSHRC723E The JVM could not check the Explanation: permissions of the shared cache The JVM cannot start the new cache. snapshot file \"%s\" System action: Explanation: The JVM fails to restore a non-persistent shared cache An error occurred during shared classes processing. from the snapshot. System action: User response: The JVM fails to restore a non-persistent shared cache Verify that the system has enough native resources for from the snapshot. the JVM. If the problem persists, contact your IBM User response: service representative. Contact your IBM service representative. JVMSHRC728E Failed to read the non-persistent JVMSHRC724E Shared cache snapshot file \"%s\" shared cache snapshot file \"%s\" does not exist Explanation: Explanation: An error occurs when reading the non-persistent The shared cache snapshot file is not found on the shared cache snapshot file. disk. System action: System action: The JVM fails to restore a non-persistent shared cache from the snapshot.
76 IBM SDK, Java Technology Edition: IBM VM messages User response: JVMSHRC732I The JVM can store classpaths into Previous error messages might indicate the reason for the shared cache created with '- the error. If this is not the case, contact your IBM Xshareclasses:restrictClasspaths' service representative. option JVMSHRC729E The snapshot was created by a Explanation: different JVM build and doesn't The JVM can store class paths into the shared cache match the running JVM because the -Xshareclasses:allowClasspaths Explanation: option is also specified. An error occurs when the JVM attempts to start the System action: restored cache. The build ID in the snapshot is The JVM continues. different from the ID of the current JVM. User response: System action: No action is required. This message is only for The JVM fails to restore a non-persistent shared cache information. from the snapshot. JVMSHRC733I The JVM cannot store classpaths User response: into the shared cache, since the Use a JVM that matches the snapshot, or destroy the cache was created with the '- snapshot. Xshareclasses:restrictClasspaths' option JVMSHRC730I The JVM has created shared cache with '- Explanation: Xshareclasses:restrictClasspaths' The JVM attaches to an existing shared cache created option. Subsequent JVM with the -Xshareclasses:restrictClasspaths invocations will not be able to option. store classpaths into the shared System action: cache The JVM continues. Explanation: User response: When the -Xshareclasses:restrictClasspaths No action is required. This message is only for option is used, subsequent JVMs cannot store class information. paths into the shared cache unless they are running with the -Xshareclasses:allowClasspaths JVMSHRC735I Use a %d-bit JVM to perform the option. requested operation on the %d-bit System action: shared cache \"%s\" as the %d- The JVM continues. bit JVM cannot verify that the shared memory was created by User response: the JVM No action is required. This message is only for information. Explanation: The JVM cannot verify the size of the shared cache. JVMSHRC731I The JVM has ignored '- The requested operation is not carried out to avoid Xshareclasses:restrictClasspaths' accidental access to shared memory of another option as the existing shared application. cache was created without '- System action: Xshareclasses:restrictClasspaths' The JVM continues. option Explanation: User response: -Xshareclasses:restrictClasspaths is You must use a JVM that has the same address mode applicable only when the JVM is initializing a new as the shared cache to carry out the requested shared cache. operation. System action: JVMSHRC743E Invalid method specification(s) for The JVM continues. option \"%s\" User response: Explanation: For this option to be effective you must remove the The method specification provided was not existing shared cache and restart the JVM. recognized. System action:
Chapter 1. IBM VM messages 77 The JVM ends. User response: Previous messages might indicate the reason for this User response: error. Contact your IBM service representative. Specify a valid method specification and try again. JVMSHRC749E Failed to find the AOT method(s) JVMSHRC744I Invalidated the %d AOT method(s) Explanation: Explanation: An error occurred while attempting the requested Successfully found the AOT method(s) and performed operation on the AOT method. the required operation. System action: System action: The JVM ends. The JVM ends. User response: User response: Previous messages might indicate the reason for this No action is required. This message is for information error. Contact your IBM service representative. only. JVMSHRC750I No AOT methods match the JVMSHRC745I Revalidated the %d AOT method specification(s) method(s) Explanation: Explanation: There are no AOT methods in the cache that match the Successfully found the AOT method and performed method specification. the required operation. System action: System action: The JVM ends. The JVM ends. User response: User response: No action is required. No action is required. This message is for information only. JVMSHRC751E Failed to parse the method specifications. No more than %d JVMSHRC746I Found the %d AOT method(s) method specifications are Explanation: allowed. Successfully found the AOT method and performed Explanation: the required operation. Too many method specifications are specified. System action: System action: The JVM ends. The JVM ends. User response: User response: No action is required. This message is for information Reduce the number of method specifications and try only. again. The maximum limit is 64. JVMSHRC747E Failed to invalidate the AOT JVMSHRC752E Failed to parse the method method(s) specification(s) Explanation: Explanation: An error occurred while performing the requested An error occurred while parsing the method operation on the AOT method. specification. System action: System action: The JVM ends. The JVM ends. User response: User response: Previous messages might indicate the reason for the Correct the format of the method specification and try error. Contact your IBM service representative. again. JVMSHRC748E Failed to revalidate the AOT JVMSHRC753E Failed to get the cache write method(s) mutex Explanation: Explanation: An error occurred while attempting the requested An error occurred when acquiring the write mutex of operation on the AOT method. the cache. System action: System action: The JVM ends.
78 IBM SDK, Java Technology Edition: IBM VM messages The JVM ends. Cannot set the group access permission when creating the new shared memory with sub-option User response: groupAccess. Verify that the system has enough native resources for the JVM to work properly. If the problem persists, System action: contact your IBM service representative. The JVM continues. JVMSHRC754I Recreation of shared memory User response: control file is not allowed. Ensure that the user has sufficient permission for creating the new shared memory with group access. Explanation: The required operation cannot complete because a JVMSHRC759 Failed to set group access valid shared cache does not exist. W permission as requested by the 'groupAccess' sub-option on the System action: semaphore control file associated The JVM ends. with shared class cache. User response: Explanation: None required. Cannot set the group access permission when creating JVMSHRC756 Failed to set group access the new control file with sub-option groupAccess. W permission on the shared cache This problem might be caused by the setting umask file as requested by the incorrectly. 'groupAccess' sub-option. System action: Explanation: The VM continues. Cannot set the group access permission when creating User response: the new cache with sub-option groupAccess. This Check the umask setting and ensure that the user has problem might be caused by setting umask incorrectly. sufficient permission for creating the semaphore System action: control file with group access. The JVM continues. JVMSHRC760 Failed to set group access User response: W permission as requested by the Check the umask setting and ensure that the user has 'groupAccess' sub-option on the sufficient permission for creating the new cache with shared memory control file group access. associated with shared class cache. JVMSHRC757 Failed to set group access W permission as requested by the Explanation: 'groupAccess' sub-option on the Cannot set the group access permission when creating semaphore set with semid=%d the new control file with sub-option groupAccess. associated with shared class This problem might be caused by the setting umask cache. incorrectly. Explanation: System action: Cannot set the group access permission when creating The VM continues. the new semaphore with sub-option groupAccess. User response: System action: Check the umask setting and ensure that the user has The JVM continues. sufficient permission for creating the shared memory control file with group access. User response: Ensure the user has sufficient permission for creating JVMSHRC761 Failed to set group access the new semaphore with group access. W permission as requested by the 'groupAccess' sub-option on the JVMSHRC758 Failed to set group access shared cache snapshot file. W permission as requested by the 'groupAccess' sub-option on the Explanation: shared memory with shmid=%d Cannot set the group access permission when creating associated with shared class the snapshot of a non-persistent shared cache with cache. sub-option groupAccess. This problem might be caused by setting the umask incorrectly. Explanation: System action:
Chapter 1. IBM VM messages 79 The VM continues. Memory pages of the cache that contain runtime data, string read/write data, and partially filled pages, are User response: protected. Check the umask setting and ensure that the user has sufficient permission for creating the shared memory System action: control file with group access. If any protected page of the cache is accessed illegally, the Java VM crashes. JVMSHRC762E Error getting stats of the shared class cache file when verifying its User response: group access permission. No action required. Explanation: JVMSHRC766I Memory page protection on An error has occurred during shared classes runtime data and partially filled processing. pages is successfully enabled System action: Explanation: The JVM ends, unless you have specified the nonfatal Memory pages of the cache that contain runtime data option with -Xshareclasses:nonfatal, in which and partially filled pages are protected. case the JVM continues without using shared classes. System action: User response: If any protected page of the cache is accessed Contact your IBM service representative. illegally, the Java VM crashes. JVMSHRC763E All shared classes sub-options in User response: total should not be longer than %u No action required. chars. JVMSHRC767I Memory page protection on Explanation: runtime data and string read-write The -Xshareclasses sub-options exceed the data is successfully enabled maximum length. Explanation: System action: Memory pages of the cache that contain runtime data The JVM ends, unless you have specified the nonfatal and string read/write data are protected. option with -Xshareclasses:nonfatal, in which System action: case the JVM continues without using shared classes. If any protected page of the cache is accessed User response: illegally, the Java VM crashes. Ensure the -Xshareclasses sub-options are not User response: longer than the maximum length and retry. No action required. JVMSHRC764E Unable to create shared memory JVMSHRC768I Memory page protection on of size %1$d bytes as requested runtime data is successfully \n \ enabled Explanation: Explanation: The system has not been able to create a shared class Memory pages of the cache that contain runtime data cache of the size requested (1$). A cache of the are protected. maximum size permitted on your system (2$) is created instead. This message is specific to Linux System action: systems. If any protected page of the cache is accessed illegally, the JVM will crash. System action: The JVM continues. User response: No action required. User response: If you require a larger cache, destroy this cache, JVMSHRC769I The JVM has enabled shared increase the value of SHMMAX, and re-create the cache partial page protection as cache. the existing shared cache was created with partial page JVMSHRC765I Memory page protection on protection enabled. runtime data, string read-write data and partially filled pages is Explanation: successfully enabled The Java VM is attached to an existing shared cache, which was created with partial protection enabled. Explanation: Any Java VM attaching to an existing shared cache
80 IBM SDK, Java Technology Edition: IBM VM messages enables partial page protection, irrespective of Increase the -Xsoftmx limit if the user wants more command line options. data to be added to the shared cache. System action: JVMSHRC772I The softmx limit for shared cache The Java VM protects both partially filled pages and \"%s\" usage is reached. Use full pages in the shared class cache. option \"%s\" to increase the softmx limit. User response: Remove the existing shared cache and restart the Java Explanation: VM. This action makes the - The -Xsoftmx limit set for shared cache usage has Xshareclasses:mprotect=nopartialpages or - been reached and no data can be added to the shared Xshareclasses:mprotect=none option effective. cache. JVMSHRC770I The JVM has disabled protecting System action: partially filled pages. If - The JVM continues. The named shared cache is still Xshareclasses:mprotect=onfi operational and continues to provide increased nd is specified, it is also ignored. performance for loading the classes it contains. However, classes not contained in the cache will Explanation: always be loaded from their source. The Java VM is attached to an existing shared cache that was created with the - System action: Xshareclasses:mprotect=nopartialpages Increase the -Xsoftmx limit if user wants more data option. Any JVM attaching to this type of cache to be added to the shared cache. disables partial page protection, irrespective of JVMSHRC773I The space for AOT data in shared command line options. cache \"%s\" is full. System action: Explanation: The Java VM protects only full pages in the shared The space for AOT data in the named shared class class cache. Partially filled pages are not protected. cache is full and no further AOT data can be added to User response: it. If the shared cache is not full, either the maximum Remove the existing shared cache and restart the Java space allowed for AOT data or the -Xsoftmx limit set VM. By default, the Java VM protects partially filled for shared cache usage is reached. pages in the shared cache after the startup phase. System action: JVMSHRC771I Enable memory protection of The JVM continues. The named shared cache is still partially filled pages. On z/OS it is operational and continues to provide increased equivalent to performance for loading the classes it contains. 'partialpagesonstartup'. However, no more AOT compiled methods can be added to the cache. Explanation: The -Xsoftmx limit set for shared cache usage has User response: been reached and no data can be added to the shared If the shared cache is not full, the maximum space cache. allowed for AOT data can be increased by using the - Xshareclasses:adjustmaxaot option. If the - System action: Xsoftmx limit for shared cache usage is reached, you The JVM continues. The named shared cache is still can increase it by using the - operational and continues to provide increased Xshareclasses:adjustsoftmx option. You can performance for loading the classes it contains. also increase the minimum space reserved for AOT However, classes not contained in the cache will data by using the -Xshareclasses:adjustminaot always be loaded from their source. option. User response:
TRCE messages Trace engine messages. JVMTRCE000E Trace option unrecognized: - An option used with the -Xtrace parameter is not Xtrace:%s known. Explanation: System action: The JVM ends.
Chapter 1. IBM VM messages 81 User response: System action: Use -Xtrace:help to find the correct syntax for the - The JVM continues but trace data is not written to this Xtrace option and try again. file. JVMTRCE001E Error processing trace option: - User response: Xtrace:%s If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. Explanation: An option used with the -Xtrace parameter could not JVMTRCE006W Error writing %d bytes to trace be processed correctly due to a syntax error. file: %s rc: %d System action: Explanation: The JVM ends. The specified trace file could not be written to. User response: System action: Use -Xtrace:help to find the correct syntax for the - The JVM continues but trace data is not written to this Xtrace option and try again. file. JVMTRCE002E Error processing trace option: - User response: Xtrace:%s=%s If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. Explanation: An option used with the -Xtrace parameter could not JVMTRCE007W Error opening next trace file be processed correctly due to a problem with the generation: %s option or the arguments used. Explanation: System action: The specified trace file could not be opened when the The JVM ends. JVM attempted to open the next trace file in a cycle of generational trace files. User response: Use -Xtrace:help to find the correct syntax for the - System action: Xtrace option and try again. The JVM continues but trace data is not written to this file. JVMTRCE003E Error processing trace option, detail: %s User response: If you need to collect the trace data, restart the JVM Explanation: specifying a trace file that can be opened. An option used with the -Xtrace parameter could not be processed correctly due to the problem described JVMTRCE008W Error performing seek in tracefile: in the detail string. %s System action: Explanation: The JVM ends. The JVM could not find an expected location in the specified trace file. User response: Use -Xtrace:help to find the correct syntax for the - System action: Xtrace option and try again. The JVM continues but trace data is not written to this file. JVMTRCE004W Error opening trace file: %s User response: Explanation: If you need to collect the trace data, restart the JVM The specified trace file could not be opened. specifying a trace file that can be opened. System action: JVMTRCE009W Error writing to snap file The JVM continues but trace data is not written to this file. Explanation: The JVM could not write trace data to a snap file while User response: the JVM was running. If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. System action: The JVM continues but trace data is not written to this JVMTRCE005W Error writing header to trace file: file. %s User response: Explanation: If you need to collect the trace data, restart the JVM The specified trace file could not be written to. specifying a trace file that can be opened.
82 IBM SDK, Java Technology Edition: IBM VM messages JVMTRCE010W Native memory allocation failure, JVMTRCE014E Trace engine initialization failed, falling back to nodynamic trace trace not enabled settings. Explanation: Explanation: The JVM cannot start the trace engine. The JVM could not allocate space for another trace System action: buffer. The JVM ends. System action: User response: The JVM continues but trace reuses existing buffers. Contact your IBM service representative. You might Trace points that are not written to disk before a new need to obtain additional information by running with buffer is required might be lost. -Xtrace:debug=
Chapter 1. IBM VM messages 83 JVMTRCE019E Trace engine failed to initialize Explanation: properly, RC = %d A timeout occurred during JVM shutdown while the trace engine is waiting for trace subscriber threads to Explanation: finish. The JVM could not initialize. System action: System action: The JVM ends without waiting for trace subscriber The JVM ends. threads to finish. User response: User response: Contact your IBM service representative. Contact your IBM service representative. JVMTRCE020W Timeout occurred during trace engine termination
VERB messages Verbose messages. JVMVERB000I Verbose stack: "%2$.*1$s" used JVMVERB004E Error: -Xverbosegclog number of %3$zd/%4$zd bytes on Java/C cycles must be greater than 0 stacks Explanation: Explanation: Either you specified the -Xverbosegclog parameter Indicates how much stack is used on each stack for a with a value of 0 for the number of cycles, or the thread when you specify the -verbose:stack parameter could not be parsed. parameter. System action: System action: The JVM ends. None. User response: User response: Use a value greater than 0 for the number of cycles. This message is an information message. No action is JVMVERB005E Error: -Xverbosegclog missing required. filename JVMVERB002I Verbose stack: maximum stack Explanation: use was %1$zd/%2$zd bytes on You used the -Xverbosegclog parameter without Java/C stacks specifying a file name. Explanation: System action: Indicates the largest stack usage for each stack for all The JVM ends. threads when you specify the -verbose:stack parameter. User response: Specify a valid file name when using the - System action: Xverbosegclog parameter. None. JVMVERB018 Invalid classpath entry: %s (file User response: W I/O failed) This message is an information message. No action is required. Explanation: The JVM could not open the specified .zip file. The JVMVERB003E Error: -Xverbosegclog number of file might not exist or the file permissions might not files must be greater than 0 allow access by the JVM. Explanation: System action: Either you specified the -Xverbosegclog parameter The JVM either ignores the issue or throws a with a value of 0 for the number of files, or the java/io/IOException exception. parameter could not be parsed. User response: System action: Check that the specified .zip file exists and has The JVM ends. appropriate permissions. User response: JVMVERB019 Invalid classpath entry: %s (file Use a number greater than 0 for the number of files. W read failed)
84 IBM SDK, Java Technology Edition: IBM VM messages Explanation: JVMVERB024 Invalid classpath entry: %s (jxe The JVM could not read part of the specified .zip file. W missing rom.classes) The file might be corrupt or truncated. Explanation: System action: A rom.classes entry could not be found in the The JVM either ignores the issue or throws a specified JXE file. java/io/IOException exception. System action: User response: The JVM either ignores the issue or throws a If the .zip file is corrupt or truncated, replace it with java/io/IOException exception. a valid copy. User response: JVMVERB020 Invalid classpath entry: %s (file Replace the JXE file with a valid copy that contains a W corrupt) rom.classes entry. Explanation: JVMVERB025 Invalid classpath entry: %s (jxe The specified .zip file is corrupt. W corrupt image header) System action: Explanation: The JVM either ignores the issue or throws a The specified JXE file had a corrupt header. java/io/IOException exception. System action: User response: The JVM either ignores the issue or throws a Replace the corrupt .zip file with a valid copy. java/io/IOException exception. JVMVERB021 Invalid classpath entry: %s User response: W (unsupported file type) Replace the corrupt JXE file with a valid copy. Explanation: JVMVERB026 Invalid classpath entry: %s The specified .zip file type is unsupported W (opposite endian jxe not System action: supported) The JVM either ignores the issue or throws a Explanation: java/io/IOException exception. The Endian nature of the specified JXE file was not User response: correct for this platform. Replace the specified .zip file with a supported .zip System action: file type. The JVM either ignores the issue or throws a java/io/IOException exception. JVMVERB022 Invalid classpath entry: %s W (unknown file type) User response: Explanation: Replace the JXE file with one of the correct The specified .zip file type is unknown. endianness. System action: JVMVERB027I Verbose stack: Running thread The JVM either ignores the issue or throws a "%2$.*1$s" is using %3$zd/ java/io/IOException exception. %4$zd bytes on Java/C stacks User response: Explanation: Replace the specified .zip file with a .zip file of a Indicates how much memory was used for the Java supported type. and C stacks for a thread. This message is issued when you specify the -verbose:stack parameter. JVMVERB023 Invalid classpath entry: %s System action: W (unknown error) The JVM continues. Explanation: An unexpected error occurred while reading the User response: specified .zip file. This message is for information only. No action is required. System action: The JVM either ignores the issue or throws a JVMVERB028I Verbose stack: Unable to print the java/io/IOException exception. stack info for currently running threads User response: If the problem persists, contact your IBM Service Explanation: representative.
Chapter 1. IBM VM messages 85 The JVM was unable to obtain a lock for the currently User response: running threads. This message is for information only. No action is required. System action: The JVM continues.
VMUT messages JVM utility messages. JVMVMUT003 Options file not found The JAVA_TOOL_OPTIONS environment variable W contains a token within quotation marks, but the closing quotation mark is missing. Explanation: You used the -Xoptionsfile parameter to specify System action: an options file, but the file could not be opened. The JVM ends. System action: User response: The JVM ignores the specified options file. Correct the JAVA_TOOL_OPTIONS environment variable. User response: Correct the command-line parameter. JVMVMUT008E Malformed value for IBM_JAVA_OPTIONS JVMVMUT004 Malformed option: '%s' W Explanation: The IBM_JAVA_OPTIONS environment variable Explanation: contains a token within quotation marks, but the The specified option could not be parsed. closing quotation mark is missing. System action: System action: The JVM ignores the option. The JVM ends. User response: User response: Correct the command-line option. Correct the IBM_JAVA_OPTIONS environment JVMVMUT005 Option too large: '%s' variable. W JVMVMUT009E Malformed value for -Xservice Explanation: Explanation: The specified option is larger than the maximum The -Xservice command-line option contains a permitted value. token within quotation marks, but the closing System action: quotation mark is missing. The JVM ignores the option. System action: User response: The JVM ends. Correct the command-line option. User response: JVMVMUT006E Malformed option %s found in - Correct the command-line option. Xoptionsfile JVMVMUT010 Malformed option value, option Explanation: W "%1$s%3$.*2$s" contains trailing You used the -Xoptionsfile parameter to specify a characters "%4$s" which have file. The file contains a token within quotation marks, been ignored but the closing quotation mark is missing. Explanation: System action: The specified option value could not be parsed. The JVM ends. System action: User response: The JVM ignores the option value. Add the missing quotation mark to the file that is User response: specified by the -Xoptionsfile parameter. Correct the command-line option. JVMVMUT007E Malformed value for JVMVMUT011E Could not allocate memory for JAVA_TOOL_OPTIONS command line option array Explanation:
86 IBM SDK, Java Technology Edition: IBM VM messages Explanation: JVMVMUT013E Options file %s invalid The JVM tried to allocate memory to copy command- line options, but failed. Explanation: An options file specified with the -Xoptionsfile System action: option cannot be opened or is too large. The JVM ends. System action: User response: The JVM ends. Check the available memory in your process or system. Increase the memory that is available to start User response: the JVM, then try again. Check the size and contents of the option file.
ZIPS messages Compressed file messages. JVMZIPS000W Unable to open %1$s (%2$s) Explanation: The JVM attempted to find an exported symbol in the Explanation: J9 zlib library, but the operation failed. The JVM attempted to load the J9 zlib library, but the operation failed. System action: The JVM ends. System action: The JVM ends. User response: Restore the file from a copy of the JVM, then start the User response: JVM again. Restore the file from a copy of the JVM, then start the JVM again. JVMZIPS001W Unable to open %s (Missing export)
Chapter 1. IBM VM messages 87 88 IBM SDK, Java Technology Edition: IBM VM messages Notices
This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 US For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 US
© Copyright IBM Corp. 2011, 2020 89 Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_.
Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Intel, Intel logo, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries.
Terms and conditions for product documentation Permissions for the use of these publications are granted subject to the following terms and conditions.
90 Notices Applicability These terms and conditions are in addition to any terms of use for the IBM website.
Personal use You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.
Commercial use You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.
Rights Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON- INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
IBM Online Privacy Statement IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below. This Software Offering does not use cookies or other technologies to collect personally identifiable information. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of various technologies, including cookies, for these purposes, see: (i) IBM’s Privacy Policy at https://www.ibm.com/privacy ; (ii) IBM’s Online Privacy Statement at https:// www.ibm.com/privacy/details (in particular, the section entitled “Cookies, Web Beacons and Other Technologies”); and (iii) the “IBM Software Products and Software-as-a-Service Privacy Statement” at https://www.ibm.com/software/info/product-privacy.
Notices 91 92 IBM SDK, Java Technology Edition: IBM VM messages
IBM®