IBM SDK, Java Technology Edition Version 1. IBM JVM messages IBM

Transcription

1 IBM SDK, Java Technology Edition Version 1 IBM JVM messages IBM

2

3 IBM SDK, Java Technology Edition Version 1 IBM JVM messages IBM

4 Note Before you use this information and the product it supports, read the information in Notices on page 93. Copyright information This edition of the IBM JVM 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, 2016, Oracle and/or its affiliates. Copyright IBM Corporation 2011, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Preface v IBM JVM messages CDRT messages DUMP messages EXEL messages EXEX messages J9CL messages J9GC messages J9RI messages J9TI messages J9VM messages JITM messages JNCK messages MECK messages OFFC messages PORT messages SHRC messages TRCE messages VERB messages VMUT messages ZIPS messages Notices Trademarks Terms and conditions for product documentation.. 95 IBM Online Privacy Statement Copyright IBM Corp. 2011, 2016 iii

6 iv IBM SDK, Java Technology Edition: IBM JVM messages

7 Preface This guide lists messages that are generated by the IBM Java Virtual Machine (JVM). Copyright IBM Corp. 2011, 2016 v

8 vi IBM SDK, Java Technology Edition: IBM JVM messages

9 IBM JVM messages CDRT messages The Java Virtual Machine (JVM) used by the IBM Software Developers Kit (SDK) is the IBM J9 virtual machine. Messages are issued by the IBM JVM in response to certain conditions. These IBM messages, error codes, and exit codes apply to multiple versions of the JVM. There are three main types of message: Information Information messages provide information about JVM For example, a dump information message is typically issued when a dump agent requests a Java technology dump. Warning Warning messages are issued by the JVM to indicate conditions that might need user intervention. Error Error messages are issued by the JVM when normal processing cannot proceed, because of unexpected conditions. IBM JVM messages have the following format: JVMTYPENUM&, where: v JVM is a standard prefix. v TYPE refers to the JVM subcomponent that issued the message. v NUM is a numerical number. v & is one of the following codes: I Information message W Warning message E Error message IBM JVM messages can help you with problem determination. Refer to diagnostic information for more detailed information about diagnosing problems with the IBM JVM. Codert module messages. This section details messages that are generated by the IBM JVM codert module: v JVMCDRT000E v JVMCDRT001E v JVMCDRT002E on page 2 JVMCDRT000E Unable to locate JIT stack map - aborting VM JIT metadata could not be found when traversing Java stacks. JVMCDRT001E Method: %2$.*1$s.%4$.*3$s%6$.*5$s (%7$p) Copyright IBM Corp. 2011,

10 JVMCDRT002E JIT metadata could not be found when traversing Java stacks. JIT metadata could not be found when traversing Java stacks. JVMCDRT002E Failing PC: %1$p (offset %2$p), metadata = %3$p DUMP messages Dump agent messages. This section details messages that are generated by dump agent processing: v JVMDUMP000E on page 3 v JVMDUMP001E on page 3 v JVMDUMP002W on page 3 v JVMDUMP003E on page 3 v JVMDUMP004E on page 3 v JVMDUMP005E on page 3 v JVMDUMP006I on page 3 v JVMDUMP007I on page 3 v JVMDUMP009I on page 3 v JVMDUMP010I on page 3 v JVMDUMP011I on page 3 v JVMDUMP012E on page 4 v JVMDUMP013I on page 4 v JVMDUMP014E on page 4 v JVMDUMP015I on page 4 v JVMDUMP016I on page 4 v JVMDUMP017I on page 4 v JVMDUMP018W on page 4 v JVMDUMP019I on page 4 v JVMDUMP020I on page 4 v JVMDUMP022W on page 4 v JVMDUMP023W on page 4 v JVMDUMP024W on page 5 v JVMDMP025I on page 5 v JVMDUMP026 on page 5 v JVMDUMP027W on page 5 v JVMDUMP028W on page 5 v JVMDUMP029W on page 5 v JVMDUMP030W on page 5 v JVMDUMP031W on page 5 v JVMDUMP032I on page 6 v JVMDUMP033I on page 6 v JVMDUMP034I on page 6 2 IBM SDK, Java Technology Edition: IBM JVM messages

11 JVMDUMP000E JVMDUMP011I v JVMDUMP035I on page 6 v JVMDUMP036I on page 6 v JVMDUMP037E on page 6 v JVMDUMP038E on page 6 v JVMDUMP039I on page 6 v JVMDUMP040I on page 6 v JVMDUMP041I on page 6 v JVMDUMP042W on page 7 JVMDUMP000E Dump option unrecognized: -Xdump:%s An option used with the -Xdump parameter is unknown. Use -Xdump:help to find the correct syntax for the -Xdump options. JVMDUMP001E Dump event unrecognized:...%s The event name provided with the -Xdump parameter is unknown. Use -Xdump:events to find the supported set of event names. JVMDUMP002W Token unrecognized: %%%1$c An unidentified token was found in the dump label. Use -Xdump:tokens to find the supported set of tokens. JVMDUMP003E Dump agent unrecognized: %s An unsupported dump type has been requested. Use -Xdump:help to find the supported set of dump types. JVMDUMP004E Missing file name The dump file name could not be found. The dump cannot be written. Provide a valid filename for the dump. JVMDUMP005E Missing external tool The executable file for the tool could not be found. The tool cannot run. Provide a valid path and filename for the executable file. JVMDUMP006I Processing dump event \"%1$s\", detail \"%3$.*2$s\" - please wait. handled. A dump event has occurred and is being The JVM attempts to process the event. No response is required. JVMDUMP007I JVM Requesting %1$s dump using '%2$s' The JVM is about to write a dump. The dump might have been triggered by an event, such as an exception, or requested using JVMTI, JVMRI, -Xtrace:trigger or the com.ibm.jvm.dump Java API. The JVM attempts to write the dump. A second message is generated when the dump is complete. Review the dump and take appropriate action. JVMDUMP009I %s dump not available The specified dump type is not currently available. For example, a JVM trace snap dump has been requested, but JVM trace is not enabled. The JVM does not write the dump. This message is only for information. JVMDUMP010I %1$s dump written to %2$s location. The dump was written to the specified To understand how to interpret a Java dump file, refer to diagnostic information. JVMDUMP011I %1$s dump created process %2$d A tool dump process has been created. IBM JVM messages 3

12 JVMDUMP012E JVMDUMP023W The JVM runs the executable process specified for the tool dump. Any parameters are passed to the process. Refer to the documentation for the tool creating the dump process. JVMDUMP012E Error in %1$s dump:%2$s The JVM detected an error while attempting to produce a dump. The JVM continues, but the dump might not be usable. Refer to diagnostic information or contact your local IBM service JVMDUMP013I Processed dump event \"%1$s\", detail "%3$.*2$s". handled. A dump event occurred and has been Refer to other messages issued by the JVM for the location of the dump file, or for other actions required. JVMDUMP014E VM Action unrecognized:...%s A specified dump request action was not understood by the JVM. and ends. The JVM produces help information Use -Xdump:request to check that your request is valid. JVMDUMP015I Aborting: Cannot open or read (%s) read mode. JVMDUMP016I The JVM cannot open a dump file in INTERNAL USE ONLY INTERNAL USE ONLY Aborting: Cannot create file (%s) An attempt by the JVM to open a new file has failed. INTERNAL USE ONLY INTERNAL USE ONLY JVMDUMP017I Aborting: Cannot compress file (%s) The JVM cannot compress a file. INTERNAL USE ONLY INTERNAL USE ONLY JVMDUMP018W Requested event is not available: run with -Xdump:dynamic flag A dump has been requested on an event type that is not supported. INTERNAL USE ONLY INTERNAL USE ONLY JVMDUMP019I JVM requesting %s dump A dump file of the type specified has been requested. The JVM attempts to produce a dump of the specified type. Wait for a message indicating that the dump is complete. JVMDUMP020I %s dump has been written A dump file of the type specified has been written. To understand how to interpret the dump file, refer to Java diagnostic information. JVMDUMP022W The requested heap compaction has not been performed because exclusive access was not requested or could not be obtained. The garbage collector could not run because the gc thread did not have exclusive access to the heap. The dump file is not produced. Modify the -Xdump option to request exclusive access. See the Java diagnostic information for valid dump request types. JVMDUMP023W The requested heap preparation has not been performed because exclusive access was not requested or could not be obtained. The dump thread must lock the heap to prevent changes while the dump is taken. Either no attempt was made to obtain the lock or the lock could not be obtained. The JVM does not produce the specified dump. Modify the -Xdump option to request exclusive access. See the Java diagnostic information for valid dump request types. 4 IBM SDK, Java Technology Edition: IBM JVM messages

13 JVMDUMP024W JVMDUMP031W JVMDUMP024W Multiple heapdumps were requested but %%id is missing from file label:. Dumps will overwrite The JVM replaces the %%id insertion point with a unique number. Because %%id is missing the replacement cannot take place, causing a potential file name clash and file overwrite. The JVM informs the user and produces dumps as requested. If you do not want files overwritten, specify a file label that includes the %%id. JVMDMP025I IEATDUMP failure for DSN='%s' RC=0x%08X RSN=0x%08X An IEATDUMP was requested but could not be produced. The JVM will output the message on the operator console. Check the response code provided in the error using the Diagnostics Guide or the z/os V1R7.0 MVS Authorized Assembler Services Reference, Return and Reason Codes. JVMDUMP026 IEATDUMP Name exceeding maximum allowed length. Default name used. The file label exceeded the maximum length for file names on z/os. The dump file is not produced. Refer to Java diagnostic information for information about producing dumps on z/os. JVMDUMP027W The requested heapdump has not been produced because another component is holding the VM exclusive lock. The exclusive VM lock must be held to produce a usable heapdump. Although the VM exclusive lock was requested by the user, the VM could not obtain the lock in a reasonable time. This behavior avoids risking a deadlock. heapdump. The VM does not produce a Wait for 1 minute and try taking the heapdump again when the VM exclusive lock might be free. JVMDUMP028W The VM exclusive lock could not be acquired before taking the system dump. Although the VM exclusive lock was requested by the user, the VM could not obtain the lock in a reasonable time before taking the system dump. This behavior avoids risking a deadlock. The VM produces a system dump without taking the VM exclusive lock. The dump might show an inconsistent view of the VM data structures and heap. Wait for 1 minute and try taking the system dump again when the VM exclusive lock might be free. JVMDUMP029W The request for prepwalk or compact before taking a system dump will be ignored because the VM exclusive lock was not requested. The user requested the prepwalk or compact options before taking a system dump, but did not request the VM exclusive lock. These actions require the exclusive VM lock. The system dump is taken without running prepwalk or compact. Modify the -Xdump:system parameter to include the exclusive request option. For example: -Xdump:system:events=user,request=exclusive+ compact+prepwalk JVMDUMP030W Cannot write dump to file %s: %s The JVM was unable to write a dump to the specified file. There might be multiple causes, including insufficient file system permissions or specifying a file path that does not exist. The JVM uses a default file name. The name and location of the file are indicated by the messages produced when the dump is written. Correct the problem with the specified file path or change the target dump file with the file= option. JVMDUMP031W The requested heapdump has not been produced because the VM exclusive lock was not requested. Add request=exclusive+prepwalk+compact to your -Xdump:heap: command line option. A heapdump dump agent was configured using the -Xdump option or JVMTI without requesting that the exclusive VM lock. The JVM does not take the heapdump because the dump might be corrupted without the VM exclusive lock in place. IBM JVM messages 5

14 JVMDUMP032I JVMDUMP041I Change the -Xdump:heap: option to include the request=exclusive option. For example: -Xdump:heap:events=user,request=exclusive JVMDUMP032I JVM requested %1$s dump using '%2$s' in response to an event The JVM writes a dump because an event, such as an exception, was triggered. The JVM attempts to write the dump. A second message is produced when the dump is complete. Review the dump and take appropriate action. JVMDUMP033I JVM requested %1$s dump in response to an event The JVM writes a dump because an event, such as an exception, has been triggered. The JVM attempts to write the dump. A second message is produced when the dump is complete. Review the dump and take appropriate action. JVMDUMP034I User requested %1$s dump using '%2$s' through %3$s The JVM writes a dump in response to a request through an API, such as JVMTI, or through the -Xtrace:trigger option. The JVM attempts to write the dump. A second message is produced when the dump is complete. Review the dump and take appropriate action. JVMDUMP035I User requested %1$s dump through %2$s The JVM writes a dump in response to a user request through an API, such as JVMTI, or through the -Xtrace:trigger option. The JVM attempts to write the dump. A second message is produced when the dump is complete. Review the dump and take appropriate action. valid filter. Modify the dump option to include a JVMDUMP037E Error in %1$s dump: %2$s failed, error code: %3$d An error has occurred in a JVM dump agent. An operating system call used by the agent has failed. Check preceding JVM messages. The JVMDUMP007I message includes the command string supplied for tool dumps. Check that the command string is correct. JVMDUMP038E Snap dump is not written because tracing to file: %1$s Snap dumps are not produced when a trace output file is in use. message. Use the trace file specified in the JVMDUMP039I Processing dump event \"%1$s\", detail \"%3$.*2$s\" at %4$s - please wait. A dump event is being handled. The JVM generates dumps as configured for the event by the -Xdump option. No action is required. JVMDUMP040I %1$s dump written to dataset(s) using name template %2$s The dump is written using the specified data set name template. Locate the dump data set, or data sets, and take appropriate action. JVMDUMP041I Incorrect use of -Xdump msg_filter The suboption msg_filter is applicable only to events throw, systhrow, catch, and uncaught. The dump agent is not loaded. Modify the dump option to apply the msg_filter suboption to applicable events. JVMDUMP036I Invalid or missing -Xdump filter A valid -Xdump filter must be supplied. The dump agent is not loaded. 6 IBM SDK, Java Technology Edition: IBM JVM messages

15 JVMDUMP042W JVMEXEL063E JVMDUMP042W Abort signal received while running on Java stack. The JVM dump agents could not be run. The JVM abort signal handler was called on a thread that is running on a Java stack. The JVM dump agents are not run to avoid further problems. The abort signal is passed on to the operating system. No specific action is required. Look for other messages that are produced to assist you with problem determination. Refer to operating system documentation for information about obtaining dumps on abort signals. EXEL messages EXE library messages. This section details messages that are generated by the IBM JVM: v JVMEXEL058E v JVMEXEL059E v JVMEXEL060E v JVMEXEL061E v JVMEXEL062E v JVMEXEL063E v JVMEXEL064E on page 8 v JVMEXEL065E on page 8 v JVMEXEL066E on page 8 v JVMEXEL067E on page 8 v JVMEXEL068E on page 8 v JVMEXEL074E on page 8 v JVMEXEL083E on page 8 v JVMEXEL084W on page 8 v JVMEXEL085W on page 8 JVMEXEL058E Internal VM error: Out of memory There is not enough virtual memory to satisfy a memory allocation request. Contact your IBM Service JVMEXEL059E Internal VM error: Failed to find class java/lang/string The java/lang/string class is not found in the class path. Contact your IBM Service JVMEXEL060E Internal VM error: Failed to create byte array for class name %s Byte array creation failed. Contact your IBM Service JVMEXEL061E Internal VM error: Failed to create java/lang/string for class name %s Creation of java/lang/string failed. Contact your IBM Service JVMEXEL062E Internal VM error: Out of memory converting string to UTF characters for class name %s The amount of available memory is too low to perform the conversion. Contact your IBM Service JVMEXEL063E Class %s does not implement main() IBM JVM messages 7

16 JVMEXEL064E JVMEXEL085W The main() method is not found. Ensure that the target class implements the main() method. JVMEXEL064E The method main must be declared public, static and void. The main() method should always be public, static, and void. Ensure that the main() method is declared correctly. JVMEXEL065E Internal VM error: Failed to create argument array An internal JVM error occurred. Contact your IBM Service JVMEXEL066E Internal VM error: Failed to create byte array for argument %s An internal JVM error occurred. Contact your IBM Service JVMEXEL067E Internal VM error: Failed to create java/lang/string for argument %s An internal JVM error occurred. Contact your IBM Service JVMEXEL068E Internal VM error: Failed to set array element for %s An internal JVM error occurred. Contact your IBM Service JVMEXEL074E Unable to redirect console to: %1$s:%2$d Failed to establish a socket connection to the target remote console. The JVM console output is not redirected to the target console. accessible. Ensure that the remote console is JVMEXEL083E Could not open file: %s The target file cannot be accessed. The JVM console output is not redirected to the target file. Ensure that the target file is accessible. JVMEXEL084W Unable to make a backup copy of file: %s the file. The JVM failed to back up the file. The JVM continues without backing up Ensure that the target file has the correct access permission. JVMEXEL085W WARNING: The command line argument "%s" has been deprecated. WARNING: Use "-jxe <path>" instead. The specified command-line argument is no longer valid. The JVM ignores the command-line argument and continues to run. Replace the command-line argument as suggested in the message text. EXEX messages JVM EXE messages This section details messages that are generated by the IBM JVM: v JVMEXEX010E on page 9 v JVMEXEX012E on page 9 v JVMEXEX013E on page 9 v JVMEXEX014I on page 9 v JVMEXEX015E on page 9 8 IBM SDK, Java Technology Edition: IBM JVM messages

17 JVMEXEX010E JVMEXEX024E v JVMEXEX016E v JVMEXEX017E v JVMEXEX023E v JVMEXEX024E JVMEXEX010E %s requires a parameter The specified command-line option requires a parameter. Add the required parameter to the JVM command-line option. JVMEXEX012E -jar option is not available for this class library This JVM does not support the -jar command-line option. Remove the -jar command-line option or use a different JVM. JVMEXEX013E Internal VM error: Failed to create Java VM created. error details. The Java virtual machine could not be Inspect previous JVM messages for the JVMEXEX014I Run %s -help for usage option. You used an invalid command-line Run the JVM with the -help command-line option. JVMEXEX015E VM startup error: Out of memory The JVM ran out of memory during the startup sequence. JVMEXEX016E Invalid jxespace parameters. The parameters supplied to the -jxespace option were not valid. Use different parameters for the -jxespace option. JVMEXEX017E Error mapping jxe in flash The JVM failed to map the memory space specified by the -jxespace option. Use different parameters for the -jxespace option. JVMEXEX023E Could not initialize JXE utilities. The JVM failed to initialize the JXE utilities library. Some of the JVM files might be corrupt. Reinstall the JVM from a package that you know to be valid. JVMEXEX024E JXE %s did not contain a startup class. startup class. The specified JXE file did not contain a Recompile the JXE with a startup class. J9CL messages IBM JVM Class library messages. This section details messages that are generated by IBM JVM class libraries: v JVMJ9CL000E on page 10 v JVMJ9CL001I on page 10 v JVMJ9CL002I on page 10 v JVMJ9CL003E on page 10 v JVMJ9CL004E on page 10 IBM JVM messages 9

18 JVMJ9CL000E JVMJ9CL033W v JVMJ9CL005E v JVMJ9CL031W v JVMJ9CL033W JVMJ9CL000E Incompatible class library The class library.jar file is not compatible with the class library native code. The JVM fails to start. Ensure that the vm.jar file has the same version as the JVM. JVMJ9CL001I Try running with -jcl:%s The class library.jar file is not compatible with the class library native code or the JVM. The JVM fails to start. Ensure that the class library native code and the JVM are compatible with the specified class library.jar file. JVMJ9CL004E Incompatible class library version: expected JCL v%1$i, found v%2$i The class library is not from the same release as the JVM. The JVM fails to start. Ensure that the JVM and the class libraries are from the same release. JVMJ9CL005E Incompatible class library version: requires VM v%1$i, found v%2$i The class library is not from the same release as the JVM. The JVM fails to start. Ensure that the JVM and the class libraries are from the same release. JVMJ9CL002I Classes are from a non-j9 library, or an incorrectly reduced JXE The class library.jar file is not compatible with this virtual machine. The JVM fails to start. Ensure that the class library is compatible with the JVM. JVMJ9CL031W Could not register dbgwrapper.dll as bootstrap library. Error code = %zu loaded. The file dbgwrapper.dll could not be The JVM attempts to start. Contact your IBM Service JVMJ9CL003E Incompatible class library version: JCL %1$x, VM %2$x The class library is not from the same release as the JVM. The JVM fails to start. Ensure that the JVM and the class libraries are from the same release. JVMJ9CL033W Could not register %s as bootstrap library. Error code = %zu The file indicated by the message could not be loaded. The JVM attempts to start. Contact your IBM Service J9GC messages Garbage collector messages. This section details messages that are generated by garbage collection: v JVMJ9GC017E on page 11 v JVMJ9GC018E on page 11 v JVMJ9GC019E on page 11 v JVMJ9GC020E on page 12 v JVMJ9GC021E on page 12 v JVMJ9GC022E on page 12 v JVMJ9GC023E on page 12 v JVMJ9GC024E on page IBM SDK, Java Technology Edition: IBM JVM messages

19 JVMJ9GC017E JVMJ9GC019E v JVMJ9GC027E on page 12 v JVMJ9GC028E on page 12 v JVMJ9GC029E on page 12 v JVMJ9GC030E on page 12 v JVMJ9GC031E on page 12 v JVMJ9GC032E on page 12 v JVMJ9GC033E on page 12 v JVMJ9GC034E on page 12 v JVMJ9GC035E on page 13 v JVMJ9GC036E on page 13 v JVMJ9GC038E on page 13 v JVMJ9GC039E on page 13 v JVMJ9GC040E on page 13 v JVMJ9GC041E on page 13 v JVMJ9GC042E on page 13 v JVMJ9GC054E on page 13 v JVMJ9GC057E on page 13 v JVMJ9GC059E on page 13 v JVMJ9GC062E on page 13 v JVMJ9GC063E on page 13 v JVMJ9GC069E on page 13 v JVMJ9GC070E on page 14 v JVMJ9GC071E on page 14 v JVMJ9GC072I on page 14 v JVMJ9GC073I on page 14 v JVMJ9GC074I on page 14 v JVMJ9GC075E on page 14 v JVMJ9GC076E on page 14 v JVMJ9GC077E on page 14 v JVMJ9GC078E on page 14 v JVMJ9GC079E on page 14 v JVMJ9GC080E on page 14 v JVMJ9GC081I on page 15 v JVMJ9GC082I on page 15 v JVMJ9GC084I on page 15 v JVMJ9GC088I on page 15 JVMJ9GC017E %1$s too small, must be at least %2$zu %3$sbytes The value for the specified option is smaller than the minimum permitted value. option. Use a larger value for the specified JVMJ9GC018E %1$s too small for %2$s The value for the specified option is smaller than the minimum permitted value. Adjust your garbage collector options. JVMJ9GC019E %1$s too large for %2$s The value for the specified option is larger than the maximum permitted value. IBM JVM messages 11

