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