20 JVMJ9GC020E JVMJ9GC034E Adjust your garbage collector options. JVMJ9GC020E %s too large for heap The value for the specified option is larger than the maximum permitted value. Adjust the garbage collector options. JVMJ9GC021E %1$s must equal %2$s If both of these options are specified together, the values must be the same. Update the garbage collector options. JVMJ9GC022E Sum of %1$s and %2$s too large for %3$s The sum of the values specified for these options is larger than the maximum permitted value. Adjust the garbage collector options. JVMJ9GC029E Option error: '%s' This option is not valid. Check the garbage collector options and correct any errors before trying again. JVMJ9GC030E %1$s value of %2$.2f must be at least %3$s less than %4$s value of %5$.2f too close. The values specified for these options are Adjust the garbage collector options. JVMJ9GC031E %1$s and %2$s cannot both be specified together. again. You cannot specify both of these options Remove one of the options and try JVMJ9GC023E Sum of %1$s and %2$s must equal %3$s The sum of the values specified for these options is not equal to the third option. Adjust the garbage collector options. JVMJ9GC024E Sum of %1$s and %2$s too large for heap The sum of the values specified for these options is larger than the maximum permitted value. Adjust the garbage collector options. JVMJ9GC027E Malformed option: '%s' The option could not be parsed. Check the garbage collector options and correct any errors before trying again. JVMJ9GC028E Option too large: '%s' The value specified for this option is larger than the maximum permitted value. Adjust the garbage collector options. JVMJ9GC032E System configuration does not support option '%s' The specified option is not supported by the current hardware or operating system configuration. Remove the option or adjust your hardware or operating system configuration. JVMJ9GC033E %1$s value must be between %2$.2f and %3$.2f (inclusive) The value specified for this option is not within the permitted range. Adjust the garbage collector options. JVMJ9GC034E %1$s value must be between %2$zu and %3$zu (inclusive) The value specified for this option is not within the permitted range. Adjust the garbage collector options. 12 IBM SDK, Java Technology Edition: IBM JVM messages

21 JVMJ9GC035E JVMJ9GC069E JVMJ9GC035E %s must be followed by a number The option specified must be directly followed by a numeric value. Adjust the garbage collector options. For example, instead of "-Xmx 100m", use "-Xmx100m". JVMJ9GC036E %1$s value must be above %2$zu small. The value specified for the option is too Use a larger value for the garbage collector option and try again. JVMJ9GC038E %s value specified is too large large. The value specified for the option is too Use a smaller value for this garbage collector option and try again. JVMJ9GC039E %1$s is deprecated; use %2$s instead supported. again. The option is deprecated and no longer Replace the deprecated option and try JVMJ9GC040E Unknown option: %s The option is not recognized. Check the garbage collector options and correct any errors before trying again. JVMJ9GC041E Unknown fvtest type: %s The option is not recognized. Check the garbage collector options and correct any errors before trying again. JVMJ9GC042E Sum of %1$s and %2$s too small for %3$s The sum of the values specified for the options is smaller than the minimum permitted value. Adjust the garbage collector options. JVMJ9GC054E Large page size %1$zu%2$s is not a supported page size; using %3$zu%4$s instead The large page size specified is not supported by the operating system. A further message is issued detailing the supported page sizes. The JVM uses the default large page size instead of the size you specified. If the default large page size is not appropriate, update the garbage collector options with a supported page size. JVMJ9GC057E %1$s must be no greater than %2$s The first option cannot be used because the value specified must not be greater than the value of the second option. Adjust the garbage collector options. JVMJ9GC059E -Xgcpolicy:metronome is not allowed without -Xrealtime The metronome garbage collection policy requires the -Xrealtime option, but this option was not specified. Adjust the garbage collector options. JVMJ9GC062E %s value must be a power of two The value of the specified option must be a power of 2, for example: 2, 4, 8, 16, and so on. Adjust the garbage collector options. JVMJ9GC063E Unable to open file '%s' for writing for writing. The specified file could not be opened A log file is not produced. Check the permissions on the file system or specify a location and file name that you have write access to. JVMJ9GC069E Failed to initialize Finalize thread The finalize thread could not be created. Check that the system has enough native memory to run the JVM. IBM JVM messages 13

22 JVMJ9GC070E JVMJ9GC080E JVMJ9GC070E Failed to startup the Garbage Collector The Garbage Collector failed to start. Check that the system has enough native memory to run the JVM. JVMJ9GC075E An error occurred in parsing '-Xlp' option option. An error occurred when parsing the -Xlp Correct the -Xlp option and try again. JVMJ9GC071E Value for '%s' is not correct The value that is specified for the option is not correct. Correct the option and try again. JVMJ9GC072I Large page size %1$zu%2$s is not a supported page size; using %3$zu%4$s %5$s instead The specified page size is not supported by the operating system. A suitable page size is used instead. page size. The JVM is started with a different Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJ9GC073I Large page size %1$zu%2$s %3$s is not a supported page size; using %4$zu%5$s instead The specified large page size is not supported by the operating system. A suitable page size is used instead. size. The JVM starts using a different page Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJ9GC074I Large page size %1$zu%2$s %3$s is not a supported page size; using %4$zu%5$s %6$s instead The specified large page size is not supported by the operating system. A suitable page size is used instead. size. The JVM starts using a different page Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJ9GC076E System configuration does not support requested %1$zu%2$s large page size The large page size that is specified is not supported by the operating system. Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJ9GC077E System configuration does not support requested %1$zu%2$s %3$s large page size The large page size that is specified is not supported by the operating system. Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJ9GC078E '%1$s' is not specified as the first parameter in '%2$s' option A parameter is missing, or the parameters are not in the correct order. again. Correct the -Xlp parameters and try JVMJ9GC079E '%1$s' option is not complete, must specify '%2$s' parameter. parameters. The option is missing one or more Specify all the required parameter for the -Xlp option and try again. JVMJ9GC080E System configuration does not support parameter '%.*s' in option '-Xlp' The parameter that is used with the -Xlp option is not recognized. try again. Remove or correct the parameter and 14 IBM SDK, Java Technology Edition: IBM JVM messages

23 JVMJ9GC081I JVMJ9RI000E JVMJ9GC081I Extra comma characters are discovered in '-Xlp' option - ignored The -Xlp option contains comma characters that are not needed. -Xlp option. The JVM ignores the extra characters. Remove the extra commas from the JVMJ9GC082I Requested for %1$s page size %2$zu%3$s%4$s is not a supported page size; using %5$zu%6$s%7$s instead The specified page size is not supported by the operating system. A suitable page size is used instead. size. The JVM starts using a different page Adjust the -Xlp or -Xgc options to specify page size that is supported by the operating system. JVMJ9GC084I OS clock resolution claims to not support the requested target pause time. Overriding due to command line option -Xgc:overrideHiresTimerCheck The operating system returned a clock resolution that is larger than requested. However, the JVM continues to start because the option -Xgc:overrideHiresTimerCheck is requested. The JVM starts, but garbage collection pause time management remains subject to operating system performance, which might not provide adequate timer resolution. Use this option with caution, and only when you are unable to use a supported operating system. JVMJ9GC088I Requested objectheap page size %1$zu%2$s could not be satisfied; using %3$zu%4$s instead The requested object heap page size is supported by the operating system, but is not currently available. The JVM starts with a different object heap page size, instead of the specified size. No action is required. J9RI messages JVMRI interface messages. This section details messages that are generated by the IBM JVMRI interface: v JVMJ9RI000E v JVMJ9RI002E on page 16 v JVMJ9RI003E on page 16 v JVMJ9RI005E on page 16 v JVMJ9RI006E on page 16 v JVMJ9RI007E on page 16 v JVMJ9RI010E on page 16 v JVMJ9RI011E on page 16 v JVMJ9RI012E on page 16 v JVMJ9RI013E on page 16 v JVMJ9RI016E on page 16 v JVMJ9RI017E on page 17 v JVMJ9RI018I on page 17 v JVMJ9RI020E on page 17 v JVMJ9RI021E on page 17 v JVMJ9RI022E on page 17 v JVMJ9RI023E on page 17 JVMJ9RI000E jvmri->createthread cannot allocate thread arguments memory The JVM could not allocate the memory required to process a JVMRI CreateThread call. IBM JVM messages 15

24 JVMJ9RI002E JVMJ9RI016E The thread is not created. Error code JNI_ERR is returned. try again. Investigate process memory usage and JVMJ9RI002E jvmri->dumpregister called with NULL callback, function not registered. The JVM could not process a JVMRI DumpRegister call because the supplied callback function parameter was null. A callback function is not registered. Error code JNI_EINVAL is returned. Correct the JVMRI DumpRegister call by providing a callback function parameter. JVMJ9RI003E Can't allocate dump agent in jvmri->dumpregister, function not registered. The JVM could not allocate the memory required to process a JVMRI DumpRegister call. A callback function is not registered. Error code JNI_ERR is returned. try again. Investigate process memory usage and JVMJ9RI005E jvmri->getcomponentdataarea component %s does not have dataarea under this vm. The JVMRI GetComponentDataArea call is not supported by this JVM. Error code JNI_ERR is returned. Remove the JVMRI GetComponentDataArea call from the JVMRI agent code. JVMJ9RI006E jvmri->getrasinfo called with NULL RasInfo structure. The JVM could not process a JVMRI GetRasInfo call because the supplied info_ptr parameter was null. Error code JNI_EINVAL is returned. Correct the JVMRI GetRasInfo call by providing a valid pointer as the info_ptr parameter. JVMJ9RI007E jvmri->getrasinfo unable to allocate memory. The JVM could not allocate the memory required to process a JVMRI GetRasInfo call. Error code JNI_ENOMEM is returned. try again. Investigate process memory usage and JVMJ9RI010E jvmri->getrasinfo unable to allocate memory. The JVM could not allocate the memory required to process a JVMRI GetRasInfo call. returned. try again. None. Error code JNI_ENOMEM is Investigate process memory usage and JVMJ9RI011E RasInfo structure has unsupported type field. The RasInfo structure that was supplied as a parameter to a JVMRI GetRasInfo call had a request type that is not valid. returned. None. Error code JNI_EINVAL is Correct the request type in the supplied RasInfo structure and try again. JVMJ9RI012E jvmri->releaserasinfo called with NULL RasInfo structure. The JVM could not process a JVMRI ReleaseRasInfo call because the supplied info_ptr parameter was null. returned. None. Error code JNI_EINVAL is Correct the JVMRI ReleaseRasInfo call by providing a valid pointer as the info_ptr parameter. JVMJ9RI013E jvmri->releaserasinfo: structure has unsupported type field. The RasInfo structure that was supplied as a parameter to a JVMRI ReleaseRasInfo call had a request type that is not valid. returned. None. Error code JNI_EINVAL is Correct the request type in the supplied RasInfo structure and try again. JVMJ9RI016E jvmri->setoutofmemoryhook called with NULL callback, function not registered. The JVM could not process a JVMRI SetOutOfMemoryHook call because the supplied callback function parameter was null. A callback function is not registered. Error code JNI_EINVAL is returned. 16 IBM SDK, Java Technology Edition: IBM JVM messages

25 JVMJ9RI017E JVMJ9RI023E Correct the JVMRI SetOutOfMemoryHook call by providing a callback function parameter. JVMJ9RI017E Can't allocate dump agent in jvmri->setoutofmemoryhook, function not registered. The JVM could not allocate the memory required to process a JVMRI SetOutOfMemoryHook call. A callback function is not registered. Error code JNI_ERR is returned. try again. Investigate process memory usage and JVMJ9RI023E jvmri->traceregister, jvmri->tracederegister and TraceListener no longer supported, use new versions in JVMRAS_VERSION_1_5 The JVMRI TraceRegister and TraceDeregister calls are not supported by this JVM. The trace listener is not registered or unregistered. Error code JNI_ERR is returned. Change the JVMRI agent code to use the JVMRI TraceRegister50 and TraceDeregister50 calls instead. JVMJ9RI018I jvmri->notifysignal raising signal %d. The JVM is about to raise a signal as requested by a JVMRI NotifySignal call. The JVM raises the requested signal. This message is an information message. No action is required. JVMJ9RI020E jvmri->createthread unable to allocate private monitor A call to the JVMRI CreateThread function failed because the JVM was unable to allocate a monitor. The thread is not created. Error code JNI_ERR is returned. try again. Investigate process memory usage and JVMJ9RI021E jvmri->rundumproutine not supported. The JVMRI RunDumpRoutine call is not supported by this JVM. None. Error code JNI_ERR is returned. Remove the JVMRI RunDumpRoutine call from the JVMRI agent code. JVMJ9RI022E initialise JVMRI unable to allocate jvmri dump monitor The JVM failed to initialize the JVMRI interface because the JVM was unable to allocate a monitor. try again. Investigate process memory usage and IBM JVM messages 17

26 JVMJ9TI000E JVMJ9TI003E J9TI messages JVMTI interface messages. This section details messages that are generated by the IBM extensions to the JVMTI interface: v JVMJ9TI000E v JVMJ9TI001E v JVMJ9TI002E v JVMJ9TI003E v JVMJ9TI004I on page 19 v JVMJ9TI005I on page 19 v JVMJ9TI006I on page 19 v JVMJ9TI007I on page 19 v JVMJ9TI011I on page 19 v JVMJ9TI012I on page 19 v JVMJ9TI014I on page 19 v JVMJ9TI015I on page 19 v JVMJ9TI016I on page 19 v JVMJ9TI017I on page 19 v JVMJ9TI018I on page 19 v JVMJ9TI019I on page 19 v JVMJ9TI020I on page 20 v JVMJ9TI021I on page 20 v JVMJ9TI022I on page 20 v JVMJ9TI025I on page 20 v JVMJ9TI026I on page 20 v JVMJ9TI030I on page 20 v JVMJ9TI031I on page 20 v JVMJ9TI070E on page 20 v JVMJ9TI071E on page 20 JVMJ9TI000E Out of memory attempting to load agent library %s then ends. memory. The system ran out of native memory. The JVM fails to load the agent library, Increase the amount of available native JVMJ9TI001E Agent library %1$s could not be opened (%2$s) The agent shared library could not be found or opened. then ends. The JVM fails to load the agent library, Verify the existence of the agent shared library, and check that the file read permissions allow access. JVMJ9TI002E Agent_OnLoad not found in library %s The specified agent does not follow the JVMTI specification. then ends. agent library. The JVM fails to load the agent library, Add an Agent_OnLoad function to the JVMJ9TI003E Agent_OnLoad failed for library %s The initialization of the agent failed in the Agent_OnLoad function. 18 IBM SDK, Java Technology Edition: IBM JVM messages

27 JVMJ9TI004I JVMJ9TI019I The JVM fails to load the agent library, then ends. Correct the Agent_OnLoad failure. JVMJ9TI004I Returns via the capabilities_ptr the extended capabilities available at this time. An internationalized description of a JVMTI extension. None. None. JVMJ9TI005I Add the new extended capabilities from capabilities_ptr. An internationalized description of a JVMTI extension. None. None. JVMJ9TI006I Relinquish the extended capabilities from capabilities_ptr. An internationalized description of a JVMTI extension. None. None. JVMJ9TI007I Get the current set of extended capabilities via capabilities_ptr. An internationalized description of a JVMTI extension. None. None. JVMJ9TI011I Add a dynamic -Xtrace option An internationalized description of a JVMTI extension. None. None. JVMJ9TI012I Add a dynamic -Xdump option An internationalized description of a JVMTI extension. None. None. JVMJ9TI014I Controls Java Lock Monitor (JLM) (COM_IBM_JLM_START, COM_IBM_JLM_START_TIME_STAMP, COM_IBM_JLM_STOP, COM_IBM_JLM_STOP_TIME_STAMP). An internationalized description of a JVMTI extension. None. None. JVMJ9TI015I Request a Java Lock Monitor (JLM) dump. An internationalized description of a JVMTI extension. None. None. JVMJ9TI016I Allow inlining in the presence of method enter and exit events (resulting in possibly inaccurate reporting of enter and exit) An internationalized description of a JVMTI extension. None. None. JVMJ9TI017I Controls various VM and compiling options. An internationalized description of a JVMTI extension. None. None. JVMJ9TI018I Sets a method for selective entry and exit notification. An internationalized description of a JVMTI extension. None. None. JVMJ9TI019I Sets notification mode for extended events, allowing thread-level selectivity An internationalized description of a JVMTI extension. None. None. IBM JVM messages 19

28 JVMJ9TI020I JVMJ9TI071E JVMJ9TI020I Gets the OS thread ID from a jthread None. An internationalized description of a JVMTI extension. None. None. JVMJ9TI021I Get extended frame information An internationalized description of a JVMTI extension. None. None. JVMJ9TI022I Get extended frame information for all stack traces. An internationalized description of a JVMTI extension. None. None. JVMJ9TI025I Allow direct JNI in the presence of method enter and exit events (resulting in possibly inaccurate reporting of enter and exit) An internationalized description of a JVMTI extension. None. None. JVMJ9TI026I Trigger a dump using the given RAS configuration. An internationalized description of a JVMTI extension. None. JVMJ9TI030I Signal the async event on a single thread or all threads An internationalized description of a JVMTI extension. None. None. JVMJ9TI031I Cancel the async event on a single thread or all threads An internationalized description of a JVMTI extension. None. None. JVMJ9TI070E Agent initialization function %s failed for library %s, return code %d Agent_OnLoad or Agent_OnAttach failed to initialize the agent. and ends. The JVM fails to load the agent library The agent library must be updated to correct the agent initialization failure. JVMJ9TI071E Agent initialization function %s not found in library %s The specified agent library does not correctly follow the JVMTI specification. and ends. The JVM fails to load the agent library The agent library must be updated to add the missing initialization function. J9VM messages General JVM messages. This section details messages that are generated by the IBM JVM: v JVMJ9VM000E on page 22 v JVMJ9VM002E on page 22 v JVMJ9VM003W on page 22 v JVMJ9VM004E on page 22 v JVMJ9VM005E on page 22 v JVMJ9VM006E on page 22 v JVMJ9VM007E on page 22 v JVMJ9VM008E on page IBM SDK, Java Technology Edition: IBM JVM messages

29 v JVMJ9VM009E on page 23 v JVMJ9VM010W on page 23 v JVMJ9VM011W on page 23 v JVMJ9VM012W on page 23 v JVMJ9VM013W on page 23 v JVMJ9VM014W on page 23 v JVMJ9VM015W on page 23 v JVMJ9VM016W on page 23 v JVMJ9VM017E on page 23 v JVMJ9VM018E on page 24 v JVMJ9VM019E on page 24 v JVMJ9VM020I on page 24 v JVMJ9VM022E on page 24 v JVMJ9VM023I on page 24 v JVMJ9VM031E on page 24 v JVMJ9VM034E on page 24 v JVMJ9VM035E on page 24 v JVMJ9VM038E on page 24 v JVMJ9VM039I on page 24 v JVMJ9VM050E on page 25 v JVMJ9VM053E on page 25 v JVMJ9VM058I on page 25 v JVMJ9VM059I on page 25 v JVMJ9VM061W on page 25 v JVMJ9VM062W on page 25 v JVMJ9VM063W on page 25 v JVMJ9VM064W on page 25 v JVMJ9VM067W on page 25 v JVMJ9VM068W on page 25 v JVMJ9VM078E on page 25 v JVMJ9VM079W on page 26 v JVMJ9VM080W on page 26 v JVMJ9VM081W on page 26 v JVMJ9VM082E on page 26 v JVMJ9VM083W on page 26 v JVMJ9VM084W on page 26 v JVMJ9VM085W on page 26 v JVMJ9VM086W on page 26 v JVMJ9VM087W on page 26 v JVMJ9VM090I on page 27 v JVMJ9VM091I on page 27 v JVMJ9VM092I on page 27 v JVMJ9VM093E on page 27 v JVMJ9VM094I on page 27 v JVMJ9VM096I on page 27 IBM JVM messages 21

30 JVMJ9VM000E JVMJ9VM007E v JVMJ9VM109E on page 27 v JVMJ9VM110E on page 27 v JVMJ9VM111E on page 27 v JVMJ9VM117I on page 27 v JVMJ9VM120I on page 27 v JVMJ9VM121I on page 28 v JVMJ9VM122E on page 28 v JVMJ9VM123E on page 28 v JVMJ9VM129E on page 28 v JVMJ9VM130E on page 28 v JVMJ9VM131E on page 28 v JVMJ9VM133W on page 28 v JVMJ9VM134W on page 28 v JVMJ9VM135W on page 28 v JVMJ9VM136W on page 29 v JVMJ9VM138W on page 29 v JVMJ9VM142E on page 29 v JVMJ9VM143E on page 29 v JVMJ9VM145E on page 29 JVMJ9VM000E Malformed value for IBM_JAVA_OPTIONS The JVM has found an error when parsing the environment variable IBM_JAVA_OPTIONS. This problem can be caused by syntax errors such as unmatched quotes. Check the syntax of the environment variable IBM_JAVA_OPTIONS JVMJ9VM002E Options file not found The file specified using the option -Xoptionsfile cannot be found. Correct the command line option for -Xoptionsfile and try again. JVMJ9VM003W JIT compiler "%s" not found. Will use interpreter. The value specified for the -Djava.compiler option is not valid. The JVM continues without a compiler. The performance might be slower. and try again. Correct the value for -Djava.compiler JVM initialization uses system services to load numerous libraries, including libraries that are specified by the user. Libraries can have dependencies on other libraries. This message is produced when a library cannot be loaded. The JVM ends Check your system to ensure that the libraries indicated are available and accessible. If this problem occurs with an application that has run successfully before, check for any recent changes to your environment. representative if the problem continues. JVMJ9VM005E Invalid value for environment variable: %s The value entered for the environment variable is not valid. Correct the value for the environment variable and try again. JVMJ9VM006E Invalid command-line option: %s The command-line option is not valid. Correct or remove the command-line option and try again. JVMJ9VM004E Cannot load library required by: %s JVMJ9VM007E Command-line option unrecognised: %s 22 IBM SDK, Java Technology Edition: IBM JVM messages

31 JVMJ9VM008E JVMJ9VM017E The command-line option is not recognized. Correct or remove the command-line option and try again. JVMJ9VM008E J9VMDllMain not found J9VMDllMain is the main module entry point for system libraries. If J9VMDllMain is not found the module cannot be used. JVMJ9VM009E J9VMDllMain failed J9VMDllMain is the main module entry point for system libraries. There has been a failure using J9VMDllMain. JVMJ9VM010W Failed to initialize %s The identified library cannot be initialized. This message is typically associated with JVMPI function. The JVM continues but the function might be affected. JVMJ9VM011W Unable to load %1$s: %2$s The JVM failed to load the library named in the first parameter. The second parameter gives further information about the failure. The JVM continues but might end later if the library contained core JVM function. Check the libraries are available and can be accessed. representative if the problem continues. JVMJ9VM012W Unable to unload %1$s: %2$s The JVM failed to unload the library named in the first parameter. The second parameter gives further information about the failure. representative if the problem continues. JVMJ9VM013W Initialization error in function %1$s(%2$d): %3$s the JVM. This is typically an internal error within The JVM continues but might end later if the error occurred in a critical area. representative if the problem continues. JVMJ9VM014W Shutdown error in function %1$s(%2$d): %3$s An internal error occurred during shutdown Further information about the error is provided. representative if the problem continues. JVMJ9VM015W Initialization error for library %1$s(%2$d): %3$s A problem occurred when the JVM tried to initialize the library. This can happen when the JVM is started with incorrect options, giving rise to additional messages. Check preceding messages for an indication of the problem. Correct the problem and try again. JVMJ9VM016W Shutdown error for library %1$s(%2$d): %3$s An internal error occurred during shutdown Further information about the error is provided. Contact your IBMM service representative if the problem continues. JVMJ9VM017E Could not allocate memory for command line option array During JVM initialization the command line options are stored in memory. There was not enough memory available for the JVM to complete the process. This is unlikely to be a problem caused by starting the JVM. Check your system for hardware or software faults and correct them. Restart your system and try again. representative if the problem continues. IBM JVM messages 23

32 JVMJ9VM018E JVMJ9VM039I JVMJ9VM018E Could not allocate memory for shared library load table pool This error is issued when memory cannot be allocated to expand an internal table. This is unlikely to be a problem caused by the JVM. The JVM continues but is likely to fail. Check your system for hardware or software faults and correct them. Restart your system and try again. representative if the problem continues. JVMJ9VM019E Fatal error: Unable to find and initialize required class %.*s A required class could not be found or could not be initialized. JVMJ9VM020I Searched in %.*s This message lists a class path entry that was searched while trying to find a required class. JVMJ9VM022E Stack map failed, result = %p - aborting VM 601. An internal error occurred. The JVM ends with exit code 600 or Contact your IBM Service JVMJ9VM023I This may indicate that JAVA_HOME is incorrect, or that class libraries are not installed A required class could not be found or could not be initialized. The value set for JAVA_HOME might be incorrect, or the class library might not be installed correctly. Check that the JAVA_HOME environment variable is properly set. JVMJ9VM031E Required class %2$.*1$s must be in the boot classpath, but was found in the application class path in %4$.*3$s A required class was found on the application class path, not on the boot classpath. For security reasons this class must be found on the boot classpath. Check your command line options to ensure that you have not placed boot classes on the application classpath. JVMJ9VM034E JVMRI requires trace engine: run with -Xtrace flag Tracing must be enabled to use the JVMRI environment requested. The JVMRI environment is not returned with the GetEnv() JNI function. Add the appropriate -Xtrace option to the command line. JVMJ9VM035E Unable to allocate OutOfMemoryError The JVM tried to issue an OutOfMemoryError but failed. Exceeding the maximum value for the -Xmca and -Xmco options causes this error. Check your use of these options, the memory usage of your application and try again (possibly using the -Xmx option on startup). If the problem persists then contact your IBM service JVMJ9VM038E -Xthr: unrecognized option --> \'%s\' The value specified for the -Xthr option was not recognized. and try again. Correct or remove the -Xthr option JVMJ9VM039I -Xscmx is ignored if -Xshareclasses is not specified The -Xscmx option is not meaningful unless shared class support is active. Remove the -Xscmx option or activate shared classes by using the -Xshareclasses option. 24 IBM SDK, Java Technology Edition: IBM JVM messages

33 JVMJ9VM050E JVMJ9VM078E JVMJ9VM050E -Xjni: unrecognized option --> \'%s\' The option specified with the -Xjni command-line parameter is not recognized. -Xjni. Correct the option specified with JVMJ9VM053E Malformed option %s found in -Xoptionsfile The options file contains an option that is not correctly specified. Correct the option in the options file. JVMJ9VM058I -Xscminaot is ignored if -Xshareclasses is not specified The command-line option -Xscminaot is not meaningful unless -Xshareclasses is specified. The JVM ignores the -Xscminaot command-line option and continues. Determine if -Xscminaot should be removed, or if -Xshareclasses should be added. JVMJ9VM059I -Xscmaxaot is ignored if -Xshareclasses is not specified The command-line option -Xscmaxaot is not meaningful unless -Xshareclasses is specified. The JVM ignores the -Xscmaxaot command-line option and continues. Determine if -Xscmaxaot should be removed, or if -Xshareclasses should be added. JVMJ9VM061W insertdumpagent requires %s An internal VM function called via the JVMTI SetVmDump() API has failed because the required DLL has not been loaded. The dump options are not changed, JNI_ERR is returned. Check whether the JVM dump functions have been disabled via the -Xdump:none option. JVMJ9VM062W removedumpagent requires %s An internal VM function called via the JVMTI SetVmDump() API has failed because the required DLL has not been loaded. The dump options are not changed, JNI_ERR is returned. Check whether the JVM dump functions have been disabled via the -Xdump:none option. JVMJ9VM063W seekdumpagent requires %s An internal VM function called via the JVMTI SetVmDump() API has failed because the required DLL has not been loaded. The dump options are not changed, JNI_ERR is returned. Check whether the JVM dump functions have been disabled via the -Xdump:none option. JVMJ9VM064W setdumpoption requires %s An internal JVM function, called by the JVMTI SetVmDump() API, has failed because the required DLL is not loaded. The dump options are not changed. JNI_ERR is returned. Check whether the JVM dump functions have been turned off with the -Xdump:none option. JVMJ9VM067W -Xshareclasses not enabled, -Xzero:sharezip option ignored The -Xzero:sharezip option is ignored if shared classes are not enabled. option. The JVM ignores the -Xzero:sharezip This warning message can be ignored if you do not want to use the -Xzero:sharezip option. If you do want to use the -Xzero:sharezip option, enable shared classes. JVMJ9VM068W -Xshareclasses not enabled, -Xzero:sharestring option ignored The -Xzero:sharestring option is ignored if shared classes are not enabled. The JVM ignores the -Xzero:sharestring option. This warning message can be ignored if you do not want to use the -Xzero:sharestring option. If you do want to use the -Xzero:sharestring option, enable shared classes. JVMJ9VM078E Malformed value for JAVA_TOOL_OPTIONS An option found in the environment variable JAVA_TOOLS_OPTIONS is not specified correctly. IBM JVM messages 25

34 JVMJ9VM079W JVMJ9VM087W Correct the option in the environment variable JAVA_TOOLS_OPTIONS. JVMJ9VM079W triggeroneoffdump(%1$s) requires %2$s An internal JVM function, called by the JVMTI TriggerVmDump() API, failed because the required DLL is not loaded. The requested dump is not triggered. JNI_ERR is returned. Check whether the JVM dump functions have been turned off with the -Xdump:none option. JVMJ9VM080W queryvmdump requires %s An internal VM function, called by the JVMTI QueryVmDump() API, failed because the required DLL is not loaded. An empty list of dump option specifications is returned. Check whether the JVM dump functions have been turned off with the -Xdump:none option. JVMJ9VM081W Malformed option value, option "%1$s%3$.*2$s" contains trailing characters "%4$s" which have been ignored The command-line option contained extra characters that were ignored. These extra characters might have been intended to be other command-line options. try again. The JVM ignores the extra characters. Correct the command-line option and JVMJ9VM082E Unable to switch to IFA processor - issue "extattr +a libj9ifa%s.so" The JVM failed to switch to an IFA (Integrated Facility for Applications) processor because the JVM library file libj9ifa%s.so requires APF authorization. The JVM continues but prevents further attempts to switch between IFA and standard processors. Set extended attributes for the libj9ifa%s.so file using the command extattr +a. JVMJ9VM083W Error switching to IFA processor rc: %08x The JVM failed to switch to an IFA (Integrated Facility for Applications) processor. The return code indicates the error condition. The JVM continues but prevents further attempts to switch between IFA and standard processors. representative for further information. JVMJ9VM084W IFA Error: unexpected return code %08x from IFA switch service The JVM failed to switch to an IFA (Integrated Facility for Applications) processor. The return code indicates the error condition. The JVM continues but prevents further attempts to switch between IFA and standard processors. representative for further information. JVMJ9VM085W Malformed option: '%s' parsed. continues. The specified option cannot not be The JVM ignores the option and Correct the command-line option. JVMJ9VM086W Option too large: '%s' The specified option is larger than the maximum permitted value. continues. The JVM ignores the option and Adjust the command-line option. JVMJ9VM087W resetdumpoption requires %s An internal JVM function, called by the JVMTI ResetVmDump() API, failed because the required DLL is not loaded. is returned. Dump options are not reset. JNI_ERR Check whether the JVM dump functions have been turned off with the -Xdump:none option. 26 IBM SDK, Java Technology Edition: IBM JVM messages

35 JVMJ9VM090I JVMJ9VM120I JVMJ9VM090I Slow response to network query (%d secs), check your IP DNS configuration A network query used by the JVM to populate diagnostic data took longer than expected. The JVM continues but the diagnostic data is not available. Check your IP DNS configuration. For example, on AIX and UNIX systems, check the file /etc/resolv.conf. JVMJ9VM096I -Xscdmx is ignored if -Xshareclasses is not specified The option -Xscdmx specifies the size of the class debug area in a shared class cache. If -Xshareclasses is not specified, -Xscdmx is ignored. The option -Xscdmx is ignored. This warning message can be ignored if you do not want to use the -Xscdmx option. If you do want to use the -Xscdmx option, enable shared classes. JVMJ9VM091I Adaptive spinning supported This information message is shown when -Xthr:what is used on the command line. The JVM prints this information message when -Xthr:what is used on the command line and adaptive spinning is enabled. No action is required. JVMJ9VM092I Adaptive spinning not supported The JVM optimization, adaptive spinning, is not enabled. This information message is shown when the option -Xthr:what is specified on the command line. No action is required. JVMJ9VM093E This version of Java requires a CPU that supports SSE2 or later extensions. See the 'Supported Environments' information in the IBM Java User Guide for more details. The processor does not support the SSE2 instruction set. Run this version of Java on a system that supports SSE2 or later extensions. For more details, see the Supported Environments information in the IBM SDK for Java User Guide. JVMJ9VM094I Thread "%s" is still alive after running the shutdown hooks. The JVM cannot shut down because a thread is still alive. DestroyJavaVM() returns JNI_ERR. Add a shutdown hook to end the thread when the JVM shuts down. JVMJ9VM109E Unsupported operating system (%s): Windows XP or newer is required. The operating system is too old to run this version of the JVM. Run the JVM on a system with a supported operating system. For information about supported hardware and software, see the IBM SDK for Java User guides. JVMJ9VM110E Invalid lockword mode specified:%s The mode specified with the option -Xlockword:mode= is not valid. Use a supported value for the mode, and start the JVM again. JVMJ9VM111E Invalid lockword option specified:%s valid. This option used with -Xlockword: is not Use a supported -Xlockword option and start the JVM again. JVMJ9VM117I -Xitsn is ignored if -Xshareclasses is not specified are enabled. -Xitsn option. -Xitsn is valid only when shared classes The JVM continues and ignores the Enable shared classes with the -Xshareclasses option, or remove the -Xitsn option. JVMJ9VM120I -Xscminjitdata is ignored if -Xshareclasses is not specified classes. -Xscminjitdata is valid only for shared The JVM continues, but the -Xscminjitdata value is ignored. IBM JVM messages 27

36 JVMJ9VM121I JVMJ9VM135W If you want to specify a value for -Xscminjitdata, enable shared classes using the -Xshareclasses option. JVMJ9VM121I -Xscmaxjitdata is ignored if -Xshareclasses is not specified classes. -Xscmaxjitdata is valid only for shared The JVM ignores the -Xscmaxjitdata option and continues. If you want to specify a value for -Xscmaxjitdata, enable shared classes using the -Xshareclasses option. JVMJ9VM122E Failed to get user32.dll address range required for -Xprotectcontiguous. The JVM failed to find the address range of user32.dll. Run the JVM without the -Xprotectcontiguous option. JVMJ9VM123E Attempting to run on a non-supported processor, JVM will terminate. The processor is not supported. See the information about supported environments in the IBM SDK for Java User Guide to determine the minimum system requirements. JVMJ9VM129E Application resumed execution after handling a fatal condition and illegally returned to, or called back into, Java After handling an unrecoverable condition, the application continues, illegally returning to, or calling back into Java. The JVM prints the error message and ends the process using the z/os specific system call, CEE3AB2(). Change the user condition handler so that the application does not continue when there is an unrecoverable condition on a Java thread. JVMJ9VM130E Application resumed execution after handling a fatal condition and illegally returned to, or called back into, Java (JIT'ed code) After handling an unrecoverable condition, the application continues, illegally returning to, or calling back into Java. The JVM prints the error message and ends the process using the z/os specific system call, CEE3AB2(). Change the user condition handler so that the application does not continue when there is an unrecoverable condition on a Java thread. JVMJ9VM131E Terminating process using CEE3AB2() with abend %1$u, reason %2$u, cleanup %3$u. The JVM detects an unrecoverable condition and ends the process using the z/os specific system call, CEE3AB2, which causes an abend. The JVM prints the error message and ends the process. Check the console and operator console messages. If further assistance is required, contact your IBM Service JVMJ9VM133W The system core size hard ulimit is set to %d, system dumps may be truncated. The JVM started with the -Xcheck:dump option, and detected that the core dump file size is limited by the system hard ulimit. Refer to the IBM SDK documentation. JVMJ9VM134W The system fullcore option is set to FALSE, system dumps may be truncated. The JVM started with the -Xcheck:dump option, and detected that the system fullcore option is set to FALSE. Refer to the IBM SDK documentation. JVMJ9VM135W /proc/sys/kernel/core_pattern setting "%s" specifies that core dumps are to be piped to an external program. The JVM may be unable to locate core dumps and rename them. The JVM started on a system with /proc/sys/kernel/core_pattern set to pipe core dumps to the command specified after the character. The JVM might be unable to locate core dumps and rename them. Message JVMPORT030W is issued when a system dump is taken. Refer to the product documentation for the IBM SDK, Java Technology Edition. 28 IBM SDK, Java Technology Edition: IBM JVM messages

37 JVMJ9VM136W JVMJ9VM145E JVMJ9VM136W /proc/sys/kernel/core_pattern setting "%s" specifies a format string for renaming core dumps. The JVM may be unable to locate core dumps and rename them. The JVM started on a system with /proc/sys/kernel/core_pattern set to rename core dumps. The JVM might be unable to locate the core dump. Refer to the product documentation for the IBM SDK, Java Technology Edition. JVMJ9VM138W The -Xdiagnosticscollector option is not supported by this JVM. The JVM started with the -Xdiagnosticscollector option, which is no longer supported. Refer to the product documentation for the IBM SDK, Java Technology Edition. JVMJ9VM142E The command-line option -Xrealtime is not supported in this version of the IBM JDK The -Xrealtime option is no longer supported with this release of the IBM developer kit. The JVM does not start. Remove this option and try again. If you require -Xrealtime functionality, contact your IBM support JVMJ9VM143E The command-line option %s is not supported in this version of the IBM SDK The IBM SDK no longer supports the %s option. The JVM fails to start. Consult your IBM service representative if % functionality is required or remove the option. JVMJ9VM145E %s is unsupported on z/os. The specified command-line option is not supported. line. The JVM fails to start. Remove the option from the command JITM messages JIT compiler messages. This section details messages that are generated by the IBM JIT compiler: v JVMJITM000E on page 30 v JVMJITM001W on page 30 v JVMJITM002W on page 30 v JVMJITM003W on page 30 v JVMJITM004W on page 30 v JVMJITM005W on page 30 v JVMJITM006W on page 30 v JVMJITM007W on page 30 v JVMJITM009E on page 30 v JVMJITM010E on page 31 v JVMJITM011E on page 31 v JVMJITM012E on page 31 v JVMJITM013E on page 31 v JVMJITM014I on page 31 v JVMJITM015I on page 31 v JVMJITM016I on page 31 v JVMJITM017I on page 31 v JVMJITM018I on page 31 IBM JVM messages 29

38 JVMJITM000E JVMJITM009E JVMJITM000E Unsupported hardware [%d]. The current hardware is not supported by the compiler. The compiler does not generate code for this hardware. Check the IBM Java documentation for a list of supported hardware. JVMJITM001W No more space for AOT code in shared class cache. New AOT code will not be generated. cache is full. The AOT section of the shared class The compiler stops generating AOT code. The AOT code already stored in the shared class cache continues to be used. Increase the size of the AOT section of the shared class cache using the -Xscmaxaot option. JVMJITM002W Failure storing AOT code in shared class cache. Shared class cache might be corrupted. Ignoring AOT code in shared class cache. An error occurred storing AOT code in the shared class cache. The compiler stops generating AOT code. AOT code from the shared class cache is not used. Destroy and re-create the AOT code in the shared class cache using the -Xshareclasses:reset option. JVMJITM003W Failure during AOT runtime initialization. Ignoring AOT code in shared class cache. An error occurred initializing AOT. The compiler does not generate AOT code. AOT code from the shared class cache is not used. If the error occurs again, destroy and re-create the AOT code in the shared class cache using the -Xshareclasses:reset option. JVMJITM004W AOT code in shared class cache cannot execute on current processor. Ignoring AOT code in shared class cache. The AOT code in the shared class cache is not compiled for this platform. The compiler does not generate AOT code. AOT code from the shared class cache is not used. Destroy and re-create the AOT code in the shared class cache for the current platform using the -Xshareclasses:reset option. JVMJITM005W AOT code in the shared class cache cannot run on current JVM release. Ignoring AOT code in shared class cache. The AOT code in the shared class cache was created using a different JVM release. The compiler does not generate AOT code. AOT code from the shared class cache is not used. Destroy and re-create the AOT code in the shared class cache for the current JVM release using the -Xshareclasses:reset option. JVMJITM006W AOT code in shared class cache cannot run with current garbage collection policy. Ignoring AOT code in shared class cache. The AOT code in the shared class cache was created using a different garbage collection policy. The compiler does not generate AOT code. AOT code from the shared class cache is not used. Destroy and re-create the AOT code in the shared class cache for the current garbage collection policy using the -Xshareclasses:reset option. JVMJITM007W AOT code in shared class cache cannot run with current JVMPI or JVMTI settings. Ignoring AOT code in shared class cache. JVMTI. AOT code cannot be used with JVMPI or The compiler does not generate AOT code. AOT code from the shared class cache is not used. To use AOT code, disable JVMTI. JVMPI is replaced by JVMTI in Java 6. JVMJITM009E System configuration does not support parameter '%.*s' in option '-Xlp' The specified parameter is not recognized for the -Xlp option. Remove the unrecognized parameter from the -Xlp option and try again. 30 IBM SDK, Java Technology Edition: IBM JVM messages

39 JVMJITM010E JVMJITM018I JVMJITM010E %s must be followed by a number The specified option must be followed immediately by a number. Adjust the JIT option. For example, replace -Xlp:objectheap:pagesize <size> with -Xlp:objectheap:pagesize<size>. JVMJITM011E %s value specified is too large The specified option is too large. Adjust the JIT options and try again. JVMJITM012E Value for '%s' is not correct correct. The value specified for the option is not Correct the option and try again. JVMJITM013E '%1$s' option is not complete, must specify '%2$s' parameter. The option specified is not complete. More parameters are required. Specify all the required parameters for the -Xlp option. JVMJITM014I Extra comma characters are discovered in '-Xlp' option - ignored The -Xlp option specified contains extra comma characters. and continues. The JVM ignores the extra characters Remove the extra commas from the -Xlp option for any future invocation. JVMJITM016I Large page size %1$zu%2$s is not a supported page size; using %3$zu%4$s %5$s instead The specified page size is not supported by the operating system. A suitable page size is used instead. size. The JVM starts using a different page Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJITM017I Large page size %1$zu%2$s %3$s is not a supported page size; using %4$zu%5$s instead The specified large page size is not supported by the operating system. A suitable page size is used instead. size. The JVM starts using a different page Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJITM018I Large page size %1$zu%2$s %3$s is not a supported page size; using %4$zu%5$s %6$s instead The specified large page size is not supported by the operating system. A suitable page size is used instead. size. The JVM starts using a different page Adjust the -Xlp option to specify a page size that is supported by the operating system. JVMJITM015I Large page size %1$zu%2$s is not a supported page size; using %3$zu%4$s instead The specified large page size is not supported by the operating system. A default size is used instead. page size. The JVM starts using the default large Adjust the -Xlp option to a specify page size that is supported by the operating system. IBM JVM messages 31

40 JVMJNCK000E JVMJNCK025I JNCK messages JNI messages. This section details messages that are generated by the IBM JNI component: v JVMJNCK000E v JVMJNCK001I v JVMJNCK002E v JVMJNCK023E v JVMJNCK024E v JVMJNCK025I v JVMJNCK062W on page 33 v JVMJNCK077E on page 33 v JVMJNCK078W on page 33 v JVMJNCK079I on page 33 v JVMJNCK080E on page 33 v JVMJNCK081W on page 33 v JVMJNCK082I on page 33 v JVMJNCK083E on page 33 v JVMJNCK084W on page 33 v JVMJNCK085I on page 33 v JVMJNCK089E on page 33 v JVMJNCK090W on page 34 v JVMJNCK091I on page 34 JVMJNCK000E -Xcheck:jni: unrecognized option --> \'%s\' You specified an unrecognized -Xcheck:jni command-line option. The JVM prints usage information for the -Xcheck:jni option and ends. option. Correct the -Xcheck:jni command-line JVMJNCK001I JNI check utility installed. Use -Xcheck:jni:help for usage on JNI calls. The JNI check utility has been installed. The JVM performs additional checks This message is an information message. No action is required. JVMJNCK023E JNI error detected. Continuing... The JNI check utility has detected a recoverable JNI error. Investigate the JNI check error that was reported in the previous message. JVMJNCK024E JNI error detected. Aborting. The JNI check utility detected an unrecoverable JNI error. Investigate the JNI check error that was reported in the previous message. JVMJNCK002E JNI check utility: unable to hook event Initialization of the JNI check utility failed because it was unable to intercept native method calls. JVMJNCK025I Use -Xcheck:jni:nonfatal to continue running when errors are detected. The JVM detected a JNI error and ended. You can use the -Xcheck:jni:nonfatal parameter to change this behaviour. 32 IBM SDK, Java Technology Edition: IBM JVM messages

41 JVMJNCK062W JVMJNCK089E If required, rerun with the -Xcheck:jni:nonfatal parameter. JVMJNCK062W JNI warning in %s: This function should not be called inside of a critical section A JNI function was called within a JNI critical section. code. Check and correct the JNI application JVMJNCK077E Error detected in %2$.*1$s.%4$.*3$s%6$.*5$s This message provides additional information about the Java class and method that were used in the JNI function identified in a previous error message. Investigate the previous error message. JVMJNCK078W Warning detected in %2$.*1$s.%4$.*3$s%6$.*5$s This message provides additional information about the Java class and method that were used in the JNI function identified in a previous warning message. message. Investigate the previous warning JVMJNCK079I Advice detected in %2$.*1$s.%4$.*3$s%6$.*5$s This message provides additional information about the Java class and method that were used in the JNI function identified in a previous advice message. message. Investigate the previous advice JVMJNCK080E Error detected in the outermost frame of an attached thread This message provides additional information about the frame context of the JNI function that was identified in a previous error message. messages. Investigate the previous error JVMJNCK081W Warning detected in the outermost frame of an attached thread This message provides additional information about the frame context of the JNI function that was identified in a previous warning message. messages. Investigate the previous warning JVMJNCK082I Advice detected in the outermost frame of an attached thread This message provides additional information about the frame context of the JNI function that was identified in a previous advice message. messages. Investigate the previous advice JVMJNCK083E Error detected in JNI_OnLoad of library %.*s This message provides additional information about the JNI function that was identified in a previous error message. Investigate the previous error message. JVMJNCK084W Warning detected in JNI_OnLoad of library %.*s This message provides additional information about the JNI function that was identified in a previous warning message. message. Investigate the previous warning JVMJNCK085I Advice detected in JNI_OnLoad of library %.*s This message provides additional information about the JNI function that was identified in a previous advice message. message. Investigate the previous advice JVMJNCK089E Error detected in the handler frame of a JVMPI or JVMTI event This message provides additional information about the frame context of the JNI function that was identified in a previous error message. IBM JVM messages 33

42 JVMJNCK090W JVMMECK002E messages. Investigate the previous error JVMJNCK090W Warning detected in handler frame of a JVMPI or JVMTI event This message provides additional information about the frame context of the JNI function that was identified in a previous warning message. messages. Investigate the previous warning JVMJNCK091I Advice detected in handler frame of a JVMPI or JVMTI event This message provides additional information about the frame context of the JNI function that was identified in a previous advice message. messages. Investigate the previous advice MECK messages Memory checking messages. This section details messages that are generated by the memory checking component of the IBM JVM: v JVMMECK000E v JVMMECK001E v JVMMECK002E JVMMECK000E An error occurred initializing the -Xcheck:memory utility The memory check utility could not locate the required virtual machine resources. performed. The requested memory check is not Verify that your Java runtime environment is correctly installed. JVMMECK001E Unrecognized -Xcheck:memory option: %s The memory check that you requested is not a recognized type. The Java application runs but no memory checks are performed. 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 The memory check utility could not store information about the source code locations of memory requests. The JVM performs the memory checks without recording memory requestor information. Check that your system is configured with sufficient memory. OFFC messages JNI control messages. This section details messages that are generated by the IBM JVM: v JVMOFFC000E on page 35 v JVMOFFC001I on page 35 v JVMOFFC002E on page 35 v JVMOFFC003E on page 35 v JVMOFFC004E on page 35 v JVMOFFC005E on page 35 v JVMOFFC007E on page 35 v JVMOFFC008E on page IBM SDK, Java Technology Edition: IBM JVM messages

43 JVMOFFC000E JVMOFFC008E v JVMOFFC009E on page 36 v JVMOFFC010E on page 36 v JVMOFFC022I on page 36 v JVMOFFC023E on page 36 v JVMOFFC024I on page 36 v JVMOFFC025E on page 36 v JVMOFFC026E on page 36 v JVMOFFC027E on page 36 v JVMOFFC028E on page 36 v JVMOFFC029E on page 36 v JVMOFFC030E on page 37 v JVMOFFC031E on page 37 JVMOFFC000E -Xoffload:sim: unrecognized option --> \'%s\' You specified an invalid option for the -Xoffload:sim parameter. Use a valid option for the -Xoffload:sim parameter. JVMOFFC001I Offload simulator utility installed. Use -Xoffload:sim:help for usage You specified the -Xoffload:sim parameter when you started the JVM. The JVM runs with the -Xoffload:sim parameter options that you supplied. This message is for information only. No action is required. JVMOFFC002E Offload Simuator: Applying %d millisecond tax to each JNI call. You specified the -Xoffload:sim:delay option when you started the JVM. you specified. The JVM runs, applying the tax that This message is for information only. No action is required. JVMOFFC003E Offload Simuator: Applying %d microsecond tax to each JNI call. You started the JVM with the -Xoffload:sim:delay option with microseconds specified. specified. The JVM applies the tax that you This message is for information only. No action is required. JVMOFFC004E Offload Simuator: Delay tax using spin. You started the JVM with the -Xoffload:sim:delay option, and spinning is used to delay tax. The JVM uses spinning to apply the tax that you specified. This message is for information only. No action is required. JVMOFFC005E Offload Simuator: Delay tax using sleep. You started the JVM with the -Xoffload:sim:delay option, and sleeping is used to delay tax. The JVM uses sleeping to apply the tax that you specified. This message is for information only. No action is required. JVMOFFC007E Offload Simuator: Clock frequency is %llu ticks/second, have_nanosleep=%d You started the JVM with the -Xoffload:sim:delay option, which displays the clock frequency and whether nanosleep is supported. The have_nanosleep value is 0 when nanosleep is supported and nonzero otherwise. The JVM displays the clock frequency and whether nanosleep is supported. This message is for information only. No action is required. JVMOFFC008E Offload Simulator: Invalid sleep time, please choose a time >= 1 millisecond. You specified an invalid sleep time in the -Xoffload:sim:delay=Xms option. IBM JVM messages 35

44 JVMOFFC009E JVMOFFC029E Start the JVM again, specifying a sleep time that is greater than or equal to 1 millisecond. JVMOFFC009E Offload: Fatal error, unable to hook event You ran the JVM with the -Xoffload:sim option, and the JVM encountered an internal error. JVMOFFC010E Unrecognized time units -> %s The value of xx specified in -Xoffload:sim:delay=Yxx is not a valid time unit. Start the JVM again, specifying either ms or µs as the time units. JVMOFFC022I Offload Trace utility installed. Use -Xoffload:trace:help for usage You started the JVM with the -Xoffload:trace option. The JVM performs offload tracing. This message is for information only. No action is required. JVMOFFC023E Offload Trace: Tuning Fork logging to %s You specified the -Xoffload:trace:tuningfork option. fork. The JVM logs offload tracing to tuning This message is for information only. No action is required. JVMOFFC024I Offload: JNI Isolation enabled for library group {%s}. You started the JVM with the -Xoffload:isolate option, specifying one or more libraries. The native code in the libraries is run in external quarantines. This message is for information only. No action is required. JVMOFFC025E Offload:Failed to start quarantine controller with url=%s. Java offload was requested, but the Java process could not connect to the remote process. Ensure that there are no firewalls or other impediments to communication between the machine on which you invoked the Java process and the machine to which it is being offloaded. Then start the JVM again. JVMOFFC026E Offload:Invalid connection information for remote isolation. You specified remote isolation on the command line, but the connection information that you supplied is not valid. Correct the connection information that you specified on the command line, then start the JVM again. JVMOFFC027E Offload:Connection information missing for remote isolation. You specified remote isolation on the command line, but did not supply connection information. Add the connection information on the command line then start the JVM again. JVMOFFC028E Offload:Failed to start local quarantine controller. An internal error occurred when trying to start the JVM in offload mode. JVMOFFC029E Offload:Failed to create offload manager. An internal error occurred when trying to start the JVM in offload mode. 36 IBM SDK, Java Technology Edition: IBM JVM messages

45 JVMOFFC030E JVMPORT002E JVMOFFC030E Offload:Could not find local natives properties file {%s}. The file specifying the native code that is run locally could not be found. The message includes the location and name of the expected file. Restore the file from a copy of the JVM, then start the JVM again. The content of the file specifying the native code that is run locally is not valid. The message includes the name of the file from which the content is read. Restore the file from a copy of the JVM, then start the JVM again. JVMOFFC031E Offload:Local natives properties file has invalid format {%s}. PORT messages Port library messages. This section details messages that are generated by the port library component of the IBM JVM: v JVMPORT001E v JVMPORT002E v JVMPORT003E on page 38 v JVMPORT004E on page 38 v JVMPORT015E on page 38 v JVMPORT016E on page 38 v JVMPORT019W on page 38 v JVMPORT022I on page 38 v JVMPORT023W on page 38 v JVMPORT024E on page 39 v JVMPORT025E on page 39 v JVMPORT026E on page 39 v JVMPORT027E on page 39 v JVMPORT028E on page 39 v JVMPORT029E on page 39 v JVMPORT030W on page 39 v JVMPORT031E on page 39 v JVMPORT034W on page 40 v JVMPORT035E on page 40 v JVMPORT036E on page 40 v JVMPORT038E on page 40 v JVMPORT046E on page 40 v JVMPORT048E on page 40 JVMPORT001E Failed to allocate memory while attempting to write to a file. The system was unable to satisfy a memory allocation request. Subsequent memory allocation attempts are likely to fail, resulting in the termination of the process. Increase the amount of memory available to the process, or contact your IBM service JVMPORT002E Unknown error loading shared library IBM JVM messages 37

46 JVMPORT003E JVMPORT023W There was an unknown error loading a shared library. The process shuts down. This message is accompanied by another message that provides more detail. Check that the shared library exists. If the library exists, contact your IBM service JVMPORT003E Dependent module %s could not be loaded be loaded. The named dependent module could not If the module was critical to the JVM, the process ends. If the JVM ends, contact your IBM service JVMPORT004E Symbol resolution failure There was a problem with symbol resolution while looking for a particular symbol. If the symbol was critical to the JVM, the JVM ends, and more information is provided. If the JVM ends, contact your IBM service JVMPORT015E Unable to resolve shared library references - a prerequisite shared library may be missing The operating system could not resolve a shared library reference. A prerequisite shared library might be missing. process ends. If the library is critical to the JVM, the If the process ends, check that the library exists. If the library exists, contact your IBM service JVMPORT016E Internal Error %i An internal error occurred while looking for a shared library. process ends. If the library is critical to the JVM, the If the process ends, check that the library exists. If the library exists, contact your IBM service JVMPORT019W Unable to create directory %s. Shared classes will be disabled until this directory is created. You included a directory when you provided the name of the shared classes cache. This directory could not be created. If you specified the -Xshareclasses:nonfatal parameter, the JVM continues without using shared classes. If you did not specify that parameter, the JVM ends. JVMPORT022I Appending.X&DS to user-specified dump template to enable multi-part dumps. You specified a dump template, by using the -Xdump:system:file= parameter or the JAVA_DUMP_TDUMP_PATTERN environment variable. The maximum amount of data that can be dumped in a single IEATDUMP file is 2 GB. For address spaces larger than 2 GB, the z/os operating system generates multiple dump files. To enable this behavior, the suffix &DS is required in the dump name. The suffix is replaced with a counter that identifies which part of the dump is in the file. If you do not add the suffix, the JVM appends it to the dump template. The JVM adds.x&ds to the dump template, then continues to run. You can ignore this message, and allow the JVM to alter the dump file name, unless the extended dump file name is too long. If the file name is too long, the JVM uses the default dump template instead. Avoid the message by including the &DS suffix in your dump template or by using the default dump template. JVMPORT023W IEATDUMP failed because user-specified dump template was too long. Retrying dump with default template. You specified a dump template, by using the -Xdump:system:file= parameter or the JAVA_DUMP_TDUMP_PATTERN environment variable. When the system tried to take a dump by using the template, the IEATDUMP routine returned with return code 0x8 and reason code 0x22, indicating that the dump failed because the name was too long. The JVM tries to take the dump again using the default dump template. Specify a shorter dump template. Note that, on the z/os 64 operating system, the JVM appends.x&ds to the user-specified dump template, to enable multi-part z/os dumps (required to store a full 64-bit address space). If the template you specified was 38 IBM SDK, Java Technology Edition: IBM JVM messages

47 JVMPORT024E JVMPORT031E close to 44 characters long, the addition of.x&ds might make it too long. JVMPORT024E IEATDUMP failed because we couldn't allocate the dump dataset (likely disk full). The JVM attempted to take an IEATDUMP, but the dump routine returned with return code 0x8 and reason code 0x26, indicating that the dump failed because the dump data set could not be allocated. a dump. The JVM continues, but fails to create The most common cause for this error message is that you have run out of space for dump data sets. Check your available dump storage. JVMPORT025E Invalid lock type for file lock operation. lockflags: %1$d A file lock operation failed because the value of the flag that specifies the lock type was not valid. The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries. JVMPORT026E File specified is a directory A file-open operation failed when the system attempted to open a directory as a file. The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries. JVMPORT027E mmap failed due to invalid memory protection parameter. The value for the memory protection parameter is not valid. The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries. JVMPORT028E mmap failed due to invalid mapping options. The value for the flag parameter that specifies mapping options is not valid. The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries. JVMPORT029E Invalid handle. file handle: %1$d. A file map operation failed because a file handle was not valid. The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries. JVMPORT030W %s setting "%s" specifies that the core dump is to be piped to an external program. Attempting to rename either core or core.%d. Linux tools such as ABRT and Apport use the information in the /proc/sys/kernel/ core_pattern file to redirect the core file to an external program, for example to create bug reports. The virtual machine looks in the current directory for a file called either core or core.process ID, depending on the contents of the /proc/sys/kernel/core_uses_pid file. Refer to the documentation for the external program specified in the /proc/sys/kernel/ core_pattern file. JVMPORT031E The LE condition %s%i, which corresponds to a software-raised POSIX signal, was received The JVM was instructed at startup to run with Language Environment (LE) condition handlers instead of POSIX signal handlers. A LE condition that corresponds to a software-raised POSIX signal was received. The JVM creates a dump containing diagnostic data and ends. IBM JVM messages 39

48 JVMPORT034W JVMPORT048E JVMPORT034W Attempted to attach shared memory created in storage protection key %lu, but currently running in key %lu. Shared memory could not be opened because the z/os storage protection key used to create the shared memory is not compatible with the current storage protection key. None. Any problems are reported using a different message. Check for other error messages. JVMPORT035E malloc31 failed to allocate buffer on z/os a buffer. The malloc31 process failed to allocate The JVM continues, but hypervisor related information is not provided. JVMPORT036E Unexpected return code from CSRSI service on z/os An unexpected return code is received from the CSRSI service on z/os. The JVM continues, but hypervisor related information is not provided. JVMPORT048E Failed to create system dump because a non-regular file \"%s\" exists with the same name as the expected system dump file The JVM did not produce a system dump because a non-regular file exists with the same name as the expected system dump file. The non-regular file might be a directory, symbolic link, pipe, or socket. Check whether the name of a non-regular file in the current working directory of the Java application clashes with one of the following names or settings: v v The default system dump file name, which is core or core.<process ID>. The setting of /proc/sys/kernel/core_pattern and /proc/sys/kernel/core_uses_pid. Rename the non-regular file or change the settings of /proc/sys/kernel/core_pattern and /proc/sys/kernel/core_uses_pid and try again. JVMPORT038E Malformed value for IBM_JAVA_HYPERVISOR_SETTINGS The IBM_JAVA_HYPERVISOR_SETTINGS environment variable is missing a closing quote character. Correct the IBM_JAVA_HYPERVISOR_SETTINGS environment variable and try again. JVMPORT046E The executable could not be opened The executable file could not be opened. The process shuts down. This message is accompanied by another message that provides more detail. 40 IBM SDK, Java Technology Edition: IBM JVM messages

49 SHRC messages Shared classes messages. This section details messages that are generated by IBM JVM class data sharing: v JVMSHRC004E on page 48 v JVMSHRC005I on page 48 v JVMSHRC006I on page 48 v JVMSHRC007I on page 49 v JVMSHRC010I on page 49 v JVMSHRC012I on page 49 v JVMSHRC013E on page 49 v JVMSHRC014E on page 49 v JVMSHRC015E on page 49 v JVMSHRC017E on page 49 v JVMSHRC018E on page 49 v JVMSHRC019E on page 49 v JVMSHRC020E on page 50 v JVMSHRC021E on page 50 v JVMSHRC022E on page 50 v JVMSHRC023E on page 50 v JVMSHRC024E on page 50 v JVMSHRC025E on page 50 v JVMSHRC026E on page 50 v JVMSHRC027E on page 50 v JVMSHRC028E on page 51 v JVMSHRC029E on page 51 v JVMSHRC030E on page 51 v JVMSHRC057E on page 51 v JVMSHRC058E on page 51 v JVMSHRC059E on page 51 v JVMSHRC060E on page 51 v JVMSHRC061E on page 51 v JVMSHRC063E on page 52 v JVMSHRC064E on page 52 v JVMSHRC065E on page 52 v JVMSHRC066I on page 52 v JVMSHRC067I on page 52 v JVMSHRC068I on page 52 v JVMSHRC069I on page 52 v JVMSHRC070I on page 52 v JVMSHRC071E on page 52 v JVMSHRC072E on page 52 v JVMSHRC077E on page 53 v JVMSHRC080E on page 53 v JVMSHRC082E on page 53 IBM JVM messages 41

50 v JVMSHRC083E on page 53 v JVMSHRC084E on page 53 v JVMSHRC086E on page 53 v JVMSHRC087E on page 53 v JVMSHRC088E on page 53 v JVMSHRC089E on page 54 v JVMSHRC090E on page 54 v JVMSHRC091E on page 54 v JVMSHRC092E on page 54 v JVMSHRC093I on page 54 v JVMSHRC095E on page 54 v JVMSHRC096I on page 54 v JVMSHRC097E on page 54 v JVMSHRC125E on page 54 v JVMSHRC126E on page 55 v JVMSHRC127E on page 55 v JVMSHRC128E on page 55 v JVMSHRC129E on page 55 v JVMSHRC130E on page 55 v JVMSHRC134E on page 55 v JVMSHRC137E on page 55 v JVMSHRC147E on page 55 v JVMSHRC154E on page 55 v JVMSHRC155E on page 56 v JVMSHRC156E on page 56 v JVMSHRC157I on page 56 v JVMSHRC158I on page 56 v JVMSHRC159I on page 56 v JVMSHRC160E on page 56 v JVMSHRC161E on page 56 v JVMSHRC162E on page 56 v JVMSHRC166I on page 56 v JVMSHRC168I on page 57 v JVMSHRC169I on page 57 v JVMSHRC171E on page 57 v JVMSHRC172E on page 57 v JVMSHRC179E on page 57 v JVMSHRC180E on page 57 v JVMSHRC181E on page 57 v JVMSHRC190E on page 57 v JVMSHRC191I on page 57 v JVMSHRC192I on page 57 v JVMSHRC202E on page 58 v JVMSHRC203E on page 58 v JVMSHRC204E on page IBM SDK, Java Technology Edition: IBM JVM messages

51 v JVMSHRC220E on page 58 v JVMSHRC221E on page 58 v JVMSHRC222E on page 58 v JVMSHRC223E on page 58 v JVMSHRC225E on page 58 v JVMSHRC226E on page 58 v JVMSHRC227E on page 59 v JVMSHRC228E on page 59 v JVMSHRC229E on page 59 v JVMSHRC230E on page 59 v JVMSHRC231E on page 59 v JVMSHRC232E on page 59 v JVMSHRC233E on page 59 v JVMSHRC234E on page 59 v JVMSHRC235E on page 59 v JVMSHRC236I on page 60 v JVMSHRC237I on page 60 v JVMSHRC241E on page 60 v JVMSHRC242E on page 60 v JVMSHRC244E on page 60 v JVMSHRC245E on page 60 v JVMSHRC246I on page 60 v JVMSHRC247E on page 60 v JVMSHRC250E on page 60 v JVMSHRC254E on page 60 v JVMSHRC255E on page 60 v JVMSHRC256I on page 61 v JVMSHRC257E on page 61 v JVMSHRC258E on page 61 v JVMSHRC259E on page 61 v JVMSHRC260E on page 61 v JVMSHRC269I on page 61 v JVMSHRC271E on page 61 v JVMSHRC272I on page 61 v JVMSHRC273I on page 61 v JVMSHRC274I on page 62 v JVMSHRC277E on page 62 v JVMSHRC278I on page 62 v JVMSHRC282I on page 62 v JVMSHRC284E on page 62 v JVMSHRC285I on page 62 v JVMSHRC286I on page 62 v JVMSHRC287E on page 62 v JVMSHRC291E on page 62 v JVMSHRC292E on page 62 IBM JVM messages 43

52 v JVMSHRC296I on page 63 v JVMSHRC297I on page 63 v JVMSHRC298E on page 63 v JVMSHRC318E on page 63 v JVMSHRC319E on page 63 v JVMSHRC320E on page 63 v JVMSHRC321E on page 63 v JVMSHRC322E on page 63 v JVMSHRC323E on page 63 v JVMSHRC324E on page 64 v JVMSHRC327E on page 64 v JVMSHRC328E on page 64 v JVMSHRC329E on page 64 v JVMSHRC330E on page 64 v JVMSHRC334E on page 64 v JVMSHRC335E on page 64 v JVMSHRC336E on page 64 v JVMSHRC337E on page 64 v JVMSHRC338E on page 65 v JVMSHRC339E on page 65 v JVMSHRC340E on page 65 v JVMSHRC361E on page 65 v JVMSHRC363E on page 65 v JVMSHRC364E on page 65 v JVMSHRC375E on page 65 v JVMSHRC404E on page 65 v JVMSHRC405E on page 66 v JVMSHRC428I on page 66 v JVMSHRC429I on page 66 v JVMSHRC430I on page 66 v JVMSHRC434E on page 66 v JVMSHRC435I on page 66 v JVMSHRC436E on page 66 v JVMSHRC437E on page 66 v JVMSHRC442E on page 66 v JVMSHRC443I on page 67 v JVMSHRC444I on page 67 v JVMSHRC445E on page 67 v JVMSHRC446E on page 67 v JVMSHRC447E on page 67 v JVMSHRC448E on page 67 v JVMSHRC449E on page 67 v JVMSHRC450E on page 67 v JVMSHRC451E on page 67 v JVMSHRC457E on page IBM SDK, Java Technology Edition: IBM JVM messages

53 v JVMSHRC461E on page 68 v JVMSHRC462I on page 68 v JVMSHRC463I on page 68 v JVMSHRC488E on page 68 v JVMSHRC500E on page 68 v JVMSHRC501E on page 68 v JVMSHRC502E on page 68 v JVMSHRC503E on page 68 v JVMSHRC504E on page 68 v JVMSHRC505E on page 69 v JVMSHRC506E on page 69 v JVMSHRC508E on page 69 v JVMSHRC511I on page 69 v JVMSHRC514E on page 69 v JVMSHRC517E on page 69 v JVMSHRC547E on page 69 v JVMSHRC549E on page 69 v JVMSHRC550E on page 69 v JVMSHRC551E on page 70 v JVMSHRC552E on page 70 v JVMSHRC557E on page 70 v JVMSHRC559E on page 70 v JVMSHRC549E on page 69 v JVMSHRC550E on page 69 v JVMSHRC550E on page 69 v JVMSHRC551E on page 70 v JVMSHRC552E on page 70 v JVMSHRC557E on page 70 v JVMSHRC559E on page 70 v JVMSHRC560E on page 70 v JVMSHRC561E on page 70 v JVMSHRC562I on page 70 v JVMSHRC572E on page 70 v JVMSHRC590E on page 70 v JVMSHRC594E on page 71 v JVMSHRC595E on page 71 v JVMSHRC598E on page 71 v JVMSHRC599E on page 71 v JVMSHRC600E on page 71 v JVMSHRC605E on page 71 v JVMSHRC611E on page 71 v JVMSHRC613E on page 71 v JVMSHRC614E on page 71 v JVMSHRC615E on page 72 v JVMSHRC616E on page 72 IBM JVM messages 45

54 v JVMSHRC617E on page 72 v JVMSHRC618E on page 72 v JVMSHRC619E on page 72 v JVMSHRC620E on page 72 v JVMSHRC621E on page 72 v JVMSHRC622E on page 72 v JVMSHRC623E on page 73 v JVMSHRC624E on page 73 v JVMSHRC625E on page 73 v JVMSHRC626I on page 73 v JVMSHRC627I on page 73 v JVMSHRC628E on page 73 v JVMSHRC629E on page 73 v JVMSHRC630I on page 73 v JVMSHRC631I on page 74 v JVMSHRC632I on page 74 v JVMSHRC633E on page 74 v JVMSHRC634E on page 74 v JVMSHRC637E on page 74 v JVMSHRC638I on page 74 v JVMSHRC639E on page 74 v JVMSHRC646E on page 75 v JVMSHRC647E on page 75 v JVMSHRC648E on page 75 v JVMSHRC649E on page 75 v JVMSHRC650E on page 75 v JVMSHRC651E on page 75 v JVMSHRC652E on page 75 v JVMSHRC653E on page 75 v JVMSHRC654E on page 76 v JVMSHRC656E on page 76 v JVMSHRC657E on page 76 v JVMSHRC658E on page 76 v JVMSHRC659E on page 76 v JVMSHRC660E on page 76 v JVMSHRC661E on page 76 v JVMSHRC662E on page 77 v JVMSHRC663I on page 77 v JVMSHRC664E on page 77 v JVMSHRC665E on page 77 v JVMSHRC666E on page 77 v JVMSHRC667I on page 77 v JVMSHRC668E on page 77 v JVMSHRC669E on page 78 v JVMSHRC670I on page IBM SDK, Java Technology Edition: IBM JVM messages

55 v JVMSHRC671E on page 78 v JVMSHRC672E on page 78 v JVMSHRC673E on page 78 v JVMSHRC674E on page 78 v JVMSHRC675E on page 78 v JVMSHRC676E on page 78 v JVMSHRC677E on page 78 v JVMSHRC678E on page 79 v JVMSHRC679E on page 79 v JVMSHRC680E on page 79 v JVMSHRC681E on page 79 v JVMSHRC682E on page 79 v JVMSHRC683E on page 79 v JVMSHRC684E on page 79 v JVMSHRC685E on page 80 v JVMSHRC686I on page 80 v JVMSHRC687E on page 80 v JVMSHRC697E on page 80 v JVMSHRC698I on page 80 v JVMSHRC699E on page 80 v JVMSHRC700I on page 80 v JVMSHRC701E on page 80 v JVMSHRC702I on page 80 v JVMSHRC703E on page 81 v JVMSHRC704E on page 81 v JVMSHRC705E on page 81 v JVMSHRC706E on page 81 v JVMSHRC707E on page 81 v JVMSHRC708E on page 81 v JVMSHRC710E on page 81 v JVMSHRC711E on page 81 v JVMSHRC713E on page 81 v JVMSHRC714I on page 82 v JVMSHRC715I on page 82 v JVMSHRC716I on page 82 v JVMSHRC717I on page 82 v JVMSHRC718E on page 82 v JVMSHRC719I on page 82 v JVMSHRC720I on page 82 v JVMSHRC721E on page 82 v JVMSHRC722E on page 82 v JVMSHRC723E on page 82 v JVMSHRC724E on page 83 v JVMSHRC725E on page 83 v JVMSHRC726E on page 83 IBM JVM messages 47

56 JVMSHRC004E JVMSHRC006I v JVMSHRC727E on page 83 v JVMSHRC728E on page 83 v JVMSHRC729E on page 83 v JVMSHRC730I on page 83 v JVMSHRC731I on page 83 v JVMSHRC732I on page 83 v JVMSHRC733I on page 84 v JVMSHRC735I on page 84 v JVMSHRC743E on page 84 v JVMSHRC744I on page 84 v JVMSHRC745I on page 84 v JVMSHRC746I on page 84 v JVMSHRC747E on page 84 v JVMSHRC748E on page 84 v JVMSHRC749E on page 84 v JVMSHRC750I on page 84 v JVMSHRC751E on page 84 v JVMSHRC752E on page 85 v JVMSHRC753E on page 85 v JVMSHRC754I on page 85 v JVMSHRC762E on page 85 v JVMSHRC765I on page 85 v JVMSHRC769I on page 85 v JVMSHRC773I on page 85 v JVMSHRC777I on page 85 v JVMSHRC781I on page 85 v JVMSHRC782I on page 85 v JVMSHRC816I on page 86 v JVMSHRC817I on page 86 v JVMSHRC818I on page 86 v JVMSHRC823I on page 86 v JVMSHRC828I on page 86 v JVMSHRC833I on page 86 v JVMSHRC838I on page 86 v JVMSHRC843I on page 86 JVMSHRC004E Cannot destroy cache "%s" destroyed. The shared class cache could not be Processing continues. Other messages might indicate the reason why the cache has not been destroyed. Investigate these messages. JVMSHRC005I No shared class caches available There are no shared class caches on the system that can be processed by the command requested. Processing continues. No action is required. JVMSHRC006I Number of caches expired within last %1$d minutes is %2$d This is an information message. Processing continues. No action is required. 48 IBM SDK, Java Technology Edition: IBM JVM messages

57 JVMSHRC007I JVMSHRC019E JVMSHRC007I Failed to remove shared class cache "%s" removed. The shared class cache could not be Processing continues. Other messages might indicate the reason why the cache has not been removed. Investigate these messages. JVMSHRC010I Shared cache "%s" is destroyed The shared class cache has been destroyed as requested. A JVM is not created and a failure message is issued, as expected. No action is required. This is an information message issued when you destroy a shared class cache. JVMSHRC012I Cannot remove shared cache "%s" as there are JVMs still attached to the cache The shared class cache cannot be removed because a process, or processes, are still attached. The JVM ends, unless you have Wait until any processes using the shared class cache have ended and then remove it. JVMSHRC013E Shared cache "%s" memory remove failed The shared class cache cannot be removed because there is shared memory associated with the cache that cannot be removed. The JVM ends, unless you have JVMSHRC014E Shared cache "%s" semaphore remove failed The shared class cache cannot be removed because there is a shared semaphore associated with the cache that cannot be removed. The JVM ends, unless you have JVMSHRC015E Shared Class Cache Error: Invalid flag An error occurred during shared class The JVM ends, unless you have JVMSHRC017E Error code: %d This message shows the error code relating to a error that will have been the subject of a previous message. The JVM ends, unless you have "-Xshareclasses:nonfatal", in which case the JVM representative, unless previous messages indicate a different response. JVMSHRC018E cannot allocate memory memory. The system is unable to obtain sufficient The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC019E request length is too small The size requested for the shared class cache is too small. The JVM ends, unless you have Increase the size for the shared class cache using the -Xscmx parameter or allow it to take the default value by not specifying the -Xscmx option. IBM JVM messages 49

58 JVMSHRC020E JVMSHRC027E JVMSHRC020E An error has occurred while opening semaphore An error has occurred during shared Further messages might follow, providing more detail. The JVM ends, unless you have representative, unless subsequent messages indicate otherwise. JVMSHRC021E An unknown error code has been returned An error has occurred during shared This message is followed by details of the numeric error code returned. The JVM ends, unless you have JVMSHRC022E Error creating shared memory region An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC023E Cache does not exist An attempt has been made to open a shared class cache that does not exist. The JVM ends, unless you have JVMSHRC024E shared memory detach error An error has occurred during shared The JVM ends, unless you have JVMSHRC025E error attaching shared memory An error has occurred during shared If the cache is damaged, the JVM attempts to re-create it. Otherwise the JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC026E Cannot create cache of requested size: Please check your SHMMAX and SHMMIN settings The system cannot create a shared class cache of the size requested by the -Xscmx parameter. If -Xscmx is not specified the default is 16MB. The JVM ends, unless you have Refer to the product documentation for information about shared memory size limits for your operating system. Restart the JVM with an acceptable shared cache size. JVMSHRC027E Shared cache name is too long The name specified for the shared class cache is too long for the operating system. The JVM ends, unless you have Specify a shorter name for the shared class cache and restart the JVM. 50 IBM SDK, Java Technology Edition: IBM JVM messages

59 JVMSHRC028E JVMSHRC061E JVMSHRC028E Permission Denied The system does not have permission to access a system resource. The JVM ends, unless you have Check earlier messages to find the resource that cannot be accessed. Only the user who creates the shared class cache has access to it, unless the -Xshareclasses:groupAccess option is specified. In this case, a user must belong to the same group as the user who created the shared class cache. JVMSHRC058E Cannot allocate memory for ClasspathItem in shrinit::hookstoresharedclass An error has occurred in shared class The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC029E Not enough memory left on the system There is not enough memory available to create the shared cache memory or semaphore. A previous message indicates the shared cache memory or semaphore concerned. The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC030E The Shared Class Cache you are attaching has invalid header. The shared class cache you are trying to use is invalid. If the cache is damaged, the JVM attempts to re-create it. Otherwise the JVM ends, unless you have JVMSHRC057E Wrong parameters for expire option The value specified for the expire parameter of -Xshareclasses is invalid. The JVM ends, unless you have Correct the value for the expire option and restart the JVM. The value must be a positive integer. JVMSHRC059E Cannot allocate memory for ClasspathItem in shrinit::hookfindsharedclass An error has occurred in shared class The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC060E Cannot allocate memory for string buffer in shrinit::hookfindsharedclass An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC061E Cache name should not be longer than 64 chars. Cache not created. The name of the shared class cache specified to the JVM exceeds the maximum length. The JVM ends, unless you have Change the shared class cache name so that it does not exceed the maximum allowed length. IBM JVM messages 51

60 JVMSHRC063E JVMSHRC072E JVMSHRC063E Cannot allocate memory for sharedclassconfig in shrinit An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC064E Failed to create configmonitor in shrinit An error has occurred during shared The JVM ends, unless you have This might be due to problems with the operating system. Restart the JVM. If the situation persists, contact your IBM service JVMSHRC065E Cannot allocate pool in shrinit An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC066I Locking of local hashtables disabled This message confirms that locking of local hashtables for the shared class cache has been disabled as requested. No action is required. The message is issued when verbose messages are requested. JVMSHRC067I Timestamp checking disabled This message confirms that shared classes timestamp checking has been disabled as requested. No action is required. The message is issued when verbose messages are requested. JVMSHRC068I Local caching of classpaths disabled This message indicates that the caching of classpaths in the shared class cache has been disabled as requested. No action is required. The message is issued when verbose messages are requested. JVMSHRC069I Concurrent store contention reduction disabled This message confirms that shared classes concurrent store contention reduction has been disabled as requested. No action is required. The message is issued when verbose messages are requested. JVMSHRC070I Incremental updates disabled This message confirms that shared classes incremental updates have been disabled as requested. No action is required. The message is issued when verbose messages are requested. JVMSHRC071E Command-line option "%s" requires sub-option The specified command-line option requires further information. The JVM ends, unless you have try again. Update the command-line option and JVMSHRC072E Command-line option "%s" unrecognized The specified command-line option is not recognized. The JVM ends, unless you have Correct or remove the invalid command-line option and try again. 52 IBM SDK, Java Technology Edition: IBM JVM messages

61 JVMSHRC077E JVMSHRC088E JVMSHRC077E Failed to create linkedlistimpl pool in SH_ClasspathManagerImpl2 An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC084E Cannot allocate memory for linked list item An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC080E Cannot allocate memory for hashtable entry An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC086E Cannot enter ClasspathManager hashtable mutex An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC082E Cannot create identifiedmutex in SH_ClasspathManagerImpl2 An error has occurred in shared class The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC083E Cannot allocate memory for identifiedclasspaths array in SH_ClasspathManagerImpl2 An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC087E MarkStale failed during ClasspathManager::update() An error has occurred during shared The JVM ends, unless you have JVMSHRC088E Failed to create cache as ROMImageSegment in SH_CacheMap An error has occurred during shared The JVM ends, unless you have IBM JVM messages 53

62 JVMSHRC089E JVMSHRC125E JVMSHRC089E Cannot create refresh mutex in SH_CacheMap An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC090E Failed to get cache mutex in SH_CacheMap startup An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC091E Read corrupt data for item 0x%p (invalid datatype) An error has occurred during shared The cache is marked as corrupt and the JVM continues. JVMSHRC092E ADD failure when reading cache An error has occurred during shared The JVM ends, unless you have JVMSHRC093I Detected unexpected termination of another JVM during update The JVM detected that another JVM ended unexpectedly while updating the shared class cache. No action required. This message is for information only. JVMSHRC095E Attempts to call markstale on shared cache items have failed An error has occurred during shared The JVM ends, unless you have JVMSHRC096I Shared cache "%s" is full. Use -Xscmx to set cache size. The named shared class cache is full and no further classes can be added to it. The named shared cache is still operational and continues to provide increased performance for loading the classes it contains. However, classes not contained in the cache are loaded from their source. To gain the full benefit of shared classes, delete and re-create the named cache. Specify a larger shared class cache size using the -Xscmx parameter. JVMSHRC097E Shared cache "%s" is corrupt. No new JVMs will be allowed to connect to the cache. Existing JVMs can continue to function, but cannot update the cache. The shared class cache named in the message is damaged. The JVM attempts to re-create the cache before starting. If the cache cannot be re-created the JVM ends, unless you have specified the nonfatal option with -Xshareclasses:nonfatal. Remove the shared class cache named in the message and restart the JVM. If the situation persists, contact your IBM service JVMSHRC125E Could not allocate memory for string buffer in SH_CacheMap An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If 54 IBM SDK, Java Technology Edition: IBM JVM messages

63 JVMSHRC126E JVMSHRC154E the situation persists, contact your IBM service JVMSHRC126E Request made to add too many items to ClasspathItem An error has occurred during shared JVMSHRC127E SH_CompositeCache::enterMutex failed with return code %d. Warning: your cache may be corrupt. An error has occurred while trying to update the shared class cache. The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC128E SH_CompositeCache::exitMutex failed with return code %d. Warning: your cache may be corrupt. An error has occurred while trying to update the shared class cache. JVMSHRC129E Attempt to set readercount to -1! An error has occurred while trying to update the shared class cache. JVMSHRC130E Attempt to allocate while commit is still pending An error has occurred while updating the shared class cache. Processing continues, if possible. JVMSHRC134E Failed to create pool in SH_ROMClassManagerImpl An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC137E SAFE MODE: Warning: ROMClass %.*s does not match ROMClass in cache This message is issued when running shared classes in safe mode and a mismatch in ROMClass bytes is detected. This message will be followed by further details of the class sizes and details of the mismatched bytes. None required. This message is for information only. The mismatch in bytes does not mean that an error has occurred, but could indicate, for example, that the class has changed since originally stored in the cache. JVMSHRC147E Character %.*s not valid for cache name The shared class cache name specified to the JVM contains invalid characters. The JVM ends, unless you have Correct the shared class cache name so that all characters are valid and restart the JVM. JVMSHRC154E Escape character %.*s not valid for cache name An invalid escape character has been specified in a shared class cache name. The JVM ends, unless you have Specify a valid escape character. Valid escape characters are %%u for username and %%g for group name. Group name is not valid for Windows. IBM JVM messages 55

64 JVMSHRC155E JVMSHRC166I JVMSHRC155E Error copying username into cache name The system could not obtain the username for inclusion in the shared class cache name. The JVM ends, unless you have JVMSHRC156E Error copying groupname into cache name The system could not obtain the groupname for inclusion in the shared class cache name. The JVM ends, unless you have JVMSHRC157I Unable to allocate %1$d bytes of shared memory requested. Succesfully allocated maximum shared memory permitted (%2$d bytes). (To increase available shared memory, modify system SHMMAX value) The system could not create a shared class cache of the size requested (1$). A cache of the maximum size permitted for the system is created. If you require a larger cache, remove and re-create the cache, increasing the value of SHMMAX. JVMSHRC158I Created shared class cache "%1$s" A shared class cache with the given name has been created. No action is required. This message is issued when verbose shared class messages are requested. JVMSHRC159I Opened shared class cache "%1$s" opened. An existing shared class cache has been No action is required. This message is issued when verbose shared class messages are requested. JVMSHRC160E The wait for the creation mutex while opening semaphore has timed out An error has occurred with shared classes The JVM ends, unless you have If the condition persists, contact your IBM service JVMSHRC161E The wait for the creation mutex while creating shared memory has timed out An error has occurred with shared classes The JVM ends, unless you have If the condition persists, contact your IBM service JVMSHRC162E The wait for the creation mutex while opening shared memory has timed out An error has occurred with shared classes The JVM ends, unless you have If the condition persists, contact your IBM service JVMSHRC166I Attached to cache "%1$s", size=%2$d bytes The JVM is attached to the cache named 1$, which is 2$ bytes in size. No action is required. This message is issued when verbose shared class messages are requested. 56 IBM SDK, Java Technology Edition: IBM JVM messages

65 JVMSHRC168I JVMSHRC192I JVMSHRC168I Total shared class bytes read=%1$lld. Total bytes stored=%2$d This message details the number of bytes read from the shared classes cache (1$), and the number of bytes stored in the cache (2$). No action is required. This message is issued when verbose shared class messages are requested, and the JVM ends. JVMSHRC169I Change detected in %2$.*1$s......marked %3$d cached classes stale A change is detected in classpath 2$, causing 3$ classes to be marked as "stale" in the shared classes cache. No action is required. This message is issued when verbose shared class messages are requested. JVMSHRC171E z/os cannot create cache of requested size: Please check your z/os system BPXPRMxx settings z/os cannot create a shared classes cache of the requested size. The JVM ends, unless you have If you need a cache of this size, ask your system programmer to increase the z/os system BPXPRMxx settings. JVMSHRC172E Cannot create cache of requested size due to Operating System restrictions The size of the cache you requested cannot be created by the operating system. The JVM ends, unless you have Refer to information about cache size limits in the Java documentation. JVMSHRC179E The ROMClass segment has been corrupted. Error reading ROMClass at 0x%p An error has occurred during shared The JVM ends, unless you have JVMSHRC180E Cannot allocate memory for hashtable entry in ScopeManagerImpl An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC181E Cannot enter ScopeManagerImpl hashtable mutex An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC190E -Xscminaot value should not be greater than -Xscmaxaot value The value for -Xscminaot cannot be greater than -Xscmaxaot. Change the value of -Xscminaot to be less than -Xscmaxaot. JVMSHRC191I -Xscminaot value is greater than -Xscmx value, so it has been set to equal -Xscmx value The value for -Xscminaot cannot be greater than -Xscmx. No action is required. The value is changed automatically. JVMSHRC192I -Xscmaxaot value is greater than -Xscmx value, so it has been set to unlimited The value for -Xscmaxaot cannot be greater than -Xscmx. IBM JVM messages 57

66 JVMSHRC202E JVMSHRC226E No action is required. The value is changed automatically. JVMSHRC202E Failed to initialize pools in shared class Manager An error has occurred while initializing shared classes. The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC203E Cannot create hashtable in shared class Manager An error has occurred while initializing shared classes. The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC204E Cannot create hashtable mutex in shared class Manager An error has occurred while initializing shared classes. The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC220E Port layer error code = %1$d This message shows the last portable error code stored in the J9 Port layer. It indicates the last error encountered. The JVM ends, unless -Xshareclasses:nonfatal is specified, in which case it JVMSHRC221E Platform error message: %1$s This message shows the last portable error code stored in the J9 Port layer, indicating the last error encountered. The JVM ends, unless you have JVMSHRC222E Persistent shared class caches cannot be created/used as memory mapping does not support the required capabilities An error has occurred during shared The JVM ends, unless you have JVMSHRC223E Persistent shared class caches cannot be created/used as file locking is not supported An error has occurred during shared The JVM ends, unless you have JVMSHRC225E Error obtaining cache file path An error has occurred during shared The JVM ends, unless you have JVMSHRC226E Error opening shared class cache file An error has occurred during shared The JVM ends, unless you have 58 IBM SDK, Java Technology Edition: IBM JVM messages

67 JVMSHRC227E JVMSHRC235E JVMSHRC227E Error acquiring shared class cache file header write lock An error has occurred during shared The JVM ends, unless you have JVMSHRC228E Error updating shared class cache last attached time An error has occurred during shared The JVM ends, unless you have JVMSHRC229E Error: shared class cache file has an invalid header An error has occurred during shared The JVM ends, unless you have JVMSHRC230E Error initialising shared cache data header An error has occurred during shared The JVM ends, unless you have JVMSHRC231E Error setting shared class cache file length An error has occurred during shared The JVM ends, unless you have JVMSHRC232E Cannot create a cache in readonly mode An error has occurred within shared classes The JVM ends, unless you have Remove the read-only option from the command-line and restart the JVM. JVMSHRC233E Error creating shared class cache file header An error has occurred during shared The JVM ends, unless you have JVMSHRC234E Error acquiring shared class cache file attach read lock An error has occurred during shared The JVM ends, unless you have JVMSHRC235E Error releasing shared class cache file attach read lock An error has occurred during shared The JVM ends, unless you have IBM JVM messages 59

68 JVMSHRC236I JVMSHRC255E JVMSHRC236I Created shared classes persistent cache %1$s Shared cache %1$s has been created as a persistent cache. This message is produced when -Xshareclasses:verbose is specified. No action is required. JVMSHRC237I Opened shared classes persistent cache %1$s Shared classes persistent cache %1$s has been opened. This message is produced when -Xshareclasses:verbose is specified. No action is required. JVMSHRC241E Error: unable to delete shared class cache file An error has occurred during shared JVMSHRC242E Error updating shared class cache file last detached time An error has occurred during shared JVMSHRC244E Error obtaining shared class cache file length An error has occurred during shared The JVM ends, unless you have JVMSHRC245E Error mapping shared class cache file An error has occurred during shared The JVM ends, unless you have JVMSHRC246I Attached shared classes persistent cache %1$s Shared classes persistent cache %1$s has been successfully attached to the process. This message might appear multiple times in verbose output. No action is required. JVMSHRC247E Error shared class cache file header eyecatcher is invalid An error has occurred during shared The JVM ends, unless you have JVMSHRC250E Cache cannot be opened read-only as it has not yet initialized The cache has not completed initialization and cannot be opened in read-only mode. The JVM ends, unless you have Wait until the cache has initialized or remove the read-only option. JVMSHRC254E Error setting length of shared class cache file An error has occurred during shared The JVM ends, unless you have JVMSHRC255E Error updating shared class cache file last detached time on JVM exit An error has occurred during shared 60 IBM SDK, Java Technology Edition: IBM JVM messages

69 JVMSHRC256I JVMSHRC273I The JVM ends, unless you have JVMSHRC256I Persistent shared cache "%1$s" has been destroyed The shared cache 1$ has been removed as requested. This message is only issued if verbose shared classes messages has been requested with -Xshareclasses:verbose. ends. When the cache is removed, the JVM No action is required. JVMSHRC257E Cannot allocate memory for linked list item in Manager An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC258E Cannot allocate memory for hashtable entry in Manager An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC259E Cannot enter Manager hashtable mutex An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC260E Failed to create pool in ByteDataManager An error has occurred during shared The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC269I The system does not support memory page protection Memory page protection is not supported on the runtime platform. This feature is disabled. Pages of the shared class cache are not protected against accidental corruption. No action is required. JVMSHRC271E Unrecognised sub-option for option mprotect= The sub-option you provided for mprotect= was not recognized. the JVM. Provide a valid sub-option and restart JVMSHRC272I Full memory page protection successfully enabled for cache Every memory page of the cache has been protected. If any page of the cache is accessed illegally, the JVM ends. No action is required. JVMSHRC273I Default memory page protection successfully enabled for cache All memory pages of the cache containing runtime data have been protected. If any protected page of the cache is accessed illegally, the JVM will end. No action is required. IBM JVM messages 61

70 JVMSHRC274I JVMSHRC292E JVMSHRC274I Memory page protection disabled for cache The cache memory is not protected against accidental corruption. The cache is not protected. No action is required. JVMSHRC277E To run "%s" utility on nonpersistent class cache "%s", you must also use "nonpersistent" suboption The JVM cannot run the utility on the nonpersistent cache because it needs the nonpersistent suboption set. Add the nonpersistent suboption and restart the JVM. JVMSHRC278I Note that utility "%s" cannot operate on incompatible class cache "%s". Please use a JVM of the correct level. The JVM cannot run the utility on the cache because it is not compatible. No action is required. JVMSHRC282I The page size of the operating system is incompatible with this cache. Attempting to re-create the cache. The cache is divided up on page boundaries. If there is a page size mismatch, the cache is unusable. the cache. The JVM tries to remove and re-create No action is required. JVMSHRC284E Cannot create a cache in readonly mode An error has occurred with shared classes The JVM ends, unless you have Remove the read-only option from your command-line and restart the JVM. JVMSHRC285I Opened shared class persistent cache %1$s read-only Shared classes persistent cache %1$s has been opened for read-only access. This message is produced when -Xshareclasses:verbose is specified. No action is required. JVMSHRC286I Opened shared class cache %1$s read-only Shared classes cache %1$s has been opened for read-only access. This message is produced when -Xshareclasses:verbose is specified. No action is required. JVMSHRC287E Persistent cache cannot be located on a networked file system. Either select "nonpersistent" or a different cachedir. An error has occurred with shared classes The JVM ends, unless you have Use the "nonpersistent" option. JVMSHRC291E Cannot allocate memory for hashtable entry in ROMClassResourceManager An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC292E Cannot enter ROMClassResourceManager hashtable mutex An error has occurred during shared The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service 62 IBM SDK, Java Technology Edition: IBM JVM messages

71 JVMSHRC296I JVMSHRC323E JVMSHRC296I Running with option "nocoremmap" will mean that IBM will be unlikely to assist with any crashes as class data will be missing from system dumps Without CORE_MMAP set to "yes", the system dumps do not contain the required class data. If possible, run with the environment variable CORE_MMAP set to "yes" and remove the "nocoremmap" option. JVMSHRC320E Error recovery: destroying shared memory semaphores. An error has occurred during shared The JVM ends, unless you have JVMSHRC297I To use persistent shared class caches on AIX, environment variable CORE_MMAP must be set to "yes" Without CORE_MMAP set to "yes", the system dumps will not contain the required class data. caches. Set CORE_MMAP or use nonpersistent JVMSHRC298E To run "%s" utility on persistent class cache "%s", use the "persistent" suboption The JVM cannot run the utility on the persistent cache, because the expected type is nonpersistent. Add the persistent suboption. JVMSHRC318E Error recovery: destroying shared memory. An error has occurred during shared The JVM ends, unless you have JVMSHRC319E Error recovery: closing shared memory. An error has occurred during shared The JVM ends, unless you have JVMSHRC321E Error recovery: closing shared memory semaphores. An error has occurred during shared The JVM ends, unless you have JVMSHRC322E Failed initializing semaphores for shared class cache. Warning: your cache may be corrupt. If you experience problems using the shared cache, you may need to destroy and re-create it. An error has occurred during shared The JVM ends, unless you have JVMSHRC323E ERROR: Entering the shared class cache header mutex failed. Warning: your cache may be corrupt. If you experience problems using the shared cache, you may need to destroy and re-create it. An error has occurred during shared The JVM ends, unless you have IBM JVM messages 63

72 JVMSHRC324E JVMSHRC337E JVMSHRC324E ERROR: Exiting the shared class cache header mutex failed. Warning: your cache may be corrupt. If you experience problems using the shared cache, you may need to destroy and re-create it. An error has occurred during shared The JVM ends, unless you have JVMSHRC327E SH_OSCachesysv::acquireWriteLock() call to j9shsem_wait has failed with error %d. semaphore. An error occurred waiting on a The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC328E System V IPC reported the following error '%s' An error occurred during the use of System V IPC functions in the JVM. The JVM ends, unless you have representative if this problem persists. JVMSHRC329E SH_CompositeCacheImpl:: enterreadwriteareamutex failed to acquire the string table mutex (return code %d). An error has prevented updates to the shared class cache. The JVM attempts to continue. representative if this problem persists. JVMSHRC330E SH_CompositeCacheImpl::runExitCode failed to acquire the write area mutex (return code %d). An error has prevented updates to the shared class cache during shutdown. The JVM attempts to continue the shutdown process. representative if this problem persists. JVMSHRC334E Error recovery failed: Destroying shared memory has failed. An error has occurred during shared The JVM ends, unless you have Consult the diagnostic information in the Java documentation. JVMSHRC335E Error recovery failed: Destroying shared semaphore has failed. An error has occurred during shared The JVM ends, unless you have Consult the diagnostic information in the Java documentation. JVMSHRC336E Port layer error code = %1$d This message shows the last portable error code stored in the J9 Port layer, indicating the last error encountered. The JVM ends, unless -Xshareclasses:nonfatal is specified, in which case processing JVMSHRC337E Platform error message: %1$s This message shows the platform specific error code and message related to the last error that was stored in the J9 Port layer. If the message does not indicate an error, there is probably no platform error associated with this port layer error. The JVM ends, unless -Xshareclasses:nonfatal is specified, in which case 64 IBM SDK, Java Technology Edition: IBM JVM messages

73 JVMSHRC338E JVMSHRC404E processing JVMSHRC338E Port layer error code = %1$d This message shows the last portable error code stored in the J9 Port layer, indicating the last error encountered. The JVM failed to clean up a System V IPC resource during error recovery. Consult the diagnostic information in the Java documentation. JVMSHRC339E Platform error message: %1$s This message shows the platform specific error code and message related to the last error that was stored in the J9 Port layer. If the message does not indicate an error, there is probably no platform error associated with this port layer error. The JVM failed to clean up a System V IPC resource during error recovery. Consult the diagnostic information in the Java documentation. JVMSHRC340E Shared Cache CRC check failed. Stored CRC %1$x, calculated CRC %2$x This message shows the CRC values when the cache startup CRC check fails The JVM attempts to re-create the cache before starting. If this process fails, the JVM ends, unless you have -Xshareclasses:nonfatal. JVMSHRC361E Error while attaching to the shared memory during open/create An error has occurred in shared class The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC363E Cannot allocate api for shared classes in shrinit An error has occurred in shared class initialization. The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC364E SH_OSCachesysv::acquireWriteLock() call to j9shsem_wait on semid %d has failed with error %d. semaphore. An error occurred while waiting on a The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC375E The cache name is too long when the user name is included. There are %d bytes left in this buffer, and your user name is %d bytes. The system cannot include the username in the shared class cache name. The JVM ends, unless you have JVMSHRC404E Failed to get a directory for the cache The directory path requested is bigger than the internal buffer space. The JVM ends, unless you have Use a shorter path or cache name. IBM JVM messages 65

74 JVMSHRC405E JVMSHRC442E JVMSHRC405E Failed to create a directory for the cache The directory specified for the shared cache could not be created. The JVM ends, unless you have Make sure that you have the correct file permissions for the controldir or cachedir chosen. JVMSHRC428I Removed older generation of shared class cache "%s" The older generation of the shared class cache was successfully removed. Processing continues. No action is required. JVMSHRC429I Failed to remove older generation of shared class cache "%s" The older generation of the shared class cache cannot be removed. Processing continues. Run with the option -Xshareclasses:verbose enabled to see other messages that might indicate why the cache is not removed. JVMSHRC430I Failed to remove current generation of shared class cache "%s" The current generation of the shared class cache cannot be removed. Processing continues. Other messages might be issued indicating the reason why the cache is not removed. Investigate these messages. JVMSHRC434E Value=%d passed by -Xitsn option is outside of the range of prime number values supported by the VM. Supported range = 0 - %u The value specified for the -Xitsn option is larger than the biggest prime number supported by the JVM. Check the value specified by the -Xitsn option on the command line. The supported range is shown in the error message. JVMSHRC435I -Xitsn%2$u uses %1$u bytes of memory, which is larger than the shared classes cache size of %3$u bytes The Shared Intern Table is part of the shared cache, therefore it cannot be larger than the shared cache. A new Shared Intern Table size is calculated, proportional to the shared cache size. Processing continues. Check the shared cache size. Check the intern string table node count, which is specified by the -Xitsn option. JVMSHRC436E Error acquiring shared class cache file header write lock An error has occurred in shared class The JVM ends, unless you have JVMSHRC437E Error releasing shared class cache file header read lock An error has occurred in shared class The JVM ends, unless you have JVMSHRC442E Shared cache "%s" is corrupt. Corruption code is %d. Corrupt value is 0x%x. No new JVMs will be allowed to connect to the cache. Existing JVMs can continue to function, but cannot update the cache. The shared class cache is corrupt. The JVM attempts to re-create the cache before starting. If this process fails, the JVM ends unless you have -Xshareclasses:nonfatal. Remove the shared class cache and try again. If the situation persists, contact your IBM service 66 IBM SDK, Java Technology Edition: IBM JVM messages

75 JVMSHRC443I JVMSHRC457E JVMSHRC443I Cache CRC is incorrect indicating a corrupt cache. Incorrect cache CRC: 0x%x. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC448E Cache size field in cache header is not valid. Cache size in cache header is: 0x%x. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC444I Read corrupt data for cache entry header 0x%p (invalid item length) An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC449E Padding is non zero. Padding bytes in cache header are: %u. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC445E Size of cache is too small to be useful. Invalid cache size: 0x%x. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC446E Failed to acquire header write lock during cache startup with error code: %d. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC447E Cache header eyecatcher is not valid. Address of eyecatcher string in cache header: 0x%p. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC450E Data length field in cache header is not valid. Data length in cache header is: %u. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC451E Data start field in cache header is not valid. Data start address in cache header is: 0x%p. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC457E Invalid cache name, the cache name "%.*s" contains only whitespace or is empty The specified shared class cache name contains only white space characters, or no characters. The JVM ends, unless you have Change the shared class cache name to IBM JVM messages 67

76 JVMSHRC461E JVMSHRC504E include non-whitespace characters, and start the JVM again. JVMSHRC461E -Xscminjitdata value should not be greater than -Xscmaxjitdata value The value for -Xscminjitdata cannot be larger than -Xscmaxjitdata. Change the value of -Xscminjitdata to be less than or equal to the value of -Xscmaxjitdata. JVMSHRC462I -Xscminjitdata value is greater than -Xscmx value, so it has been set to equal -Xscmx value The value specified for the -Xscminjitdata option cannot be greater than the value for the -Xscmx option. The value for the -Xscminjitdata option is changed and the JVM continues. No action is required. JVMSHRC463I -Xscmaxjitdata value is greater than -Xscmx value, so it has been set to unlimited The value specified for the -Xscmaxjitdata option cannot be greater than the value specified for the -Xscmx option. The value of the -Xscmaxjitdata option is changed automatically and the JVM continues. No action is required. JVMSHRC488E Total of -Xscminaot and -Xscminjitdata values should not be greater than available cache size The total value of the -Xscminaot and -Xscminjitdata options cannot be greater than the available cache size. Change the values of the -Xscminaot and -Xscminjitdata options so that the total of these values does not exceed the available cache size. JVMSHRC500E The debug area is corrupt because free space low address %p, is greater than free space high address %p An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC501E The debug area is corrupt because the 'line number table data' low address %p, is greater than the high address %p An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC502E The debug area is corrupt because the 'local variable table data' low address %p, is greater than the high address %p An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC503E The debug area is corrupt because storing 'line number table' %d bytes, and 'local variable table' %d bytes, will result in a 'line number table data' high address of %p, which will be greater than the new 'local variable table data' low address %p An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC504E Cache data start is null. data start: %p An error has occurred in shared class The cache is marked as corrupt and the JVM continues. 68 IBM SDK, Java Technology Edition: IBM JVM messages

77 JVMSHRC505E JVMSHRC550E JVMSHRC505E The debug area is corrupt because free space high address %p minus the free space low address %p exceeds the debug region size of %lu bytes An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC506E The debug area is corrupt because its size of %lu is larger than the total cache size of %u stored in the cache header An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC508E Acquired a different semaphore than previously used with this cache. old semid=%d, new semid=%d An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC511I Composite cache has bad initialization flag value. The value of ccinitcomplete is %lu The value of the initialization flag for the composite cache is incorrect. The cache is marked as corrupt and the JVM continues. JVMSHRC514E Invalid setting for cachedirperm option. This must be unix style file permission in the range of or (in octal representation). The value specified for the cachedirperm parameter is not in a valid format. Run the command again with a valid cachedirperm value. Use UNIX-style file permissions in octal representation in the range of or JVMSHRC517E Unrecognised sub-option for option printallstats=. Use printallstats=help to see available options. The suboption provided for printallstats= is not recognized. Run printallstats=help to see a list of valid options and try again. JVMSHRC547E Cannot allocate memory for character array in shrinit An error has occurred when parsing shared class command-line options. The JVM ends, unless you have The system might be low on resources. Try again when the system is more lightly loaded. If the situation persists, contact your IBM service JVMSHRC549E -Xshareclasses:checkStringTableReset may fail. String table is not large enough. It needs to be more than to OS page size. Table size = %d, Page size = %d An error has occurred in shared class JVMSHRC550E ROUND_TO_PAGE_SIZE runtime flag is missing. -Xshareclasses:checkStringTableReset requires string table be rounded to page size. An error has occurred in shared class IBM JVM messages 69

78 JVMSHRC551E JVMSHRC590E JVMSHRC551E Cache \"%s\" is marked as full. Failed to allocate block size = %d. The JVM is unable to store the requested data in the cache because the cache is marked as full. JVMSHRC552E Cannot allocate requested block size for cache \"%s\". Available bytes = %d, Requested bytes = %d There is not enough free memory in the shared class cache to store the amount of data requested. JVMSHRC557E Unrecognised sub-option for option printstats=. Use printstats=help to see available options. The suboption provided for printstats= is not recognized. Run printstats=help for a list of valid options and try again. JVMSHRC559E Failed to create a directory \"%s\" for the shared class cache The directory specified for the shared class cache could not be created. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Make sure that you have the right permissions for the controldir or cachedir chosen. JVMSHRC560E Internal cache name is not proper. An error has occurred in shared class The JVM ends, unless you have JVMSHRC561E Failed to initialize the shared classes cache, there is not enough space in the file system. Available free disk space bytes = %lld, requested bytes = %lld. An error has occurred in shared class The JVM ends, unless you have Increase the amount of space available in your file system and try again. JVMSHRC562I Read corrupt data for cache entry header 0x%p (invalid item length of %u bytes) An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC572E Opening a Realtime cache, which is not compatible with this JVM, use the -Xrealtime JVM option to access this cache cache. A standard JVM is accessing a real-time The JVM ends, unless you have To use a real-time JVM, specify the -Xrealtime option. If you do not want to use a real-time JVM, use a different cache name. JVMSHRC590E The "enablebci" sub-option was specified but the existing cache was not created with the "enablebci" sub-option. An error occurred when processing shared class options. The JVM ends, unless you have Remove the enablebci suboption, which is incompatible with this shared classes cache and try again. 70 IBM SDK, Java Technology Edition: IBM JVM messages

79 JVMSHRC594E JVMSHRC614E JVMSHRC594E The -Xshareclasses:cacheRetransformed sub-option is incompatible with a shared cache created with the enablebci sub-option An error occurred when processing shared class options. The JVM ends, unless you have Remove the cacheretransformed suboption, which is incompatible with this shared classes cache and try again. JVMSHRC595E Command-line options \"%s\" and \"%s\" are incompatible The JVM found incompatible suboptions when processing the shared class options. Remove one of the incompatible -Xshareclasses suboptions and try again. JVMSHRC598E The raw class data area is corrupt because its size of %lu is larger than the total cache size of %lu. An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC599E The raw class data area free space is corrupt ('free space start'=%p, 'free space end'=%p, 'free size'=%lu bytes) An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC600E The raw class data area is corrupt because storing %u bytes will exceed the available area free space ('free space start'=%p, 'free space end'=%p). An error has occurred in shared class The cache is marked as corrupt and the JVM continues. JVMSHRC605E The memory size for \"%s\" is too large, or specifies units other than 'K','M', or 'G'. The memory size is too large, or specifies units other than K, M, or G. Correct or remove the incorrect command-line option and try again. JVMSHRC611E The "disablebci" sub-option is specified but the existing cache was created with the "enablebci" sub-option. An error occurred when processing shared class options. The JVM ends, unless you have Remove the disablebci suboption, which is incompatible with this shared classes cache and try again. JVMSHRC613E An error has occurred while opening semaphore. Control file is found to be corrupt. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC614E An error has occurred while opening semaphore. Mismatch in semaphore ID. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service IBM JVM messages 71

80 JVMSHRC615E JVMSHRC622E JVMSHRC615E An error has occurred while opening semaphore. Mismatch in semaphore key. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC619E Semaphore control file is read only. permission. The semaphore control file has only read The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check that the semaphore control file has read/write permissions and try again. If the situation persists, contact your IBM service JVMSHRC616E An error has occurred while opening semaphore. Mismatch in number of semaphores in the semaphore set. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC620E Error opening shared memory region. Control file is found to be corrupt. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC617E An error has occurred while opening semaphore. Semaphore marker not found in the semaphore set. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC618E Semaphore control file is not readable. control file. The JVM cannot read the semaphore The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check that the semaphore control file has read/write permissions and try again. If the situation persists, contact your IBM service JVMSHRC621E Error opening shared memory region. Mismatch in shared memory ID. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC622E Error opening shared memory region. Mismatch in shared memory key. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service 72 IBM SDK, Java Technology Edition: IBM JVM messages

81 JVMSHRC623E JVMSHRC630I JVMSHRC623E Error opening shared memory region. Check for group id failed. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC624E Error opening shared memory region. Check for user id failed. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC625E Error opening shared memory region. Check for shared memory size failed. An error occurred during shared class The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check any messages that follow, which might indicate the problem. For further assistance, contact your IBM service JVMSHRC626I Recreation of shared memory control file is not allowed when retrieving cache stats. This message provides information only. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. No action is required. JVMSHRC627I Recreation of shared memory control file is not allowed when running in read-only mode. This message is for information only. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. No action is required. JVMSHRC628E Shared memory control file is not readable. control file. The JVM cannot read the shared memory The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check that the shared memory control file has read/write permissions and try again. If the situation persists, contact your IBM service JVMSHRC629E Shared memory control file is read only. The shared memory control file has only read permission. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Check that the shared memory control file has read/write permissions and try again. If the situation persists, contact your IBM service JVMSHRC630I Space is full for storing non-aot/non-jit data, such as classes, in shared cache \"%s\". The available space for storing non-aot/non-jit data, such as classes, in the named shared classes cache is full. No further data can be added. The named shared cache is still operational and continues to provide increased performance for loading the classes that are stored. However, classes that are not contained in the cache are always loaded from their source. To gain the full benefit of shared classes, delete and re-create the named cache, specifying a larger shared class cache size with the -Xscmx parameter. IBM JVM messages 73

82 JVMSHRC631I JVMSHRC639E JVMSHRC631I Space reserved for AOT data in shared cache \"%s\" is full. Use -Xscminaot to increase space reserved for AOT data. The available space for storing AOT data in the named shared classes cache is full. No further AOT data can be added. The named shared cache is still operational and continues to provide increased performance for loading the classes that are stored. However, no more AOT compiled methods can be added to the cache. To allow the JVM to store more AOT compiled methods into the shared classes cache, increase the value that is specified by the -Xscminaot option. JVMSHRC632I Space reserved for JIT data in shared cache \"%s\" is full. Use -Xscminjitdata to increase space reserved for JIT data. The available space for storing JIT data in the named shared classes cache is full. No further JIT data can be added. The named shared cache is still operational and continues to provide increased performance for loading the classes that are stored. However, no more JIT-related data can be added to the cache. To allow the JVM to store more JIT-related data into the shared classes cache, increase the value that is specified by the -Xscminjitdata option. JVMSHRC633E The "-XX:+StoreIntermediateClassfile" option was specified but the existing cache was not created with the "-XX:+StoreIntermediateClassfile" option. An error occurred when processing shared class options. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. try again. Remove the incompatible option and JVMSHRC634E The "-XX:- StoreIntermediateClassfile" option was specified but the existing cache was created with the "-XX:+StoreIntermediateClassfile" option. An error occurred when processing shared class options. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Remove the option -XX:-StoreIntermediateClassfile from the command line to use the existing shared classes cache. JVMSHRC637E The -Xshareclasses:cacheRetransformed sub-option is incompatible with an existing BCI enabled shared cache. An error occurred when processing shared class options. The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. and try again. Remove the incompatible suboption JVMSHRC638I Cache creation with the cacheretransformed option forces disablebci mode. When you use the option -Xshareclasses:cacheRetransformed, the shared cache that is created does not support Byte Code Instrumentation (BCI). Using this option is equivalent to setting -Xshareclasses:disableBCI. No action is required. This message is for information only. JVMSHRC639E Only shared cache utility options can be used in combination with -Xmt. Put other shared cache options in the javad.options file. Shared cache runtime options must be specified in the javad.options file. The javad process must be restarted before any shared classes cache options take effect. Replace the incompatible -Xshareclasses option with a -Xshareclasses utility option and try again. 74 IBM SDK, Java Technology Edition: IBM JVM messages

83 JVMSHRC646E JVMSHRC653E JVMSHRC646E The JVM could not check the permissions of the semaphore set associated with the shared cache. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC647E The JVM detected effective user id of the process is the owner but not the creator of semaphore set associated with the shared cache. JVM will not attach to the shared cache to prevent accessing unintended shared cache. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Delete the existing shared classes cache and restart to create a new shared classes cache. JVMSHRC648E The JVM is not configured to access semaphore set associated with existing non-persistent shared class cache. To attach to the non-persistent shared class cache, use 'groupaccess' sub-option. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Modify the existing -Xshareclasses option to add a groupaccess sub option and start again. JVMSHRC649E The JVM does not permit access to the shared cache's semaphore set created and owned by another user not in its group. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Specify a different cache name or directory to avoid a conflict with the existing shared classes cache. This cache was created by another user that is not in the same group. JVMSHRC650E The JVM could not check the permissions of the shared memory associated with the shared cache. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. JVMSHRC651E The JVM detected effective user id of the process is the owner but not the creator of shared memory associated with the shared cache. JVM will not attach to the shared cache to prevent accessing unintended shared cache. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Delete the existing shared classes cache and restart to create a new shared classes cache. JVMSHRC652E The JVM is not configured to access shared memory associated with existing non-persistent shared class cache. To attach to the non-persistent shared class cache, use 'groupaccess' sub-option. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Modify the existing -Xshareclasses option to add the groupaccess sub option and try again. JVMSHRC653E The JVM is not configured to access shared memory associated with existing non-persistent shared class cache. To attach to the non-persistent shared class cache, use 'groupaccess' and 'readonly' sub-option. IBM JVM messages 75

84 JVMSHRC654E JVMSHRC661E An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Modify the existing -Xshareclasses option to add the groupaccess and readonly sub options and try again. JVMSHRC654E The JVM does not permit access to the shared cache's shared memory region created and owned by another user not in its group. An error occurred during shared classes The JVM ends, unless you specified the nonfatal option with -Xshareclasses:nonfatal, in which case the JVM continues without using shared classes. Specify a different cache name or directory to avoid a conflict with an existing shared classes cache. This cache was created by another user that is not in the same group. JVMSHRC656E The JVM is not configured to access shared cache file. To attach to the shared class cache, use 'groupaccess' suboption. An error occurred within shared classes The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM Modify the existing -Xshareclasses: option to add the groupaccess suboption, then restart the Java VM. JVMSHRC657E The JVM does not permit access to the shared cache file because the JVM process's user ID and group ID are different from the shared cache file owner's user ID and group ID, and the JVM process's user ID does not belong to the shared cache file owner's group. An error occurred within shared classes The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM Specify a different cache name or directory to avoid conflict with an existing shared cache that is created by another user who is in a different group. JVMSHRC658E The JVM could not check the permissions of the shared cache file. An error occurred within shared classes The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM JVMSHRC659E An error has occurred while opening shared memory An error occurred in shared class Further messages might follow, providing more detail. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM representative, unless subsequent messages indicate otherwise. JVMSHRC660E The JVM failed to associate semaphore set id=%d with the shared class cache. This message displays the ID of the semaphore set that the Java VM failed to associate with the shared class cache due to an error that is indicated in previous messages. The Java VM continues. Use the ipcrm command to remove the semaphore set that is indicated in the error message, if it still exists and is not in use. JVMSHRC661E The JVM failed to associate shared memory id=%d with the shared class cache. This message displays the ID of the shared memory that the Java VM failed to associate with the shared class cache due to an error that is indicated in previous messages. The Java VM continues. Use the ipcrm command to remove the shared memory that is indicated in the error message, if it still exists and is not in use. 76 IBM SDK, Java Technology Edition: IBM JVM messages

85 JVMSHRC662E JVMSHRC668E JVMSHRC662E Error recovery: destroyed semaphore set associated with shared class cache. An error occurred in shared class processing, and as part of error recovery the Java VM destroyed the semaphore set that was associated with the shared class cache. The Java VM detected an error during shared class processing and destroyed the semaphore set in an attempt to recover. JVMSHRC663I Error recovery: destroyed semaphore set with id=%d associated with shared class cache. An error occurred in shared class processing, and as part of error recovery the Java VM destroyed the semaphore set that as associated with the shared class cache. The Java VM detected an error during shared class processing and destroyed the semaphore set in an attempt to recover. JVMSHRC664E Error recovery failed: Failed to destroy the semaphore set with semid=%d associated with shared class cache. Only creator or owner or user with administrative privileges can destroy the semaphore set. An error occurred in shared class The Java virtual machine's attempt to destroy the semaphore set as part of error recovery failed because the operating system allows only the creator, owner, or a user with administrative privileges to destroy the semaphore set. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM No action is required. JVMSHRC665E Error recovery failed: Failed to destroy the semaphore set with semid=%d associated with shared class cache. An error occurred in shared class The Java virtual machine's attempt to destroy the semaphore set as part of error recovery failed. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM JVMSHRC666E Error recovery: destroyed shared memory associated with shared class cache. An error occurred in shared class processing and as part of error recovery the Java VM destroyed the shared memory that was associated with the shared class cache. The Java VM detected an error during shared class processing and destroyed the shared memory in an attempt to recover. JVMSHRC667I Error recovery: destroyed shared memory with id=%d associated with shared class cache. An error occurred in shared class processing and as part of error recovery the Java VM destroyed the shared memory that was associated with the shared class cache. The Java VM detected an error during shared class processing and destroyed the shared memory in an attempt to recover. JVMSHRC668E Error recovery failed: Failed to destroy the shared memory with shmid=%d associated with shared class cache. Only creator or owner or user with administrative privileges can destroy the shared memory. An error occurred in shared class The Java virtual machine's attempt to destroy the shared memory as part of error recovery failed because the operating system allows only the creator, owner, or a user with administrative privileges to destroy the shared memory. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM No action is required. IBM JVM messages 77

86 JVMSHRC669E JVMSHRC677E JVMSHRC669E Error recovery failed: Failed to destroy the shared memory with shmid=%d associated with shared class cache. An error occurred in shared class The Java virtual machine's attempt to destroy the shared memory as part of error recovery failed. The Java VM ends, unless you specified the nonfatal option by using the -Xshareclasses:nonfatal parameter, in which case the Java VM JVMSHRC670I Error recovery: attempting to use shared cache in readonly mode if the shared memory region exists, in response to "-Xshareclasses:nonfatal" option. An error occurred in shared class The presence of the -Xshareclasses:nonfatal option causes the Java VM to attempt to use the shared cache in read-only mode. The Java VM attempts to attach to the shared memory segment of the shared class cache in read-only mode if it exists. No action is required. JVMSHRC671E User is not allowed to destroy the semaphore set with semid=%d. Only creator or owner or user with administrative privileges can destroy the semaphore set. The operating system allows only the creator, owner, or a user with administrative privileges to destroy the semaphore set. The Java VM continues. No action is required. JVMSHRC672E Failed to destroy semaphore set associated with shared class cache. An error occurred while destroying the semaphore set that is associated with the shared class cache. The Java VM continues. JVMSHRC673E Failed to destroy semaphore set with semid=%d associated with shared class cache. An error occurred while destroying the semaphore set that is associated with the shared class cache. The Java VM continues. JVMSHRC674E User is not allowed to destroy the shared memory with shmid=%d. Only creator or owner or user with administrative privileges can destroy the shared memory. The operating system allows only the creator, owner, or a user with administrative privileges to destroy the shared memory. The Java VM continues. No action is required. JVMSHRC675E Failed to destroy shared memory associated with shared class cache. An error occurred while destroying the shared memory that is associated with the shared class cache. The Java VM continues. JVMSHRC676E Failed to destroy shared memory with shmid=%d associated with shared class cache. An error occurred while destroying the shared memory that is associated with the shared class cache. The Java VM continues. JVMSHRC677E Port layer error code = %1$d This message shows the last portable error code that is stored in the J9 Port layer. This message indicates the last error that was encountered. The Java VM failed to clean up a System V IPC resource. 78 IBM SDK, Java Technology Edition: IBM JVM messages

87 JVMSHRC678E JVMSHRC684E JVMSHRC678E Platform error message: %1$s This message shows the platform-specific error code and message that is related to the last error that was stored in the J9 Port layer. The Java VM failed to clean up a System V IPC resource. JVMSHRC679E Error recovery failure: Failed to remove the semaphore set control file %s associated with shared class cache. An error occurred during shared class The Java virtual machine's attempt to remove the control file as part of error recovery failed. The Java VM continues. If the Java VM fails to start, remove the control files manually. JVMSHRC680E Error recovery failure: Failed to remove the semaphore set control file %s associated with shared class cache. An error occurred during shared class The Java virtual machine's attempt to remove the control file as part of error recovery failed. The Java VM continues. If the Java VM fails to start, remove the control files manually. JVMSHRC681E System limit for maximum number of semaphores or the system wide maximum number of semaphores has been reached. The Java VM failed to create a new semaphore set for the shared class cache because the system limit was reached. If you specified the -Xshareclasses:nonfatal option, the Java VM tries to use an existing shared class cache in read-only mode. If the cache does not exist, the Java VM continues without the shared class cache. If you did not specify the -Xshareclasses:nonfatal option, the Java VM ends. Contact your system administrator to increase the system limit on semaphore resources, or clean up any unused semaphore sets in the system then restart the Java VM. JVMSHRC682E System limit for maximum number of shared memory regions or system-wide limit on memory allocated to shared memory regions has been reached. The Java VM failed to create a new shared memory region for the shared class cache because the system limit was reached. If you specified the -Xshareclasses:nonfatal option the Java VM continues without the shared class cache, otherwise the Java VM ends. Contact your system administrator to increase the system limit on shared memory resources, or clean up any unused shared memory regions in the system then restart the Java VM. JVMSHRC683E System limit on the total number of open files has been reached. The Java VM failed to create a new control file for the shared class cache because the system limit was reached. If you specified the -Xshareclasses:nonfatal option and this error occurred when creating a semaphore control file, the Java VM tries to use an existing shared class cache in read-only mode. If the cache does not exist, the Java VM continues without the shared class cache. If this error occurred when creating a shared memory control file, the Java VM continues without the shared class cache. If you did not specify the -Xshareclasses:nonfatal option, the Java VM ends. Contact your system administrator to increase the system limit on maximum open files, or close any unused files then restart the Java VM. JVMSHRC684E An error has occurred while opening semaphore. Control file could not be locked. An error has occurred in shared class Further messages might follow, providing more detail. If you specified the -Xshareclasses:nonfatal option, the Java VM tries to use an existing shared class cache in read-only mode. If the cache does not exist, the Java VM continues without the shared class cache. If you did not specify the -Xshareclasses:nonfatal option, the Java VM ends. representative, unless subsequent messages indicate otherwise. IBM JVM messages 79

88 JVMSHRC685E JVMSHRC702I JVMSHRC685E An error has occurred while opening shared memory. Control file could not be locked. An error occurred in shared class Further messages might follow, providing more detail. If you specified the -Xshareclasses:nonfatal option, the Java VM continues without the shared class cache, otherwise the Java VM ends. representative, unless subsequent messages indicate otherwise. JVMSHRC686I Failed to startup shared class cache. Continue without using it as -Xshareclasses:nonfatal is specified An error occurred during shared class cache start. You specified the -Xshareclasses:nonfatal option, so the Java VM will continue without using the shared class cache. The Java VM continues without the shared class cache. representative to understand why the shared class cache could not be started. Previous error messages might indicate the reason. JVMSHRC687E A new shared class cache cannot be created when running with -Xshareclasses:readonly option An error occurred during shared class cache start. The Java VM cannot create a new shared class cache when the -Xshareclasses:readonly option is specified. The Java VM ends unless you specified the -Xshareclasses:nonfatal option, in which case the Java VM continues without the shared class cache. Remove the readonly suboption from the -Xshareclasses option, then restart the Java VM. The readonly suboption is useful only if the shared class cache already exists. JVMSHRC697E Failed to get a directory for the shared cache The directory path requested is bigger than the internal buffer space. The JVM fails to complete the operation of creating a snapshot of the non-persistent shared cache. name. Use a shorter directory path or cache JVMSHRC698I Non-persistent shared cache \"%s\" has been restored successfully from the snapshot The non-persistent shared cache is successfully restored from the snapshot. No action is required. This message is only for information. JVMSHRC699E Failed to restore the non-persistent shared cache \"%s\" from the snapshot An error occurred when the JVM attempted to restore the non-persistent cache. The JVM fails to complete the operation of restoring a non-persistent shared cache from the snapshot. Other messages might indicate the reason why the cache cannot be restored from the snapshot. JVMSHRC700I Snapshot of non-persistent shared cache \"%s\" has been created The JVM successfully created the snapshot of an existing non-persistent shared cache. No action is required. This message is only for information. JVMSHRC701E Failed to create a snapshot of non-persistent shared cache \"%s\" An error occurred when the JVM attempted to create a snapshot of a non-persistent shared cache. The JVM fails to complete the operation of creating the snapshot of a non-persistent shared cache. Other messages might indicate the reason why the snapshot failed to be created. JVMSHRC702I Failed to get a directory for the shared cache snapshot The directory path that is requested is bigger than the internal buffer space. The JVM fails to complete the required operation on the shared cache snapshot. name. Use a shorter directory path or cache 80 IBM SDK, Java Technology Edition: IBM JVM messages

89 JVMSHRC703E JVMSHRC713E JVMSHRC703E Failed to open the shared cache snapshot file \"%s\" An error occurs when the JVM attempts to open the shared cache snapshot file. The JVM fails to complete the required operation on the shared cache snapshot file. Previous error messages might indicate the reason for this failure. If this is not the case, contact your IBM service JVMSHRC704E Port layer error code = %1$d This message shows the last portable error code that was encountered. The JVM fails to complete the required operation on the shared cache snapshot. A later message might provide more information about this error code and the action that can be taken. If this is not the case, contact your IBM service JVMSHRC705E Platform error message: %1$s This message shows the platform-specific error code and message that relates to the last portable error code that was encountered. This code might indicate a success message, in which case there is probably no associated platform error. The JVM fails to complete the required operation on the shared cache snapshot file. If an appropriate action cannot be determined from the error message, contact your IBM service JVMSHRC706E Failed to acquire file lock on the shared cache snapshot file An error occurs when the JVM attempts to acquire a file lock on the shared cache snapshot file. The JVM fails to complete the required operation on the shared cache snapshot file. Previous error messages might indicate the reason for the failure. If not, contact your IBM service JVMSHRC707E Failed to acquire the mutex of cache \"%s\" An error occurs when the JVM attempts to acquire a cache mutex. The JVM fails to complete the operation of creating the snapshot of a non-persistent shared cache. Verify that the system has enough native resources for the JVM. If the problem persists, contact your IBM service JVMSHRC708E Failed to truncate the existing non-persistent shared cache snapshot file \"%s\" An error occurs when the JVM attempts to truncate the non-persistent shared cache snapshot file. operation. The JVM fails to complete the Previous error messages might indicate the reason. JVMSHRC710E Failed to write into the non-persistent shared cache snapshot file \"%s\" An error occurs when the JVM attempts to write to a non-persistent shared cache snapshot file. operation. The JVM fails to complete the Previous error messages might indicate the reason for the failure, for example, the disk might be full. If this is not the case, contact your IBM service JVMSHRC711E Failed to reposition the offset of the file descriptor in the non-persistent shared cache snapshot file \"%s\" An error occurs when the JVM attempts to reposition the offset of the file descriptor in the non-persistent shared cache snapshot file. The JVM fails to complete the operation of creating the snapshot of a non-persistent shared cache. Previous error messages might indicate the reason for the failure. If this is not the case, contact your IBM service JVMSHRC713E Failed to get the length of the shared cache snapshot file \"%s\" An error occurs when the JVM attempts to obtain the length of the snapshot file. The JVM fails to complete the operation of destroying a shared cache snapshot. Previous error messages might indicate the reason for the failure. If this is not the case, contact your IBM service IBM JVM messages 81

90 JVMSHRC714I JVMSHRC723E JVMSHRC714I No shared cache snapshots available There are no snapshots present in the cachedir that can be processed by the command requested. Processing continues. No action is required. JVMSHRC715I Removed older generation of shared cache snapshot \"%s\" The JVM successfully removes an older generation of the indicated shared cache snapshot. JVM processing continues. No action is required. This message is only for information. JVMSHRC716I Failed to remove older generation of shared cache snapshot \"%s\" The JVM is unable to remove the older generation of the indicated shared cache snapshot. JVM processing continues. Previous error messages might indicate the reason for the failure. If this is not the case, contact your IBM service JVMSHRC717I Failed to remove current generation of shared cache snapshot \"%s\" The JVM is unable to remove the current generation of the indicated shared cache snapshot. The JVM fails to remove the snapshot of a shared cache. Previous error messages might indicate the reason for this failure. If this is not the case, contact your IBM service JVMSHRC718E Shared cache snapshot does not exist The JVM attempts to remove a shared cache snapshot that does not exist. No action is required. JVMSHRC719I Shared cache snapshot \"%s\" is destroyed The named shared cache snapshot is removed, as requested. No action is required. This message is only for information. JVMSHRC720I Recreation of shared memory control file is not allowed when creating a snapshot of the cache The JVM cannot create a snapshot of the shared cache because a valid shared cache does not exist. No action is required. JVMSHRC721E The JVM is not configured to access the non-persistent shared cache snapshot file \"%s\". To open the file, use 'groupaccess' sub-option. An error occurred during shared classes The JVM fails to restore a non-persistent shared cache from the snapshot. Modify your -Xshareclasses: option to add the groupaccess suboption and try again. The snapshot might have been created by another user in the same group as the current user. JVMSHRC722E The JVM does not permit access to the shared cache snapshot file \"%s\" because the JVM process's user ID and group ID are different from the shared cache snapshot file owner's user ID and group ID, and the JVM process's user ID does not belong to the shared cache snapshot file owner's group. An error occurred during shared classes The JVM fails to restore a non-persistent shared cache from the snapshot. Specify a different cache name or directory. This action avoids a conflict with an existing shared cache snapshot that was created by another user that is not in the same group. JVMSHRC723E The JVM could not check the permissions of the shared cache snapshot file \"%s\" An error occurred during shared classes The JVM fails to restore a non-persistent shared cache from the snapshot. 82 IBM SDK, Java Technology Edition: IBM JVM messages

91 JVMSHRC724E JVMSHRC732I JVMSHRC724E Shared cache snapshot file \"%s\" does not exist The shared cache snapshot file is not found on the disk. The JVM fails to restore a shared cache from the snapshot. JVMSHRC725E The length of the non-persistent shared cache snapshot file \"%s\" is invalid. The length of the file is %lld bytes. A valid snapshot file is at least %d bytes and at most %lld bytes. The length of the file is not valid The JVM fails to restore a non-persistent shared cache from the snapshot. Check that the file is a valid shared cache snapshot file. JVMSHRC726E Non-persistent shared cache \"%s\" already exists. It cannot be restored from the snapshot. Only a new non-persistent shared cache can be restored from a snapshot. The JVM fails to restore a non-persistent shared cache from the snapshot. Check that the non-persistent cache does not exist before restoring the cache from the snapshot. JVMSHRC727E An error has occurred in creating the new non-persistent shared cache The JVM cannot start the new cache. The JVM fails to restore a non-persistent shared cache from the snapshot. Verify that the system has enough native resources for the JVM. If the problem persists, contact your IBM service JVMSHRC728E Failed to read the non-persistent shared cache snapshot file \"%s\" An error occurs when reading the non-persistent shared cache snapshot file. The JVM fails to restore a non-persistent shared cache from the snapshot. Previous error messages might indicate the reason for the error. If this is not the case, contact your IBM service JVMSHRC729E The snapshot was created by a different JVM build and doesn't match the running JVM An error occurs when the JVM attempts to start the restored cache. The build ID in the snapshot is different from the ID of the current JVM. The JVM fails to restore a non-persistent shared cache from the snapshot. Use a JVM that matches the snapshot, or destroy the snapshot. JVMSHRC730I The JVM has created shared cache with '-Xshareclasses:restrictClasspaths' option. Subsequent JVM invocations will not be able to store classpaths into the shared cache When the -Xshareclasses:restrictClasspaths option is used, subsequent JVMs cannot store class paths into the shared cache unless they are running with the -Xshareclasses:allowClasspaths option. No action is required. This message is only for information. JVMSHRC731I The JVM has ignored '-Xshareclasses:restrictClasspaths' option as the existing shared cache was created without '-Xshareclasses:restrictClasspaths' option -Xshareclasses:restrictClasspaths is applicable only when the JVM is initializing a new shared cache. For this option to be effective you must remove the existing shared cache and restart the JVM. JVMSHRC732I The JVM can store classpaths into the shared cache created with '-Xshareclasses:restrictClasspaths' option The JVM can store class paths into the shared cache because the -Xshareclasses:allowClasspaths option is also specified. No action is required. This message is only for information. IBM JVM messages 83

92 JVMSHRC733I JVMSHRC751E JVMSHRC733I The JVM cannot store classpaths into the shared cache, since the cache was created with the '-Xshareclasses:restrictClasspaths' option The JVM attaches to an existing shared cache created with the -Xshareclasses:restrictClasspaths option. No action is required. This message is only for information. JVMSHRC735I Use a %d-bit JVM to perform the requested operation on the %d-bit shared cache \"%s\" as the %d-bit JVM cannot verify that the shared memory was created by the JVM The JVM cannot verify the size of the shared cache. The requested operation is not carried out to avoid accidental access to shared memory of another application. You must use a JVM that has the same address mode as the shared cache to carry out the requested operation. JVMSHRC743E Invalid method specification(s) for option \"%s\" The method specification provided was not recognized. and try again. Specify a valid method specification JVMSHRC744I Invalidated the %d AOT method(s) Successfully found the AOT method(s) and performed the required operation. No action is required. This message is for information only. JVMSHRC745I Revalidated the %d AOT method(s) Successfully found the AOT method and performed the required operation. No action is required. This message is for information only. JVMSHRC746I Found the %d AOT method(s) Successfully found the AOT method and performed the required operation. No action is required. This message is for information only. JVMSHRC747E Failed to invalidate the AOT method(s) An error occurred while performing the requested operation on the AOT method. Previous messages might indicate the reason for the error. JVMSHRC748E Failed to revalidate the AOT method(s) An error occurred while attempting the requested operation on the AOT method. Previous messages might indicate the reason for this error. JVMSHRC749E Failed to find the AOT method(s) An error occurred while attempting the requested operation on the AOT method. Previous messages might indicate the reason for this error. JVMSHRC750I No AOT methods match the method specification(s) There are no AOT methods in the cache that match the method specification. No action is required. JVMSHRC751E Failed to parse the method specifications. No more than %d method specifications are allowed. specified. Too many method specifications are Reduce the number of method specifications and try again. The maximum limit is IBM SDK, Java Technology Edition: IBM JVM messages

93 JVMSHRC752E JVMSHRC782I JVMSHRC752E Failed to parse the method specification(s) An error occurred while parsing the method specification. Correct the format of the method specification and try again. JVMSHRC753E Failed to get the cache write mutex An error occurred when acquiring the write mutex of the cache. Verify that the system has enough native resources for the JVM to work properly. If the problem persists, contact your IBM service JVMSHRC754I Recreation of shared memory control file is not allowed. The required operation cannot complete because a valid shared cache does not exist. None required. JVMSHRC762E Error getting stats of the shared class cache file when verifying its group access permission. An error has occurred during shared classes The JVM ends, unless you have JVMSHRC765I Memory page protection on runtime data, string read-write data and partially filled pages is successfully enabled Memory pages of the cache that contain runtime data, string read/write data, and partially filled pages, are protected. If any protected page of the cache is accessed illegally, the Java VM crashes. No action required. JVMSHRC769I Memory page protection on runtime data and partially filled pages is successfully enabled Memory pages of the cache that contain runtime data and partially filled pages are protected. If any protected page of the cache is accessed illegally, the Java VM crashes. No action required. JVMSHRC773I Memory page protection on runtime data and string read-write data is successfully enabled Memory pages of the cache that contain runtime data and string read/write data are protected. If any protected page of the cache is accessed illegally, the Java VM crashes. No action required. JVMSHRC777I Memory page protection on runtime data is successfully enabled Memory pages of the cache that contain runtime data are protected. If any protected page of the cache is accessed illegally, the JVM will crash. No action required. JVMSHRC781I The JVM has enabled shared cache partial page protection as the existing shared cache was created with partial page protection enabled. The Java VM is attached to an existing shared cache, which was created with partial protection enabled. Any Java VM attaching to an existing shared cache enables partial page protection, irrespective of command line options. The Java VM protects both partially filled pages and full pages in the shared class cache. Remove the existing shared cache and restart the Java VM. This action makes the -Xshareclasses:mprotect=nopartialpages or -Xshareclasses:mprotect=none option effective. JVMSHRC782I The JVM has disabled protecting partially filled pages. If -Xshareclasses:mprotect=onfind is specified, it is also ignored. The Java VM is attached to an existing shared cache that was created with the -Xshareclasses:mprotect=nopartialpages option. Any JVM attaching to this type of cache disables partial page protection, irrespective of command line options. IBM JVM messages 85

94 JVMSHRC816I JVMSHRC843I The Java VM protects only full pages in the shared class cache. Partially filled pages are not protected. Remove the existing shared cache and restart the Java VM. By default, the Java VM protects partially filled pages in the shared cache after the startup phase. JVMSHRC816I The JVM has enabled shared cache partial page protection on startup as the existing shared cache was created with partial page protection enabled during startup. The Java VM is attached to an existing shared cache that was created with partial protection enabled during startup. Any Java VM attaching to this type of cache enables partial page protection during startup, irrespective of command line options. The Java VM starts protecting partially filled pages during startup. No action required. JVMSHRC817I The JVM has not enabled protecting shared cache partially filled pages on startup. The Java VM is attached to an existing shared cache that was not created with the -Xshareclasses:mprotectOnStartup option. Any Java VM attaching to this type of cache enables partial page protection after the startup phase. The Java VM protects partially filled pages when the startup phase is complete. Remove the existing shared cache and restart the Java VM with the -Xshareclasses:mprotectOnStartup option. JVMSHRC818I Compressed references persistent shared cache \"%1$s\" has been destroyed. Use option -Xnocompressedrefs if you want to destroy a non-compressed references cache. The compressed references cache '1$' is removed as requested. The Java VM stops when the processing is complete. No action required. JVMSHRC823I Non-compressed references persistent shared cache \"%1$s\" has been destroyed. Use option -Xcompressedrefs if you want to destroy a compressed references cache. The non-compressed references cache '1$' is destroyed as requested. The Java VM stops when the processing is complete. No action required. JVMSHRC828I Compressed references shared cache \"%s\" is destroyed. Use option -Xnocompressedrefs if you want to destroy a non-compressed references cache. The compressed references shared class cache is removed as requested. A Java VM is not created and a failure message is issued. However, this failure message is a normal response when you request a shared class cache to be removed. No action required. JVMSHRC833I Non-compressed references shared cache \"%s\" is destroyed. Use option -Xcompressedrefs if you want to destroy a compressed references cache. The non-compressed references shared class cache is removed as requested. A Java VM is not created and a failure message is issued. However, this failure message is a normal response when you request a shared class cache to be removed. No action required. JVMSHRC838I Compressed references shared cache snapshot \"%s\" is destroyed. Use option -Xnocompressedrefs if you want to destroy a non-compressed references cache snapshot. The compressed references shared cache snapshot is removed as requested. The Java VM continues. No action required. JVMSHRC843I Non-compressed references shared cache snapshot \"%s\" is destroyed. Use option -Xcompressedrefs if you want to destroy a compressed references cache snapshot. The non-compressed references shared cache snapshot is removed as requested. The Java VM continues. No action required. 86 IBM SDK, Java Technology Edition: IBM JVM messages

95 JVMTRCE000E JVMTRCE004W TRCE messages Trace engine messages. This section details messages that are generated by the IBM trace engine: v JVMTRCE000E v JVMTRCE001E v JVMTRCE002E v JVMTRCE003E v JVMTRCE004W v JVMTRCE005W on page 88 v JVMTRCE006W on page 88 v JVMTRCE007W on page 88 v JVMTRCE008W on page 88 v JVMTRCE009W on page 88 v JVMTRCE010W on page 88 v JVMTRCE011W on page 88 v JVMTRCE012W on page 88 v JVMTRCE013I on page 88 v JVMTRCE014E on page 88 v JVMTRCE015E on page 89 v JVMTRCE016E on page 89 v JVMTRCE017E on page 89 v JVMTRCE018E on page 89 v JVMTRCE019E on page 89 v JVMTRCE020W on page 89 JVMTRCE000E Trace option unrecognized: -Xtrace:%s An option used with the -Xtrace parameter is not known. Use -Xtrace:help to find the correct syntax for the -Xtrace option and try again. JVMTRCE001E Error processing trace option: -Xtrace:%s An option used with the -Xtrace parameter could not be processed correctly due to a syntax error. Use -Xtrace:help to find the correct syntax for the -Xtrace option and try again. JVMTRCE002E Error processing trace option: -Xtrace:%s=%s An option used with the -Xtrace parameter could not be processed correctly due to a problem with the option or the arguments used. Use -Xtrace:help to find the correct syntax for the -Xtrace option and try again. JVMTRCE003E Error processing trace option, detail: %s An option used with the -Xtrace parameter could not be processed correctly due to the problem described in the detail string. Use -Xtrace:help to find the correct syntax for the -Xtrace option and try again. JVMTRCE004W Error opening trace file: %s opened. The specified trace file could not be The JVM continues but trace data is not written to this file. If you need to collect the trace data, IBM JVM messages 87

96 JVMTRCE005W JVMTRCE014E restart the JVM specifying a trace file that can be opened. restart the JVM specifying a trace file that can be opened. JVMTRCE005W Error writing header to trace file: %s written to. The specified trace file could not be The JVM continues but trace data is not written to this file. If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. JVMTRCE006W Error writing %d bytes to trace file: %s rc: %d written to. The specified trace file could not be The JVM continues but trace data is not written to this file. If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. JVMTRCE007W Error opening next trace file generation: %s The specified trace file could not be opened when the JVM attempted to open the next trace file in a cycle of generational trace files. The JVM continues but trace data is not written to this file. If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. JVMTRCE008W Error performing seek in tracefile: %s The JVM could not find an expected location in the specified trace file. The JVM continues but trace data is not written to this file. If you need to collect the trace data, restart the JVM specifying a trace file that can be opened. JVMTRCE009W Error writing to snap file The JVM could not write trace data to a snap file while the JVM was running. The JVM continues but trace data is not written to this file. If you need to collect the trace data, JVMTRCE010W Native memory allocation failure, falling back to nodynamic trace settings. The JVM could not allocate space for another trace buffer. The JVM continues but trace reuses existing buffers. Trace points that are not written to disk before a new buffer is required might be lost. No action is required. However, to reduce the amount of trace points produced, change the trace options. JVMTRCE011W Module not configured for trace: %s The JVM could not configure trace for the specified module, typically due to a native out of memory situation. The JVM continues but there is no trace data generated for this module. You might need to obtain additional information by running with -Xtrace:debug=<n>. JVMTRCE012W Unable to open trace point counter file %s, counters redirected to stderr. The JVM could not open the specified file for the trace point counts at shutdown. The JVM writes the counter information to stderr at shutdown. If you need to collect the trace data, restart the JVM specifying a trace file that can be written to. JVMTRCE013I Writing trace count info to %s The JVM is writing trace counter information to the specified location at shutdown. The JVM writes the counter information to that location at shutdown. No action required. This message is for information only. JVMTRCE014E Trace engine initialization failed, trace not enabled The JVM cannot start the trace engine. You might need to obtain additional information by running with -Xtrace:debug=<n>. 88 IBM SDK, Java Technology Edition: IBM JVM messages

97 JVMTRCE015E JVMVERB000I JVMTRCE015E Error registering trace write subscriber The JVM cannot start the trace subscriber thread that writes trace buffers to disk. The JVM continues but trace data is not written to disk. You might need to obtain additional information by running with -Xtrace:debug=<n>. JVMTRCE016E Storage for RasGlobalStorage not available, trace not enabled The JVM could not be initialized. JVMTRCE017E Unable to allocate RAS thread local storage key The JVM could not initialize. JVMTRCE018E Unable to allocate UTE thread local storage key The JVM could not initialize. JVMTRCE019E Trace engine failed to initialize properly, RC = %d The JVM could not initialize. JVMTRCE020W Timeout occurred during trace engine termination A timeout occurred during JVM shutdown while the trace engine is waiting for trace subscriber threads to finish. The JVM ends without waiting for trace subscriber threads to finish. VERB messages Verbose messages. This section details verbose messages that are generated by the IBM JVM: v JVMVERB000I v JVMVERB002I on page 90 v JVMVERB003E on page 90 v JVMVERB004E on page 90 v JVMVERB005E on page 90 v JVMVERB018W on page 90 v JVMVERB019W on page 90 v JVMVERB020W on page 90 v JVMVERB021W on page 90 v JVMVERB022W on page 90 v JVMVERB023W on page 90 v JVMVERB024W on page 90 v JVMVERB025W on page 91 v JVMVERB026W on page 91 v JVMVERB027I on page 91 v JVMVERB028I on page 91 JVMVERB000I Verbose stack: "%2$.*1$s" used %3$zd/%4$zd bytes on Java/C stacks Indicates how much stack is used on each stack for a thread when you specify the -verbose:stack parameter. IBM JVM messages 89

98 JVMVERB002I JVMVERB024W None. This message is an information message. No action is required. JVMVERB002I Verbose stack: maximum stack use was %1$zd/%2$zd bytes on Java/C stacks Indicates the largest stack usage for each stack for all threads when you specify the -verbose:stack parameter. None. This message is an information message. No action is required. JVMVERB003E Error: -Xverbosegclog number of files must be greater than 0 Either you specified the -Xverbosegclog parameter with a value of 0 for the number of files, or the parameter could not be parsed. Use a number greater than 0 for the number of files. JVMVERB004E Error: -Xverbosegclog number of cycles must be greater than 0 Either you specified the -Xverbosegclog parameter with a value of 0 for the number of cycles, or the parameter could not be parsed. Use a value greater than 0 for the number of cycles. JVMVERB005E Error: -Xverbosegclog missing filename You used the -Xverbosegclog parameter without specifying a file name. Specify a valid file name when using the -Xverbosegclog parameter. JVMVERB018W Invalid classpath entry: %s (file I/O failed) The JVM could not open the specified.zip file. The file might not exist or the file permissions might not allow access by the JVM. The JVM either ignores the issue or throws a java/io/ioexception exception. Check that the specified.zip file exists and has appropriate permissions. JVMVERB019W Invalid classpath entry: %s (file read failed) The JVM could not read part of the specified.zip file. The file might be corrupt or truncated. The JVM either ignores the issue or throws a java/io/ioexception exception. If the.zip file is corrupt or truncated, replace it with a valid copy. JVMVERB020W Invalid classpath entry: %s (file corrupt) The specified.zip file is corrupt. The JVM either ignores the issue or throws a java/io/ioexception exception. valid copy. Replace the corrupt.zip file with a JVMVERB021W Invalid classpath entry: %s (unsupported file type) unsupported The specified.zip file type is The JVM either ignores the issue or throws a java/io/ioexception exception. Replace the specified.zip file with a supported.zip file type. JVMVERB022W Invalid classpath entry: %s (unknown file type) The specified.zip file type is unknown. The JVM either ignores the issue or throws a java/io/ioexception exception. Replace the specified.zip file with a.zip file of a supported type. JVMVERB023W Invalid classpath entry: %s (unknown error) An unexpected error occurred while reading the specified.zip file. The JVM either ignores the issue or throws a java/io/ioexception exception. If the problem persists, contact your IBM Service JVMVERB024W Invalid classpath entry: %s (jxe missing rom.classes) A rom.classes entry could not be found in the specified JXE file. The JVM either ignores the issue or 90 IBM SDK, Java Technology Edition: IBM JVM messages

99 JVMVERB025W JVMVMUT006E throws a java/io/ioexception exception. Replace the JXE file with a valid copy that contains a rom.classes entry. JVMVERB025W Invalid classpath entry: %s (jxe corrupt image header) header. The specified JXE file had a corrupt The JVM either ignores the issue or throws a java/io/ioexception exception. valid copy. Replace the corrupt JXE file with a JVMVERB026W Invalid classpath entry: %s (opposite endian jxe not supported) The Endian nature of the specified JXE file was not correct for this platform. The JVM either ignores the issue or throws a java/io/ioexception exception. Replace the JXE file with one of the correct endianness. JVMVERB027I Verbose stack: Running thread "%2$.*1$s" is using %3$zd/%4$zd bytes on Java/C stacks Indicates how much memory was used for the Java and C stacks for a thread. This message is issued when you specify the -verbose:stack parameter. This message is for information only. No action is required. JVMVERB028I Verbose stack: Unable to print the stack info for currently running threads The JVM was unable to obtain a lock for the currently running threads. This message is for information only. No action is required. VMUT messages JVM utility messages. This section details messages that are generated by IBM JVM utilities: v JVMVMUT003E v JVMVMUT004W v JVMVMUT005W v JVMVMUT006E v JVMVMUT007E on page 92 v JVMVMUT008E on page 92 v JVMVMUT009E on page 92 v JVMVMUT010W on page 92 v JVMVMUT011E on page 92 v JVMVMUT013E on page 92 JVMVMUT003E Options file not found Correct the command-line option. You used the -Xoptionsfile parameter to specify an options file, but the file could not be opened. file. The JVM ignores the specified options Correct the command-line parameter. JVMVMUT005W Option too large: '%s' The specified option is larger than the maximum permitted value. The JVM ignores the option. Correct the command-line option. JVMVMUT004W Malformed option: '%s' The specified option could not be parsed. The JVM ignores the option. JVMVMUT006E Malformed option %s found in -Xoptionsfile You used the -Xoptionsfile parameter IBM JVM messages 91

100 JVMVMUT007E JVMZIPS001W to specify a file. The file contains a token within quotation marks, but the closing quotation mark is missing. Correct the command-line option. Add the missing quotation mark to the file that is specified by the -Xoptionsfile parameter. JVMVMUT007E Malformed value for JAVA_TOOL_OPTIONS The JAVA_TOOL_OPTIONS environment variable contains a token within quotation marks, but the closing quotation mark is missing. Correct the JAVA_TOOL_OPTIONS environment variable. JVMVMUT008E Malformed value for IBM_JAVA_OPTIONS The IBM_JAVA_OPTIONS environment variable contains a token within quotation marks, but the closing quotation mark is missing. Correct the IBM_JAVA_OPTIONS environment variable. JVMVMUT009E Malformed value for -Xservice The -Xservice command-line option contains a token within quotation marks, but the closing quotation mark is missing. JVMVMUT010W Malformed option value, option "%1$s%3$.*2$s" contains trailing characters "%4$s" which have been ignored parsed. The specified option value could not be The JVM ignores the option value. Correct the command-line option. JVMVMUT011E Could not allocate memory for command line option array The JVM tried to allocate memory to copy command-line options, but failed. Check the available memory in your process or system. Increase the memory that is available to start the JVM, then try again. JVMVMUT013E Options file %s invalid An options file specified with the -Xoptionsfile option cannot be opened or is too large. option file. Check the size and contents of the ZIPS messages Compressed file messages. This section details messages that are generated by the IBM JVM: v JVMZIPS000W v JVMZIPS001W JVMZIPS000W Unable to open %1$s (%2$s) JVM, then start the JVM again. The JVM attempted to load the J9 zlib library, but the operation failed. Restore the file from a copy of the JVM, then start the JVM again. JVMZIPS001W Unable to open %s (Missing export) The JVM attempted to find an exported symbol in the J9 zlib library, but the operation failed. Restore the file from a copy of the 92 IBM SDK, Java Technology Edition: IBM JVM messages

101 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 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 , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , 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 Copyright IBM Corp. 2011,

102 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 US 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: 94 IBM SDK, Java Technology Edition: IBM JVM messages

103 (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 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. 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. Notices 95

104 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 ; (ii) IBM s Online Privacy Statement at (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 96 IBM SDK, Java Technology Edition: IBM JVM messages

105 Notices 97

106 IBM Printed in USA