ibm sdk, java technology edition: ibm vm messagesattempting to pr oduce a dump. system action: the...

IBM SDK, Java Technology EditionVersion 1

IBM VM messages

IBM

NoteBefore you use this information and the product it supports, read the information in “Notices” on page 77.

Copyright information

This edition of the IBM VM messages guide applies to the IBM SDK and Runtime Environment, Java TechnologyEdition, for all versions, releases, modifications, and fix packs, unless otherwise indicated.

Portions © Copyright 1997, 2018, Oracle and/or its affiliates.

© Copyright IBM Corporation 2011, 2018.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . v

IBM VM messages . . . . . . . . . . 1CDRT messages . . . . . . . . . . . . . 1DUMP messages . . . . . . . . . . . . . 2EXEL messages . . . . . . . . . . . . . 6EXEX messages . . . . . . . . . . . . . 7J9CL messages . . . . . . . . . . . . . . 8J9GC messages . . . . . . . . . . . . . 8J9RI messages . . . . . . . . . . . . . 12J9TI messages . . . . . . . . . . . . . 14J9VM messages . . . . . . . . . . . . . 17JITM messages . . . . . . . . . . . . . 24JNCK messages . . . . . . . . . . . . . 26

MECK messages. . . . . . . . . . . . . 27OFFC messages . . . . . . . . . . . . . 28PORT messages . . . . . . . . . . . . . 30SHRC messages . . . . . . . . . . . . . 33TRCE messages . . . . . . . . . . . . . 71VERB messages . . . . . . . . . . . . . 73VMUT messages. . . . . . . . . . . . . 75ZIPS messages . . . . . . . . . . . . . 75

Notices . . . . . . . . . . . . . . 77Trademarks . . . . . . . . . . . . . . 79Terms and conditions for product documentation. . 79IBM Online Privacy Statement . . . . . . . . 80

© Copyright IBM Corp. 2011, 2018 iii

iv IBM SDK, Java Technology Edition: IBM VM messages

Preface

This guide lists messages that are generated by the IBM® Java™ Virtual Machine(JVM).

© Copyright IBM Corp. 2011, 2018 v

vi IBM SDK, Java Technology Edition: IBM VM messages

IBM VM messages

The Java virtual machine (VM) that is used by the IBM Software Developers Kit(SDK) is the IBM J9 virtual machine. Messages are issued by the IBM VM inresponse to certain conditions.

These IBM messages, error codes, and exit codes apply to multiple versions ofthe JVM.

There are three main types of message:

InformationInformation messages provide information about JVM processing. Forexample, a dump information message is typically issued when a dumpagent requests a Java dump.

WarningWarning messages are issued by the JVM to indicate conditions that mightneed user intervention.

Error Error messages are issued by the JVM when normal processing cannotproceed, because of unexpected conditions.

IBM VM 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 VM messages can help you with problem determination. Refer to diagnosticinformation for more detailed information about diagnosing problems with theIBM JVM.

CDRT messagesCodert module messages.

JVMCDRT000E Unable to locate JIT stack map -aborting VM

Explanation: JIT metadata could not be found whentraversing Java stacks.

System action: The JVM ends.

User response: Contact your IBM servicerepresentative.

JVMCDRT001E Method: %2$.*1$s.%4$.*3$s%6$.*5$s(%7$p)




JVMCDRT002E Failing PC: %1$p (offset %2$p),metaData = %3$p



© Copyright IBM Corp. 2011, 2018 1


DUMP messagesDump agent messages.

JVMDUMP000E Dump option unrecognized:-Xdump:%s

Explanation: An option used with the -Xdumpparameter is unknown.


User response: Use -Xdump:help to find the correctsyntax for the -Xdump options.

JVMDUMP001E Dump event unrecognized: ...%s

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


User response: Use -Xdump:events to find thesupported set of event names.

JVMDUMP002W Token unrecognized: %%%1$c

Explanation: An unidentified token was found in thedump label.


User response: Use -Xdump:tokens to find thesupported set of tokens.

JVMDUMP003E Dump agent unrecognized: %s

Explanation: An unsupported dump type has beenrequested.


User response: Use -Xdump:help to find the supportedset of dump types.

JVMDUMP004E Missing file name

Explanation: The dump file name could not be found.

System action: The dump cannot be written.

User response: Provide a valid filename for the dump.

JVMDUMP005E Missing external tool

Explanation: The executable file for the tool could notbe found.

System action: The tool cannot run.

User response: Provide a valid path and filename forthe executable file.

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

Explanation: A dump event has occurred and is beinghandled.

System action: The JVM attempts to process the event.

User response: No response is required.

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

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

System action: The JVM attempts to write the dump.A second message is generated when the dump iscomplete.

User response: Review the dump and takeappropriate action.

JVMDUMP009I %s dump not available

Explanation: The specified dump type is not currentlyavailable. For example, a JVM trace snap dump hasbeen requested, but JVM trace is not enabled.

System action: The JVM does not write the dump.

User response: This message is only for information.

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

Explanation: The dump was written to the specifiedlocation.

System action: The JVM continues.

User response: To understand how to interpret a Javadump file, refer to diagnostic information.

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

Explanation: A tool dump process has been created.

System action: The JVM runs the executable processspecified for the tool dump. Any parameters are passedto the process.

User response: Refer to the documentation for the toolcreating the dump process.

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

Explanation: The JVM detected an error while

JVMDUMP000E • JVMDUMP012E

2 IBM SDK, Java Technology Edition: IBM VM messages

attempting to produce a dump.

System action: The JVM continues, but the dumpmight not be usable.

User response: Refer to diagnostic information orcontact your local IBM service representative.

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

Explanation: A dump event occurred and has beenhandled.


User response: Refer to other messages issued by theJVM for the location of the dump file, or for otheractions required.

JVMDUMP014E VM Action unrecognized: ...%s

Explanation: A specified dump request action was notunderstood by the JVM.

System action: The JVM produces help informationand ends.

User response: Use -Xdump:request to check that yourrequest is valid.

JVMDUMP015I Aborting: Cannot open or read (%s)

Explanation: The JVM cannot open a dump file inread mode.

System action: INTERNAL USE ONLY

User response: INTERNAL USE ONLY

JVMDUMP016I Aborting: Cannot create file (%s)

Explanation: An attempt by the JVM to open a newfile has failed.



JVMDUMP017I Aborting: Cannot compress file (%s)

Explanation: The JVM cannot compress a file.



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

Explanation: A dump has been requested on an eventtype that is not supported.



JVMDUMP019I JVM requesting %s dump

Explanation: A dump file of the type specified hasbeen requested.

System action: The JVM attempts to produce a dumpof the specified type.

User response: Wait for a message indicating that thedump is complete.

JVMDUMP020I %s dump has been written

Explanation: A dump file of the type specified hasbeen written.


User response: To understand how to interpret thedump file, refer to Java diagnostic information.

JVMDUMP022W The requested heap compactionhas not been performed becauseexclusive access was not requested orcould not be obtained.

Explanation: The garbage collector could not runbecause the gc thread did not have exclusive access tothe heap.

System action: The dump file is not produced.

User response: Modify the -Xdump option to requestexclusive access. See the Java diagnostic information forvalid dump request types.

JVMDUMP023W The requested heap preparationhas not been performed becauseexclusive access was not requested orcould not be obtained.

Explanation: The dump thread must lock the heap toprevent changes while the dump is taken. Either noattempt was made to obtain the lock or the lock couldnot be obtained.

System action: The JVM does not produce thespecified dump.

User response: Modify the -Xdump option to requestexclusive access. See the Java diagnostic information forvalid dump request types.

JVMDUMP024W Multiple heapdumps wererequested but %%id is missing from filelabel:. Dumps will overwrite

Explanation: The JVM replaces the %%id insertionpoint with a unique number. Because %%id is missingthe replacement cannot take place, causing a potentialfile name clash and file overwrite.

System action: The JVM informs the user andproduces dumps as requested.

JVMDUMP013I • JVMDUMP024W

IBM VM messages 3

User response: 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

Explanation: An IEATDUMP was requested but couldnot be produced.

System action: The JVM will output the message onthe operator console.

User response: Check the response code provided inthe error using the Diagnostics Guide or the z/OS®

V1R7.0 MVS™ Authorized Assembler ServicesReference, 36.1.10 Return and Reason Codes.

JVMDUMP026 IEATDUMP Name exceedingmaximum allowed length. Default nameused.

Explanation: The file label exceeded the maximumlength for file names on z/OS.

System action: The dump file is not produced.

User response: Refer to Java diagnostic informationfor information about producing dumps on z/OS.

JVMDUMP027W The requested heapdump has notbeen produced because anothercomponent is holding the VM exclusivelock.

Explanation: The exclusive VM lock must be held toproduce a usable heapdump. Although the VMexclusive lock was requested by the user, the VM couldnot obtain the lock in a reasonable time. This behavioravoids risking a deadlock.

System action: The VM does not produce aheapdump.

User response: Wait for 1 minute and try taking theheapdump again when the VM exclusive lock might befree.

JVMDUMP028W The VM exclusive lock could notbe acquired before taking the systemdump.

Explanation: Although the VM exclusive lock wasrequested by the user, the VM could not obtain the lockin a reasonable time before taking the system dump.This behavior avoids risking a deadlock.

System action: The VM produces a system dumpwithout taking the VM exclusive lock. The dump mightshow an inconsistent view of the VM data structuresand heap.

User response: Wait for 1 minute and try taking thesystem dump again when the VM exclusive lock mightbe free.

JVMDUMP029W The request for prepwalk orcompact before taking a system dumpwill be ignored because the VMexclusive lock was not requested.

Explanation: The user requested the prepwalk orcompact options before taking a system dump, but didnot request the VM exclusive lock. These actionsrequire the exclusive VM lock.

System action: The system dump is taken withoutrunning prepwalk or compact.

User response: Modify the -Xdump:system parameterto include the exclusive request option. For example:

-Xdump:system:events=user,request=exclusive+compact+prepwalk

JVMDUMP030W Cannot write dump to file %s: %s

Explanation: The JVM was unable to write a dump tothe specified file. There might be multiple causes,including insufficient file system permissions orspecifying a file path that does not exist.

System action: The JVM uses a default file name. Thename and location of the file are indicated by themessages produced when the dump is written.

User response: Correct the problem with the specifiedfile path or change the target dump file with the file=option.

JVMDUMP031W The requested heapdump has notbeen produced because the VMexclusive lock was not requested. Addrequest=exclusive+prepwalk+compact toyour -Xdump:heap: command line option.

Explanation: A heapdump dump agent wasconfigured using the -Xdump option or JVMTI withoutrequesting that the exclusive VM lock.

System action: The JVM does not take the heapdumpbecause the dump might be corrupted without the VMexclusive lock in place.

User response: Change the -Xdump:heap: option toinclude the request=exclusive option. For example:

-Xdump:heap:events=user,request=exclusive

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

Explanation: The JVM writes a dump because anevent, such as an exception, was triggered.

System action: The JVM attempts to write the dump.A second message is produced when the dump iscomplete.


JVMDMP025I • JVMDUMP032I


JVMDUMP033I JVM requested %1$s dump inresponse to an event

Explanation: The JVM writes a dump because anevent, such as an exception, has been triggered.



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

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



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

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



JVMDUMP036I Invalid or missing -Xdump filter

Explanation: A valid -Xdump filter must be supplied.

System action: The dump agent is not loaded.

User response: Modify the dump option to include avalid filter.

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

Explanation: An error has occurred in a JVM dumpagent. An operating system call used by the agent hasfailed.


User response: Check preceding JVM messages. TheJVMDUMP007I message includes the command stringsupplied for tool dumps. Check that the commandstring is correct.

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

Explanation: Snap dumps are not produced when atrace output file is in use.


User response: Use the trace file specified in themessage.

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

Explanation: A dump event is being handled.

System action: The JVM generates dumps asconfigured for the event by the -Xdump option.

User response: No action is required.

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

Explanation: The dump is written using the specifieddata set name template.


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

JVMDUMP041I Incorrect use of -Xdump msg_filter

Explanation: The suboption msg_filter is applicableonly to events throw, systhrow, catch, and uncaught.

System action: The dump agent is not loaded.

User response: Modify the dump option to apply themsg_filter suboption to applicable events.

JVMDUMP042W Abort signal received whilerunning on Java stack. The JVM dumpagents could not be run.

Explanation: The JVM abort signal handler was calledon a thread that is running on a Java stack. The JVMdump agents are not run to avoid further problems.

System action: The JVM ends. The abort signal ispassed on to the operating system.

User response: No specific action is required. Look forother messages that are produced to assist you withproblem determination. Refer to operating systemdocumentation for information about obtaining dumpson abort signals.

JVMDUMP033I • JVMDUMP042W

IBM VM messages 5

JVMDUMP043E %s not supported on this platform

Explanation: The option that is specified is notsupported on the current platform.


User response: Remove the option and try again.

JVMDUMP044E Invalid or reserved valid value for%s

Explanation: The value for the option is out of theallowed range or is reserved for other purposes.


User response: Select a different value for the optionand try again.

EXEL messagesEXE library messages.

JVMEXEL058E Internal VM error: Out of memory

Explanation: There is not enough virtual memory tosatisfy a memory allocation request.


User response: Contact your IBM Servicerepresentative.

JVMEXEL059E Internal VM error: Failed to findclass java/lang/String

Explanation: The java/lang/String class is not foundin the class path.



JVMEXEL060E Internal VM error: Failed to createbyte array for class name %s

Explanation: Byte array creation failed.



JVMEXEL061E Internal VM error: Failed to createjava/lang/String for class name %s

Explanation: Creation of java/lang/String failed.



JVMEXEL062E Internal VM error: Out of memoryconverting string to UTF characters forclass name %s

Explanation: The amount of available memory is toolow to perform the conversion.



JVMEXEL063E Class %s does not implement main()

Explanation: The main() method is not found.


User response: Ensure that the target class implementsthe main() method.

JVMEXEL064E The method main must be declaredpublic, static and void.

Explanation: The main() method should always bepublic, static, and void.


User response: Ensure that the main() method isdeclared correctly.

JVMEXEL065E Internal VM error: Failed to createargument array

Explanation: An internal JVM error occurred.



JVMEXEL066E Internal VM error: Failed to createbyte array for argument %s




JVMEXEL067E Internal VM error: Failed to createjava/lang/String for argument %s



JVMDUMP043E • JVMEXEL067E



JVMEXEL068E Internal VM error: Failed to set arrayelement for %s




JVMEXEL074E Unable to redirect console to:%1$s:%2$d

Explanation: Failed to establish a socket connection tothe target remote console.

System action: The JVM console output is notredirected to the target console.

User response: Ensure that the remote console isaccessible.

JVMEXEL083E Could not open file: %s

Explanation: The target file cannot be accessed.

System action: The JVM console output is notredirected to the target file.

User response: Ensure that the target file is accessible.

JVMEXEL084W Unable to make a backup copy offile: %s

Explanation: The JVM failed to back up the file.

System action: The JVM continues without backing upthe file.

User response: Ensure that the target file has thecorrect access permission.

JVMEXEL085W WARNING: The command lineargument "%s" has been deprecated.WARNING: Use "-jxe <path>" instead.

Explanation: The specified command-line argument isno longer valid.

System action: The JVM ignores the command-lineargument and continues to run.

User response: Replace the command-line argumentas suggested in the message text.

EXEX messagesJVM EXE messages

JVMEXEX010E %s requires a parameter

Explanation: The specified command-line optionrequires a parameter.


User response: Add the required parameter to theJVM command-line option.

JVMEXEX012E -jar option is not available for thisclass library

Explanation: This JVM does not support the -jarcommand-line option.


User response: Remove the -jar command-line optionor use a different JVM.

JVMEXEX013E Internal VM error: Failed to createJava VM

Explanation: The Java virtual machine could not becreated.


User response: Inspect previous JVM messages for theerror details.

JVMEXEX014I Run %s -help for usage

Explanation: You used an invalid command-lineoption.


User response: Run the JVM with the -helpcommand-line option.

JVMEXEX015E VM startup error: Out of memory

Explanation: The JVM ran out of memory during thestartup sequence.



JVMEXEX016E Invalid jxespace parameters.

Explanation: The parameters supplied to the-jxespace option were not valid.


User response: Use different parameters for the-jxespace option.

JVMEXEX017E Error mapping jxe in flash

JVMEXEL068E • JVMEXEX017E

IBM VM messages 7

Explanation: The JVM failed to map the memoryspace specified by the -jxespace option.


User response: Use different parameters for the-jxespace option.

JVMEXEX023E Could not initialize JXE utilities.

Explanation: The JVM failed to initialize the JXEutilities library. Some of the JVM files might be corrupt.


User response: Reinstall the JVM from a package thatyou know to be valid.

JVMEXEX024E JXE %s did not contain a startupclass.

Explanation: The specified JXE file did not contain astartup class.


User response: Recompile the JXE with a startup class.

J9CL messagesIBM virtual machine Class library messages.

JVMJ9CL000E Incompatible class library

Explanation: The class library .jar file is notcompatible with the class library native code.

System action: The JVM fails to start.

User response: Ensure that the vm.jar file has thesame version as the JVM.

JVMJ9CL001I Try running with -jcl:%s

Explanation: The class library .jar file is notcompatible with the class library native code or theJVM.


User response: Ensure that the class library nativecode and the JVM are compatible with the specifiedclass library .jar file.

JVMJ9CL002I Classes are from a non-J9 library, or anincorrectly reduced JXE

Explanation: The class library .jar file is notcompatible with this virtual machine.


User response: Ensure that the class library iscompatible with the JVM.

JVMJ9CL003E Incompatible class library version:JCL %1$x, VM %2$x

Explanation: The class library is not from the samerelease as the JVM.


User response: Ensure that the JVM and the classlibraries are from the same release.

JVMJ9CL004E Incompatible class library version:expected JCL v%1$i, found v%2$i




JVMJ9CL005E Incompatible class library version:requires VM v%1$i, found v%2$i




JVMJ9CL031W Could not register dbgwrapper.dll asbootstrap library. Error code = %zu

Explanation: The file dbgwrapper.dll could not beloaded.

System action: The JVM attempts to start.


JVMJ9CL033W Could not register %s as bootstraplibrary. Error code = %zu

Explanation: The file indicated by the message couldnot be loaded.

System action: The JVM attempts to start.


J9GC messagesGarbage collector messages.

JVMEXEX023E • JVMJ9CL033W


JVMJ9GC017E %1$s too small, must be at least%2$zu %3$sbytes

Explanation: The value for the specified option issmaller than the minimum permitted value.


User response: Use a larger value for the specifiedoption.

JVMJ9GC018E %1$s too small for %2$s

Explanation: The value for the specified option issmaller than the minimum permitted value.


User response: Adjust your garbage collector options.

JVMJ9GC019E %1$s too large for %2$s

Explanation: The value for the specified option islarger than the maximum permitted value.


User response: Adjust your garbage collector options.

JVMJ9GC020E %s too large for heap

Explanation: The value for the specified option islarger than the maximum permitted value.


User response: Adjust the garbage collector options.

JVMJ9GC021E %1$s must equal %2$s

Explanation: If both of these options are specifiedtogether, the values must be the same.


User response: Update the garbage collector options.

JVMJ9GC022E Sum of %1$s and %2$s too large for%3$s

Explanation: The sum of the values specified for theseoptions is larger than the maximum permitted value.



JVMJ9GC023E Sum of %1$s and %2$s must equal%3$s

Explanation: The sum of the values specified for theseoptions is not equal to the third option.



JVMJ9GC024E Sum of %1$s and %2$s too large forheap

Explanation: The sum of the values specified for theseoptions is larger than the maximum permitted value.



JVMJ9GC027E Malformed option: '%s'

Explanation: The option could not be parsed.


User response: Check the garbage collector optionsand correct any errors before trying again.

JVMJ9GC028E Option too large: '%s'

Explanation: The value specified for this option islarger than the maximum permitted value.



JVMJ9GC029E Option error: '%s'

Explanation: This option is not valid.



JVMJ9GC030E %1$s value of %2$.2f must be at least%3$s less than %4$s value of %5$.2f

Explanation: The values specified for these options aretoo close.



JVMJ9GC031E %1$s and %2$s cannot both bespecified

Explanation: You cannot specify both of these optionstogether.


User response: Remove one of the options and tryagain.

JVMJ9GC032E System configuration does notsupport option '%s'

Explanation: The specified option is not supported bythe current hardware or operating systemconfiguration.


JVMJ9GC017E • JVMJ9GC032E

IBM VM messages 9

User response: Remove the option or adjust yourhardware or operating system configuration.

JVMJ9GC033E %1$s value must be between %2$.2fand %3$.2f (inclusive)

Explanation: The value specified for this option is notwithin the permitted range.



JVMJ9GC034E %1$s value must be between %2$zuand %3$zu (inclusive)

Explanation: The value specified for this option is notwithin the permitted range.



JVMJ9GC035E %s must be followed by a number

Explanation: The option specified must be directlyfollowed by a numeric value.


User response: Adjust the garbage collector options.For example, instead of "-Xmx 100m", use "-Xmx100m".

JVMJ9GC036E %1$s value must be above %2$zu

Explanation: The value specified for the option is toosmall.


User response: Use a larger value for the garbagecollector option and try again.

JVMJ9GC038E %s value specified is too large

Explanation: The value specified for the option is toolarge.


User response: Use a smaller value for this garbagecollector option and try again.

JVMJ9GC039E %1$s is deprecated; use %2$s instead

Explanation: The option is deprecated and no longersupported.


User response: Replace the deprecated option and tryagain.

JVMJ9GC040E Unknown option: %s

Explanation: The option is not recognized.



JVMJ9GC041E Unknown fvtest type: %s

Explanation: The option is not recognized .



JVMJ9GC042E Sum of %1$s and %2$s too small for%3$s

Explanation: The sum of the values specified for theoptions is smaller than the minimum permitted value.



JVMJ9GC054E Large page size %1$zu%2$s is not asupported page size; using %3$zu%4$sinstead

Explanation: The large page size specified is notsupported by the operating system. A further messageis issued detailing the supported page sizes.

System action: The JVM uses the default large pagesize instead of the size you specified.

User response: If the default large page size is notappropriate, update the garbage collector options witha supported page size.

JVMJ9GC057E %1$s must be no greater than %2$s

Explanation: The first option cannot be used becausethe value specified must not be greater than the valueof the second option.



JVMJ9GC059E -Xgcpolicy:metronome is not allowedwithout -Xrealtime

Explanation: The metronome garbage collection policyrequires the -Xrealtime option, but this option was notspecified.





JVMJ9GC062E %s value must be a power of two

Explanation: The value of the specified option mustbe a power of 2, for example: 2, 4, 8, 16, and so on.



JVMJ9GC063E Unable to open file '%s' for writing

Explanation: The specified file could not be openedfor writing.

System action: A log file is not produced.

User response: Check the permissions on the filesystem or specify a location and file name that youhave write access to.

JVMJ9GC069E Failed to initialize Finalize thread

Explanation: The finalize thread could not be created.


User response: Check that the system has enoughnative memory to run the JVM.

JVMJ9GC070E Failed to startup the GarbageCollector

Explanation: The Garbage Collector failed to start.


User response: Check that the system has enoughnative memory to run the JVM.

JVMJ9GC071E Value for '%s' is not correct

Explanation: The value that is specified for the optionis not correct.


User response: Correct the option and try again.

JVMJ9GC072I Large page size %1$zu%2$s is not asupported page size; using %3$zu%4$s%5$s instead

Explanation: The specified page size is not supportedby the operating system. A suitable page size is usedinstead.

System action: The JVM is started with a differentpage size.

User response: Adjust the -Xlp option to specify apage size that is supported by the operating system.

JVMJ9GC073I Large page size %1$zu%2$s %3$s isnot a supported page size; using%4$zu%5$s instead

Explanation: The specified large page size is notsupported by the operating system. A suitable pagesize is used instead.

System action: The JVM starts using a different pagesize.


JVMJ9GC074I Large page size %1$zu%2$s %3$s isnot a supported page size; using%4$zu%5$s %6$s instead




JVMJ9GC075E An error occurred in parsing '-Xlp'option

Explanation: An error occurred when parsing the -Xlpoption.


User response: Correct the -Xlp option and try again.

JVMJ9GC076E System configuration does notsupport requested %1$zu%2$s largepage size

Explanation: The large page size that is specified isnot supported by the operating system.



JVMJ9GC077E System configuration does notsupport requested %1$zu%2$s %3$slarge page size

Explanation: The large page size that is specified isnot supported by the operating system.




IBM VM messages 11

JVMJ9GC078E '%1$s' is not specified as the firstparameter in '%2$s' option

Explanation: A parameter is missing, or theparameters are not in the correct order.


User response: Correct the -Xlp parameters and tryagain.

JVMJ9GC079E '%1$s' option is not complete, mustspecify '%2$s' parameter.

Explanation: The option is missing one or moreparameters.


User response: Specify all the required parameter forthe -Xlp option and try again.

JVMJ9GC080E System configuration does notsupport parameter '%.*s' in option '-Xlp'

Explanation: The parameter that is used with the -Xlpoption is not recognized.


User response: Remove or correct the parameter andtry again.

JVMJ9GC081I Extra comma characters are discoveredin '-Xlp' option - ignored

Explanation: The -Xlp option contains commacharacters that are not needed.

System action: The JVM ignores the extra characters.

User response: Remove the extra commas from the-Xlp option.

JVMJ9GC082I Requested for %1$s page size%2$zu%3$s%4$s is not a supported pagesize; using %5$zu%6$s%7$s instead



User response: Adjust the -Xlp or -Xgc options tospecify page size that is supported by the operatingsystem.

JVMJ9GC084I OS clock resolution claims to notsupport the requested target pause time.Overriding due to command line option-Xgc:overrideHiresTimerCheck

Explanation: The operating system returned a clockresolution that is larger than requested. However, theJVM continues to start because the option-Xgc:overrideHiresTimerCheck is requested.

System action: The JVM starts, but garbage collectionpause time management remains subject to operatingsystem performance, which might not provide adequatetimer resolution.

User response: Use this option with caution, and onlywhen you are unable to use a supported operatingsystem.

JVMJ9GC088I Requested objectheap page size%1$zu%2$s could not be satisfied; using%3$zu%4$s instead

Explanation: The requested object heap page size issupported by the operating system, but is not currentlyavailable.

System action: The JVM starts with a different objectheap page size, instead of the specified size.


JVMJ9GC089W The -Xgc:preferredHeapBase optionis not supported on z/OS.

Explanation: The JVM was started with the-Xgc:preferredHeapBase option, which has no effect onz/OS.

System action: The JVM ignores the-Xgc:preferredHeapBase option.

User response: For a list of supported options, refer tothe IBM SDK documentation.

J9RI messagesJVMRI interface messages.

JVMJ9RI000E jvmri->CreateThread cannot allocatethread arguments memory

Explanation: The JVM could not allocate the memoryrequired to process a JVMRI CreateThread call.

System action: The thread is not created. Error codeJNI_ERR is returned.

User response: Investigate process memory usage andtry again.

JVMJ9GC078E • JVMJ9RI000E


JVMJ9RI002E jvmri->DumpRegister called withNULL callback, function not registered.

Explanation: The JVM could not process a JVMRIDumpRegister call because the supplied callbackfunction parameter was null.

System action: A callback function is not registered.Error code JNI_EINVAL is returned.

User response: Correct the JVMRI DumpRegister callby providing a callback function parameter.

JVMJ9RI003E Can't allocate dump agent injvmri->DumpRegister, function notregistered.

Explanation: The JVM could not allocate the memoryrequired to process a JVMRI DumpRegister call.

System action: A callback function is not registered.Error code JNI_ERR is returned.


JVMJ9RI005E jvmri->GetComponentDataAreacomponent %s does not have dataAreaunder this vm.

Explanation: The JVMRI GetComponentDataArea callis not supported by this JVM.

System action: Error code JNI_ERR is returned.

User response: Remove the JVMRIGetComponentDataArea call from the JVMRI agentcode.

JVMJ9RI006E jvmri->GetRasInfo called with NULLRasInfo structure.

Explanation: The JVM could not process a JVMRIGetRasInfo call because the supplied info_ptrparameter was null.

System action: Error code JNI_EINVAL is returned.

User response: Correct the JVMRI GetRasInfo call byproviding a valid pointer as the info_ptr parameter.

JVMJ9RI007E jvmri->GetRasInfo unable to allocatememory.

Explanation: The JVM could not allocate the memoryrequired to process a JVMRI GetRasInfo call.

System action: Error code JNI_ENOMEM is returned.


JVMJ9RI010E jvmri->GetRasInfo unable to allocatememory.

Explanation: The JVM could not allocate the memoryrequired to process a JVMRI GetRasInfo call.

System action: None. Error code JNI_ENOMEM isreturned.


JVMJ9RI011E RasInfo structure has unsupportedtype field.

Explanation: The RasInfo structure that was suppliedas a parameter to a JVMRI GetRasInfo call had arequest type that is not valid.

System action: None. Error code JNI_EINVAL isreturned.

User response: Correct the request type in thesupplied RasInfo structure and try again.

JVMJ9RI012E jvmri->ReleaseRasInfo called withNULL RasInfo structure.

Explanation: The JVM could not process a JVMRIReleaseRasInfo call because the supplied info_ptrparameter was null.


User response: Correct the JVMRI ReleaseRasInfo callby providing a valid pointer as the info_ptr parameter.

JVMJ9RI013E jvmri->ReleaseRasInfo: structure hasunsupported type field.

Explanation: The RasInfo structure that was suppliedas a parameter to a JVMRI ReleaseRasInfo call had arequest type that is not valid.


User response: Correct the request type in thesupplied RasInfo structure and try again.

JVMJ9RI016E jvmri->SetOutOfMemoryHook calledwith NULL callback, function notregistered.

Explanation: The JVM could not process a JVMRISetOutOfMemoryHook call because the suppliedcallback function parameter was null.

System action: A callback function is not registered.Error code JNI_EINVAL is returned.

User response: Correct the JVMRISetOutOfMemoryHook call by providing a callbackfunction parameter.

JVMJ9RI002E • JVMJ9RI016E

IBM VM messages 13

JVMJ9RI017E Can't allocate dump agent injvmri->SetOutOfMemoryHook, functionnot registered.

Explanation: The JVM could not allocate the memoryrequired to process a JVMRI SetOutOfMemoryHookcall.

System action: A callback function is not registered.Error code JNI_ERR is returned.


JVMJ9RI018I jvmri->NotifySignal raising signal %d.

Explanation: The JVM is about to raise a signal asrequested by a JVMRI NotifySignal call.

System action: The JVM raises the requested signal.

User response: This message is an informationmessage. No action is required.

JVMJ9RI020E jvmri->CreateThread unable to allocateprivate monitor

Explanation: A call to the JVMRI CreateThreadfunction failed because the JVM was unable to allocatea monitor.

System action: The thread is not created. Error codeJNI_ERR is returned.


JVMJ9RI021E jvmri->RunDumpRoutine notsupported.

Explanation: The JVMRI RunDumpRoutine call is notsupported by this JVM.

System action: None. Error code JNI_ERR is returned.

User response: Remove the JVMRI RunDumpRoutinecall from the JVMRI agent code.

JVMJ9RI022E initialise JVMRI unable to allocatejvmri dump monitor

Explanation: The JVM failed to initialize the JVMRIinterface because the JVM was unable to allocate amonitor.



JVMJ9RI023E jvmri->TraceRegister,jvmri->TraceDeregister andTraceListener no longer supported, usenew versions inJVMRAS_VERSION_1_5

Explanation: The JVMRI TraceRegister andTraceDeregister calls are not supported by this JVM.

System action: The trace listener is not registered orunregistered. Error code JNI_ERR is returned.

User response: Change the JVMRI agent code to usethe JVMRI TraceRegister50 and TraceDeregister50 callsinstead.

J9TI messagesJVMTI interface messages.

JVMJ9RI017E • JVMJ9RI023E


JVMJ9TI000E Out of memory attempting to loadagent library %s

Explanation: The system ran out of native memory.

System action: The JVM fails to load the agent library,then ends.

User response: Increase the amount of available nativememory.

JVMJ9TI001E Agent library %1$s could not beopened (%2$s)

Explanation: The agent shared library could not befound or opened.


User response: Verify the existence of the agent sharedlibrary, and check that the file read permissions allowaccess.

JVMJ9TI002E Agent_OnLoad not found in library%s

Explanation: The specified agent does not follow theJVMTI specification.


User response: Add an Agent_OnLoad function to theagent library.

JVMJ9TI003E Agent_OnLoad failed for library %s

Explanation: The initialization of the agent failed inthe Agent_OnLoad function.


User response: Correct the Agent_OnLoad failure.

JVMJ9TI004I Returns via the capabilities_ptr theextended capabilities available at thistime.

Explanation: An internationalized description of aJVMTI extension.

System action: None.

User response: None.

JVMJ9TI005I Add the new extended capabilitiesfrom capabilities_ptr.




JVMJ9TI006I Relinquish the extended capabilitiesfrom capabilities_ptr.




JVMJ9TI007I Get the current set of extendedcapabilities via capabilities_ptr.




JVMJ9TI011I Add a dynamic -Xtrace option




JVMJ9TI012I Add a dynamic -Xdump option




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).




JVMJ9TI015I Request a Java Lock Monitor (JLM)dump.




JVMJ9TI000E • JVMJ9TI015I

IBM VM messages 15

JVMJ9TI016I Allow inlining in the presence ofmethod enter and exit events (resultingin possibly inaccurate reporting of enterand exit)




JVMJ9TI017I Controls various VM and compilingoptions.




JVMJ9TI018I Sets a method for selective entry andexit notification.




JVMJ9TI019I Sets notification mode for extendedevents, allowing thread-level selectivity




JVMJ9TI020I Gets the OS thread ID from a jthread




JVMJ9TI021I Get extended frame information




JVMJ9TI022I Get extended frame information for allstack traces.




JVMJ9TI025I Allow direct JNI in the presence ofmethod enter and exit events (resultingin possibly inaccurate reporting of enterand exit)




JVMJ9TI026I Trigger a dump using the given RASconfiguration.




JVMJ9TI030I Signal the async event on a singlethread or all threads




JVMJ9TI031I Cancel the async event on a singlethread or all threads




JVMJ9TI070E Agent initialization function %s failedfor library %s, return code %d

Explanation: Agent_OnLoad or Agent_OnAttachfailed to initialize the agent.

System action: The JVM fails to load the agent libraryand ends.

User response: The agent library must be updated tocorrect the agent initialization failure.

JVMJ9TI071E Agent initialization function %s notfound in library %s

Explanation: The specified agent library does notcorrectly follow the JVMTI specification.

System action: The JVM fails to load the agent libraryand ends.

JVMJ9TI016I • JVMJ9TI071E


User response: The agent library must be updated to add the missing initialization function.

J9VM messagesGeneral JVM messages.

JVMJ9VM000E Malformed value forIBM_JAVA_OPTIONS

Explanation: The JVM has found an error whenparsing the environment variableIBM_JAVA_OPTIONS. This problem can be caused bysyntax errors such as unmatched quotes.


User response: Check the syntax of the environmentvariable IBM_JAVA_OPTIONS

JVMJ9VM002E Options file not found

Explanation: The file specified using the option-Xoptionsfile cannot be found.


User response: Correct the command line option for-Xoptionsfile and try again.

JVMJ9VM003W JIT compiler "%s" not found. Willuse interpreter.

Explanation: The value specified for the-Djava.compiler option is not valid.

System action: The JVM continues without a compiler.The performance might be slower.

User response: Correct the value for -Djava.compilerand try again.

JVMJ9VM004E Cannot load library required by: %s

Explanation: JVM initialization uses system services toload numerous libraries, including libraries that arespecified by the user. Libraries can have dependencieson other libraries. This message is produced when alibrary cannot be loaded.

System action: The JVM ends

User response: Check your system to ensure that thelibraries indicated are available and accessible. If thisproblem occurs with an application that has runsuccessfully before, check for any recent changes toyour environment. Contact your IBM servicerepresentative if the problem continues.

JVMJ9VM005E Invalid value for environmentvariable: %s

Explanation: The value entered for the environmentvariable is not valid.


User response: Correct the value for the environmentvariable and try again.

JVMJ9VM006E Invalid command-line option: %s

Explanation: The command-line option is not valid.


User response: Correct or remove the command-lineoption and try again.

JVMJ9VM007E Command-line option unrecognised:%s

Explanation: The command-line option is notrecognized.


User response: Correct or remove the command-lineoption and try again.

JVMJ9VM008E J9VMDllMain not found

Explanation: J9VMDllMain is the main module entrypoint for system libraries. If J9VMDllMain is not foundthe module cannot be used.



JVMJ9VM009E J9VMDllMain failed

Explanation: J9VMDllMain is the main module entrypoint for system libraries. There has been a failureusing J9VMDllMain.



JVMJ9VM010W Failed to initialize %s

Explanation: The identified library cannot beinitialized. This message is typically associated withJVMPI function.

System action: The JVM continues but the functionmight be affected.


JVMJ9VM011W Unable to load %1$s: %2$s

JVMJ9VM000E • JVMJ9VM011W

IBM VM messages 17

Explanation: The JVM failed to load the library namedin the first parameter. The second parameter givesfurther information about the failure.

System action: The JVM continues but might end laterif the library contained core JVM function.

User response: Check the libraries are available andcan be accessed. Contact your IBM servicerepresentative if the problem continues.

JVMJ9VM012W Unable to unload %1$s: %2$s

Explanation: The JVM failed to unload the librarynamed in the first parameter. The second parametergives further information about the failure.


User response: Contact your IBM servicerepresentative if the problem continues.

JVMJ9VM013W Initialization error in function%1$s(%2$d): %3$s

Explanation: This is typically an internal error withinthe JVM.

System action: The JVM continues but might end laterif the error occurred in a critical area.


JVMJ9VM014W Shutdown error in function%1$s(%2$d): %3$s

Explanation: An internal error occurred duringshutdown processing. Further information about theerror is provided.



JVMJ9VM015W Initialization error for library%1$s(%2$d): %3$s

Explanation: A problem occurred when the JVM triedto initialize the library. This can happen when the JVMis started with incorrect options, giving rise toadditional messages.


User response: Check preceding messages for anindication of the problem. Correct the problem and tryagain.

JVMJ9VM016W Shutdown error for library%1$s(%2$d): %3$s

Explanation: An internal error occurred duringshutdown processing. Further information about theerror is provided.


User response: Contact your IBMM servicerepresentative if the problem continues.

JVMJ9VM017E Could not allocate memory forcommand line option array

Explanation: During JVM initialization the commandline options are stored in memory. There was notenough memory available for the JVM to complete theprocess.


User response: This is unlikely to be a problemcaused by starting the JVM. Check your system forhardware or software faults and correct them. Restartyour system and try again. Contact your IBM servicerepresentative if the problem continues.

JVMJ9VM018E Could not allocate memory forshared library load table pool

Explanation: This error is issued when memorycannot be allocated to expand an internal table. This isunlikely to be a problem caused by the JVM.

System action: The JVM continues but is likely to fail.

User response: Check your system for hardware orsoftware faults and correct them. Restart your systemand try again. Contact your IBM service representativeif the problem continues.

JVMJ9VM019E Fatal error: Unable to find andinitialize required class %.*s

Explanation: A required class could not be found orcould not be initialized.



JVMJ9VM020I Searched in %.*s

Explanation: This message lists a class path entry thatwas searched while trying to find a required class.



JVMJ9VM012W • JVMJ9VM020I


JVMJ9VM022E Stack map failed, result = %p -aborting VM

Explanation: An internal error occurred.

System action: The JVM ends with exit code 600 or601.


JVMJ9VM023I This may indicate that JAVA_HOMEis incorrect, or that class libraries are notinstalled

Explanation: A required class could not be found orcould not be initialized. The value set for JAVA_HOMEmight be incorrect, or the class library might not beinstalled correctly.


User response: Check that the JAVA_HOMEenvironment variable is properly set.

JVMJ9VM031E Required class %2$.*1$s must be inthe boot classpath, but was found in theapplication class path in %4$.*3$s

Explanation: A required class was found on theapplication class path, not on the boot classpath. Forsecurity reasons this class must be found on the bootclasspath.


User response: Check your command line options toensure that you have not placed boot classes on theapplication classpath.

JVMJ9VM034E JVMRI requires trace engine: runwith -Xtrace flag

Explanation: Tracing must be enabled to use theJVMRI environment requested.

System action: The JVMRI environment is notreturned with the GetEnv() JNI function.

User response: Add the appropriate -Xtrace option tothe command line.

JVMJ9VM035E Unable to allocateOutOfMemoryError

Explanation: The JVM tried to issue anOutOfMemoryError but failed.


User response: Exceeding the maximum value for the-Xmca and -Xmco options causes this error. Check youruse of these options, the memory usage of yourapplication and try again (possibly using the -Xmxoption on startup). If the problem persists then contact

your IBM service representative.

JVMJ9VM038E -Xthr: unrecognized option --> \'%s\'

Explanation: The value specified for the -Xthr optionwas not recognized.


User response: Correct or remove the -Xthr optionand try again.

JVMJ9VM039I -Xscmx is ignored if -Xshareclasses isnot specified

Explanation: The -Xscmx option is not meaningfulunless shared class support is active.


User response: Remove the -Xscmx option or activateshared classes by using the -Xshareclasses option.

JVMJ9VM050E -Xjni: unrecognized option --> \'%s\'

Explanation: The option specified with the -Xjnicommand-line parameter is not recognized.


User response: Correct the option specified with-Xjni.

JVMJ9VM053E Malformed option %s found in-Xoptionsfile

Explanation: The options file contains an option thatis not correctly specified.


User response: Correct the option in the options file.

JVMJ9VM058I -Xscminaot is ignored if-Xshareclasses is not specified

Explanation: The command-line option -Xscminaot isnot meaningful unless -Xshareclasses is specified.

System action: The JVM ignores the -Xscminaotcommand-line option and continues.

User response: Determine if -Xscminaot should beremoved, or if -Xshareclasses should be added.

JVMJ9VM059I -Xscmaxaot is ignored if-Xshareclasses is not specified

Explanation: The command-line option -Xscmaxaot isnot meaningful unless -Xshareclasses is specified.

System action: The JVM ignores the -Xscmaxaotcommand-line option and continues.

User response: Determine if -Xscmaxaot should beremoved, or if -Xshareclasses should be added.

JVMJ9VM022E • JVMJ9VM059I

IBM VM messages 19

JVMJ9VM061W insertDumpAgent requires %s

Explanation: An internal VM function called via theJVMTI SetVmDump() API has failed because therequired DLL has not been loaded.

System action: The dump options are not changed,JNI_ERR is returned.

User response: Check whether the JVM dumpfunctions have been disabled via the -Xdump:noneoption.

JVMJ9VM062W removeDumpAgent requires %s




JVMJ9VM063W seekDumpAgent requires %s




JVMJ9VM064W setDumpOption requires %s

Explanation: An internal JVM function, called by theJVMTI SetVmDump() API, has failed because therequired DLL is not loaded.

System action: The dump options are not changed.JNI_ERR is returned.

User response: Check whether the JVM dumpfunctions have been turned off with the -Xdump:noneoption.

JVMJ9VM067W -Xshareclasses not enabled,-Xzero:sharezip option ignored

Explanation: The -Xzero:sharezip option is ignored ifshared classes are not enabled.

System action: The JVM ignores the -Xzero:sharezipoption.

User response: This warning message can be ignoredif 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

Explanation: The -Xzero:sharestring option isignored if shared classes are not enabled.

System action: The JVM ignores the-Xzero:sharestring option.

User response: This warning message can be ignoredif you do not want to use the -Xzero:sharestringoption. If you do want to use the -Xzero:sharestringoption, enable shared classes.

JVMJ9VM078E Malformed value forJAVA_TOOL_OPTIONS

Explanation: An option found in the environmentvariable JAVA_TOOLS_OPTIONS is not specifiedcorrectly.


User response: Correct the option in the environmentvariable JAVA_TOOLS_OPTIONS.

JVMJ9VM079W triggerOneOffDump(%1$s) requires%2$s

Explanation: An internal JVM function, called by theJVMTI TriggerVmDump() API, failed because therequired DLL is not loaded.

System action: The requested dump is not triggered.JNI_ERR is returned.


JVMJ9VM080W queryVmDump requires %s

Explanation: An internal VM function, called by theJVMTI QueryVmDump() API, failed because therequired DLL is not loaded.

System action: An empty list of dump optionspecifications is returned.


JVMJ9VM081W Malformed option value, option"%1$s%3$.*2$s" contains trailingcharacters "%4$s" which have beenignored

Explanation: The command-line option containedextra characters that were ignored. These extracharacters might have been intended to be othercommand-line options.

System action: The JVM ignores the extra characters.

JVMJ9VM061W • JVMJ9VM081W


User response: Correct the command-line option andtry again.

JVMJ9VM082E Unable to switch to IFA processor -issue "extattr +a libj9ifa%s.so"

Explanation: The JVM failed to switch to an IFA(Integrated Facility for Applications) processor becausethe JVM library file libj9ifa%s.so requires APFauthorization.

System action: The JVM continues but preventsfurther attempts to switch between IFA and standardprocessors.

User response: Set extended attributes for thelibj9ifa%s.so file using the command extattr +a.

JVMJ9VM083W Error switching to IFA processor rc:%08x

Explanation: The JVM failed to switch to an IFA(Integrated Facility for Applications) processor. Thereturn code indicates the error condition.


User response: Contact your IBM servicerepresentative for further information.

JVMJ9VM084W IFA Error: unexpected return code%08x from IFA switch service

Explanation: The JVM failed to switch to an IFA(Integrated Facility for Applications) processor. Thereturn code indicates the error condition.


User response: Contact your IBM servicerepresentative for further information.

JVMJ9VM085W Malformed option: '%s'

Explanation: The specified option cannot not beparsed.

System action: The JVM ignores the option andcontinues.

User response: Correct the command-line option.

JVMJ9VM086W Option too large: '%s'

Explanation: The specified option is larger than themaximum permitted value.

System action: The JVM ignores the option andcontinues.

User response: Adjust the command-line option.

JVMJ9VM087W resetDumpOption requires %s

Explanation: An internal JVM function, called by theJVMTI ResetVmDump() API, failed because therequired DLL is not loaded.

System action: Dump options are not reset. JNI_ERRis returned.


JVMJ9VM090I Slow response to network query (%dsecs), check your IP DNS configuration

Explanation: A network query used by the JVM topopulate diagnostic data took longer than expected.

System action: The JVM continues but the diagnosticdata is not available.

User response: Check your IP DNS configuration. Forexample, on AIX® and UNIX systems, check the file/etc/resolv.conf.

JVMJ9VM091I Adaptive spinning supported

Explanation: This information message is shown when-Xthr:what is used on the command line.

System action: The JVM prints this informationmessage when -Xthr:what is used on the command lineand adaptive spinning is enabled.


JVMJ9VM092I Adaptive spinning not supported

Explanation: The JVM optimization, adaptivespinning, is not enabled. This information message isshown when the option -Xthr:what is specified on thecommand line.



JVMJ9VM093E This version of Java requires a CPUthat supports SSE2 or later extensions.See the 'Supported Environments'information in the IBM Java User Guidefor more details.

Explanation: The processor does not support the SSE2instruction set.


User response: Run this version of Java on a systemthat supports SSE2 or later extensions. For more details,see the Supported Environments information in theIBM SDK for Java User Guide.

JVMJ9VM082E • JVMJ9VM093E

IBM VM messages 21

JVMJ9VM094I Thread "%s" is still alive afterrunning the shutdown hooks.

Explanation: The JVM cannot shut down because athread is still alive.

System action: DestroyJavaVM() returns JNI_ERR.

User response: Add a shutdown hook to end thethread when the JVM shuts down.

JVMJ9VM096I -Xscdmx is ignored if -Xshareclassesis not specified

Explanation: The option -Xscdmx specifies the size ofthe class debug area in a shared class cache. If-Xshareclasses is not specified, -Xscdmx is ignored.

System action: The option -Xscdmx is ignored.

User response: This warning message can be ignoredif you do not want to use the -Xscdmx option. If you dowant to use the -Xscdmx option, enable shared classes.

JVMJ9VM109E Unsupported operating system (%s):Windows XP or newer is required.

Explanation: The operating system is too old to runthis version of the JVM.


User response: Run the JVM on a system with asupported operating system. For information aboutsupported hardware and software, see the IBM SDK forJava User guides.

JVMJ9VM110E Invalid lockword mode specified:%s

Explanation: The mode specified with the option-Xlockword:mode= is not valid.


User response: Use a supported value for the mode,and start the JVM again.

JVMJ9VM111E Invalid lockword option specified:%s

Explanation: This option used with -Xlockword: is notvalid.


User response: Use a supported -Xlockword optionand start the JVM again.

JVMJ9VM117I -Xitsn is ignored if -Xshareclasses isnot specified

Explanation: -Xitsn is valid only when shared classesare enabled.

System action: The JVM continues and ignores the-Xitsn option.

User response: Enable shared classes with the-Xshareclasses option, or remove the -Xitsn option.

JVMJ9VM120I -Xscminjitdata is ignored if-Xshareclasses is not specified

Explanation: -Xscminjitdata is valid only for sharedclasses.

System action: The JVM continues, but the-Xscminjitdata value is ignored.

User response: 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

Explanation: -Xscmaxjitdata is valid only for sharedclasses.

System action: The JVM ignores the -Xscmaxjitdataoption and continues.

User response: If you want to specify a value for-Xscmaxjitdata, enable shared classes using the-Xshareclasses option.

JVMJ9VM122E Failed to get user32.dll address rangerequired for -Xprotectcontiguous.

Explanation: The JVM failed to find the address rangeof user32.dll.


User response: Run the JVM without the-Xprotectcontiguous option.

JVMJ9VM123E Attempting to run on anon-supported processor, JVM willterminate.

Explanation: The processor is not supported.


User response: See the information about supportedenvironments in the IBM SDK for Java User Guide todetermine the minimum system requirements.

JVMJ9VM129E Application resumed execution afterhandling a fatal condition and illegallyreturned to, or called back into, Java

Explanation: After handling an unrecoverablecondition, the application continues, illegally returningto, or calling back into Java.

System action: The JVM prints the error message andends the process using the z/OS specific system call,CEE3AB2().

User response: Change the user condition handler so

JVMJ9VM094I • JVMJ9VM129E


that the application does not continue when there is anunrecoverable condition on a Java thread.

JVMJ9VM130E Application resumed execution afterhandling a fatal condition and illegallyreturned to, or called back into, Java(JIT'ed code)

Explanation: After handling an unrecoverablecondition, the application continues, illegally returningto, or calling back into Java.

System action: The JVM prints the error message andends the process using the z/OS specific system call,CEE3AB2().

User response: Change the user condition handler sothat the application does not continue when there is anunrecoverable condition on a Java thread.

JVMJ9VM131E Terminating process usingCEE3AB2() with abend %1$u, reason%2$u, cleanup %3$u.

Explanation: The JVM detects an unrecoverablecondition and ends the process using the z/OS specificsystem call, CEE3AB2, which causes an abend.

System action: The JVM prints the error message andends the process.

User response: Check the console and operatorconsole messages. If further assistance is required,contact your IBM Service representative.

JVMJ9VM133W The system core size hard ulimit isset to %d, system dumps may betruncated.

Explanation: The JVM started with the -Xcheck:dumpoption, and detected that the core dump file size islimited by the system hard ulimit.


User response: Refer to the IBM SDK documentation.

JVMJ9VM134W The system fullcore option is set toFALSE, system dumps may be truncated.

Explanation: The JVM started with the -Xcheck:dumpoption, and detected that the system fullcore option isset to FALSE.


User response: Refer to the IBM SDK documentation.

JVMJ9VM135W /proc/sys/kernel/core_pattern setting"%s" specifies that core dumps are to bepiped to an external program. The JVMmay be unable to locate core dumps andrename them.

Explanation: The JVM started on a system with/proc/sys/kernel/core_pattern set to pipe core dumpsto the command specified after the | character. TheJVM might be unable to locate core dumps and renamethem.

System action: The JVM continues. MessageJVMPORT030W is issued when a system dump is taken.

User response: Refer to the product documentationfor the IBM SDK, Java Technology Edition.

JVMJ9VM136W /proc/sys/kernel/core_pattern setting"%s" specifies a format string forrenaming core dumps. The JVM may beunable to locate core dumps and renamethem.

Explanation: The JVM started on a system with/proc/sys/kernel/core_pattern set to rename coredumps. The JVM might be unable to locate the coredump.



JVMJ9VM138W The -Xdiagnosticscollector option isnot supported by this JVM.

Explanation: The JVM started with the-Xdiagnosticscollector option, which is no longersupported.



JVMJ9VM142E The command-line option -Xrealtimeis not supported in this version of theIBM JDK

Explanation: The -Xrealtime option is no longersupported with this release of the IBM developer kit.

System action: The JVM does not start.

User response: Remove this option and try again. Ifyou require -Xrealtime functionality, contact your IBMsupport representative.

JVMJ9VM143E The command-line option %s is notsupported in this version of the IBMSDK

Explanation: The IBM SDK no longer supports the %soption.


User response: Consult your IBM servicerepresentative if % functionality is required or removethe option.

JVMJ9VM130E • JVMJ9VM143E

IBM VM messages 23

JVMJ9VM145E %s is unsupported on z/OS.

Explanation: The specified command-line option isnot supported.


User response: Remove the option from the commandline.

JVMJ9VM167E GC optimizations on idle are notsupported

Explanation: The JVM idle tuning options are notsupported on some platforms and Garbage Collection(GC) policies.


User response: Refer to the documentation forsupported platforms and GC policies.

JITM messagesJIT compiler messages.

JVMJITM000E Unsupported hardware [%d].

Explanation: The current hardware is not supportedby the compiler.

System action: The compiler does not generate codefor this hardware.

User response: Check the IBM Java documentation fora list of supported hardware.

JVMJITM001W No more space for AOT code inshared class cache. New AOT code willnot be generated.

Explanation: The AOT section of the shared classcache is full.

System action: The compiler stops generating AOTcode. The AOT code already stored in the shared classcache continues to be used.

User response: Increase the size of the AOT section ofthe shared class cache using the -Xscmaxaot option.

JVMJITM002W Failure storing AOT code in sharedclass cache. Shared class cache might becorrupted. Ignoring AOT code in sharedclass cache.

Explanation: An error occurred storing AOT code inthe shared class cache.

System action: The compiler stops generating AOTcode. AOT code from the shared class cache is notused.

User response: Destroy and re-create the AOT code inthe shared class cache using the -Xshareclasses:resetoption.

JVMJITM003W Failure during AOT runtimeinitialization. Ignoring AOT code inshared class cache.

Explanation: An error occurred initializing AOT.

System action: The compiler does not generate AOT

code. AOT code from the shared class cache is notused.

User response: If the error occurs again, destroy andre-create the AOT code in the shared class cache usingthe -Xshareclasses:reset option.

JVMJITM004W AOT code in shared class cachecannot execute on current processor.Ignoring AOT code in shared classcache.

Explanation: The AOT code in the shared class cacheis not compiled for this platform.

System action: The compiler does not generate AOTcode. AOT code from the shared class cache is notused.

User response: Destroy and re-create the AOT code inthe shared class cache for the current platform usingthe -Xshareclasses:reset option.

JVMJITM005W AOT code in the shared class cachecannot run on current JVM release.Ignoring AOT code in shared classcache.

Explanation: The AOT code in the shared class cachewas created using a different JVM release.


User response: Destroy and re-create the AOT code inthe shared class cache for the current JVM release usingthe -Xshareclasses:reset option.

JVMJITM006W AOT code in shared class cachecannot run with current garbagecollection policy. Ignoring AOT code inshared class cache.

Explanation: The AOT code in the shared class cachewas created using a different garbage collection policy.

JVMJ9VM145E • JVMJITM006W



User response: Destroy and re-create the AOT code inthe shared class cache for the current garbage collectionpolicy using the -Xshareclasses:reset option.

JVMJITM007W AOT code in shared class cachecannot run with current JVMPI orJVMTI settings. Ignoring AOT code inshared class cache.

Explanation: AOT code cannot be used with JVMPI orJVMTI.


User response: To use AOT code, disable JVMTI.JVMPI is replaced by JVMTI in Java 6.

JVMJITM009E System configuration does notsupport parameter '%.*s' in option '-Xlp'

Explanation: The specified parameter is notrecognized for the -Xlp option.


User response: Remove the unrecognized parameterfrom the -Xlp option and try again.

JVMJITM010E %s must be followed by a number

Explanation: The specified option must be followedimmediately by a number.


User response: Adjust the JIT option. For example,replace -Xlp:objectheap:pagesize <size> with-Xlp:objectheap:pagesize<size>.

JVMJITM011E %s value specified is too large

Explanation: The specified option is too large.


User response: Adjust the JIT options and try again.

JVMJITM012E Value for '%s' is not correct

Explanation: The value specified for the option is notcorrect.


User response: Correct the option and try again.

JVMJITM013E '%1$s' option is not complete, mustspecify '%2$s' parameter.

Explanation: The option specified is not complete.More parameters are required.


User response: Specify all the required parameters forthe -Xlp option.

JVMJITM014I Extra comma characters are discoveredin '-Xlp' option - ignored

Explanation: The -Xlp option specified contains extracomma characters.

System action: The JVM ignores the extra charactersand continues.

User response: Remove the extra commas from the-Xlp option for any future invocation.

JVMJITM015I Large page size %1$zu%2$s is not asupported page size; using %3$zu%4$sinstead

Explanation: The specified large page size is notsupported by the operating system. A default size isused instead.

System action: The JVM starts using the default largepage size.

User response: Adjust the -Xlp option to a specifypage size that is supported by the operating system.

JVMJITM016I Large page size %1$zu%2$s is not asupported page size; using %3$zu%4$s%5$s instead




JVMJITM017I Large page size %1$zu%2$s %3$s isnot a supported page size; using%4$zu%5$s instead




JVMJITM007W • JVMJITM017I

IBM VM messages 25

JVMJITM018I Large page size %1$zu%2$s %3$s isnot a supported page size; using%4$zu%5$s %6$s instead




JNCK messagesJNI messages.

JVMJNCK000E -Xcheck:jni: unrecognized option -->\'%s\'

Explanation: You specified an unrecognized-Xcheck:jni command-line option.

System action: The JVM prints usage information forthe -Xcheck:jni option and ends.

User response: Correct the -Xcheck:jni command-lineoption.

JVMJNCK001I JNI check utility installed. Use-Xcheck:jni:help for usage

Explanation: The JNI check utility has been installed.

System action: The JVM performs additional checkson JNI calls.


JVMJNCK002E JNI check utility: unable to hookevent

Explanation: Initialization of the JNI check utilityfailed because it was unable to intercept native methodcalls.



JVMJNCK023E JNI error detected. Continuing...

Explanation: The JNI check utility has detected arecoverable JNI error.


User response: Investigate the JNI check error thatwas reported in the previous message.

JVMJNCK024E JNI error detected. Aborting.

Explanation: The JNI check utility detected anunrecoverable JNI error.


User response: Investigate the JNI check error thatwas reported in the previous message.

JVMJNCK025I Use -Xcheck:jni:nonfatal to continuerunning when errors are detected.

Explanation: The JVM detected a JNI error and ended.You can use the -Xcheck:jni:nonfatal parameter tochange this behaviour.


User response: If required, rerun with the-Xcheck:jni:nonfatal parameter.

JVMJNCK062W JNI warning in %s: This functionshould not be called inside of a criticalsection

Explanation: A JNI function was called within a JNIcritical section.


User response: Check and correct the JNI applicationcode.

JVMJNCK077E Error detected in%2$.*1$s.%4$.*3$s%6$.*5$s

Explanation: This message provides additionalinformation about the Java class and method that wereused in the JNI function identified in a previous errormessage.


User response: Investigate the previous error message.

JVMJNCK078W Warning detected in%2$.*1$s.%4$.*3$s%6$.*5$s

Explanation: This message provides additionalinformation about the Java class and method that wereused in the JNI function identified in a previouswarning message.


User response: Investigate the previous warningmessage.

JVMJNCK079I Advice detected in%2$.*1$s.%4$.*3$s%6$.*5$s

Explanation: This message provides additional

JVMJITM018I • JVMJNCK079I


information about the Java class and method that wereused in the JNI function identified in a previous advicemessage.


User response: Investigate the previous advicemessage.

JVMJNCK080E Error detected in the outermost frameof an attached thread

Explanation: This message provides additionalinformation about the frame context of the JNI functionthat was identified in a previous error message.


User response: Investigate the previous errormessages.

JVMJNCK081W Warning detected in the outermostframe of an attached thread

Explanation: This message provides additionalinformation about the frame context of the JNI functionthat was identified in a previous warning message.


User response: Investigate the previous warningmessages.

JVMJNCK082I Advice detected in the outermostframe of an attached thread

Explanation: This message provides additionalinformation about the frame context of the JNI functionthat was identified in a previous advice message.


User response: Investigate the previous advicemessages.

JVMJNCK083E Error detected in JNI_OnLoad oflibrary %.*s

Explanation: This message provides additionalinformation about the JNI function that was identifiedin a previous error message.


User response: Investigate the previous error message.

JVMJNCK084W Warning detected in JNI_OnLoad oflibrary %.*s

Explanation: This message provides additionalinformation about the JNI function that was identifiedin a previous warning message.


User response: Investigate the previous warningmessage.

JVMJNCK085I Advice detected in JNI_OnLoad oflibrary %.*s

Explanation: This message provides additionalinformation about the JNI function that was identifiedin a previous advice message.


User response: Investigate the previous advicemessage.

JVMJNCK089E Error detected in the handler frameof a JVMPI or JVMTI event

Explanation: This message provides additionalinformation about the frame context of the JNI functionthat was identified in a previous error message.


User response: Investigate the previous errormessages.

JVMJNCK090W Warning detected in handler frameof a JVMPI or JVMTI event

Explanation: This message provides additionalinformation about the frame context of the JNI functionthat was identified in a previous warning message.


User response: Investigate the previous warningmessages.

JVMJNCK091I Advice detected in handler frame of aJVMPI or JVMTI event

Explanation: This message provides additionalinformation about the frame context of the JNI functionthat was identified in a previous advice message.


User response: Investigate the previous advicemessages.

MECK messagesMemory checking messages.

JVMMECK000E An error occurred initializing the-Xcheck:memory utility

Explanation: The memory check utility could notlocate the required virtual machine resources.

JVMJNCK080E • JVMMECK000E

IBM VM messages 27

System action: The requested memory check is notperformed.

User response: Verify that your Java runtimeenvironment is correctly installed.

JVMMECK001E Unrecognized -Xcheck:memoryoption: %s

Explanation: The memory check that you requested isnot a recognized type.

System action: The Java application runs but nomemory checks are performed.

User response: Run the JVM with the

-Xcheck:memory:help option to list the valid checks.

JVMMECK002E An error occurred creating the callsite data structure. Call site informationwill not be displayed

Explanation: The memory check utility could not storeinformation about the source code locations of memoryrequests.

System action: The JVM performs the memory checkswithout recording memory requestor information.

User response: Check that your system is configuredwith sufficient memory.

OFFC messagesJNI control messages.

JVMOFFC000E -Xoffload:sim: unrecognized option--> \'%s\'

Explanation: You specified an invalid option for the-Xoffload:sim parameter.


User response: Use a valid option for the-Xoffload:sim parameter.

JVMOFFC001I Offload simulator utility installed.Use -Xoffload:sim:help for usage

Explanation: You specified the -Xoffload:simparameter when you started the JVM.

System action: The JVM runs with the -Xoffload:simparameter options that you supplied.

User response: This message is for information only.No action is required.

JVMOFFC002E Offload Simuator: Applying %dmillisecond tax to each JNI call.

Explanation: You specified the -Xoffload:sim:delayoption when you started the JVM.

System action: The JVM runs, applying the tax thatyou specified.


JVMOFFC003E Offload Simuator: Applying %dmicrosecond tax to each JNI call.

Explanation: You started the JVM with the-Xoffload:sim:delay option with microsecondsspecified.

System action: The JVM applies the tax that youspecified.


JVMOFFC004E Offload Simuator: Delay tax usingspin.

Explanation: You started the JVM with the-Xoffload:sim:delay option, and spinning is used todelay tax.

System action: The JVM uses spinning to apply thetax that you specified.


JVMOFFC005E Offload Simuator: Delay tax usingsleep.

Explanation: You started the JVM with the-Xoffload:sim:delay option, and sleeping is used todelay tax.

System action: The JVM uses sleeping to apply the taxthat you specified.


JVMOFFC007E Offload Simuator: Clock frequency is%llu ticks/second, have_nanosleep=%d

Explanation: You started the JVM with the-Xoffload:sim:delay option, which displays the clockfrequency and whether nanosleep is supported. Thehave_nanosleep value is 0 when nanosleep is supportedand nonzero otherwise.

System action: The JVM displays the clock frequencyand whether nanosleep is supported.


JVMMECK001E • JVMOFFC007E


JVMOFFC008E Offload Simulator: Invalid sleeptime, please choose a time >= 1millisecond.

Explanation: You specified an invalid sleep time in the-Xoffload:sim:delay=Xms option.


User response: Start the JVM again, specifying a sleeptime that is greater than or equal to 1 millisecond.

JVMOFFC009E Offload: Fatal error, unable to hookevent

Explanation: You ran the JVM with the -Xoffload:simoption, and the JVM encountered an internal error.



JVMOFFC010E Unrecognized time units -> %s

Explanation: The value of xx specified in-Xoffload:sim:delay=Yxx is not a valid time unit.


User response: Start the JVM again, specifying eitherms or µs as the time units.

JVMOFFC022I Offload Trace utility installed. Use-Xoffload:trace:help for usage

Explanation: You started the JVM with the-Xoffload:trace option.

System action: The JVM performs offload tracing.


JVMOFFC023E Offload Trace: Tuning Fork loggingto %s

Explanation: You specified the-Xoffload:trace:tuningfork option.

System action: The JVM logs offload tracing to tuningfork.


JVMOFFC024I Offload: JNI Isolation enabled forlibrary group {%s}.

Explanation: You started the JVM with the-Xoffload:isolate option, specifying one or morelibraries.

System action: The native code in the libraries is runin external quarantines.


JVMOFFC025E Offload:Failed to start quarantinecontroller with url=%s.

Explanation: Java offload was requested, but the Javaprocess could not connect to the remote process.


User response: Ensure that there are no firewalls orother impediments to communication between themachine on which you invoked the Java process andthe machine to which it is being offloaded. Then startthe JVM again.

JVMOFFC026E Offload:Invalid connectioninformation for remote isolation.

Explanation: You specified remote isolation on thecommand line, but the connection information that yousupplied is not valid.


User response: Correct the connection informationthat you specified on the command line, then start theJVM again.

JVMOFFC027E Offload:Connection informationmissing for remote isolation.

Explanation: You specified remote isolation on thecommand line, but did not supply connectioninformation.


User response: Add the connection information on thecommand line then start the JVM again.

JVMOFFC028E Offload:Failed to start localquarantine controller.

Explanation: An internal error occurred when tryingto start the JVM in offload mode.



JVMOFFC029E Offload:Failed to create offloadmanager.

Explanation: An internal error occurred when tryingto start the JVM in offload mode.



JVMOFFC008E • JVMOFFC029E

IBM VM messages 29

JVMOFFC030E Offload:Could not find local nativesproperties file {%s}.

Explanation: The file specifying the native code that isrun locally could not be found. The message includesthe location and name of the expected file.


User response: Restore the file from a copy of theJVM, then start the JVM again.

JVMOFFC031E Offload:Local natives properties filehas invalid format {%s}.

Explanation: The content of the file specifying thenative code that is run locally is not valid. The messageincludes the name of the file from which the content isread.



PORT messagesPort library messages.

JVMPORT001E Failed to allocate memory whileattempting to write to a file.

Explanation: The system was unable to satisfy amemory allocation request.

System action: Subsequent memory allocationattempts are likely to fail, resulting in the terminationof the process.

User response: Increase the amount of memoryavailable to the process, or contact your IBM servicerepresentative.

JVMPORT002E Unknown error loading sharedlibrary

Explanation: There was an unknown error loading ashared library.

System action: The process shuts down.

User response: This message is accompanied byanother message that provides more detail. Check thatthe shared library exists. If the library exists, contactyour IBM service representative.

JVMPORT003E Dependent module %s could not beloaded

Explanation: The named dependent module could notbe loaded.

System action: If the module was critical to the JVM,the process ends.

User response: If the JVM ends, contact your IBMservice representative.

JVMPORT004E Symbol resolution failure

Explanation: There was a problem with symbolresolution while looking for a particular symbol.

System action: If the symbol was critical to the JVM,the JVM ends, and more information is provided.

User response: If the JVM ends, contact your IBMservice representative.

JVMPORT015E Unable to resolve shared libraryreferences - a prerequisite shared librarymay be missing

Explanation: The operating system could not resolve ashared library reference. A prerequisite shared librarymight be missing.

System action: If the library is critical to the JVM, theprocess ends.

User response: If the process ends, check that thelibrary exists. If the library exists, contact your IBMservice representative.

JVMPORT016E Internal Error %i

Explanation: An internal error occurred while lookingfor a shared library.

System action: If the library is critical to the JVM, theprocess ends.

User response: If the process ends, check that thelibrary exists. If the library exists, contact your IBMservice representative.

JVMPORT019W Unable to create directory %s.Shared classes will be disabled untilthis directory is created.

Explanation: You included a directory when youprovided the name of the shared classes cache. Thisdirectory could not be created.

System action: If you specified the-Xshareclasses:nonfatal parameter, the JVM continueswithout using shared classes. If you did not specifythat parameter, the JVM ends.


JVMOFFC030E • JVMPORT019W


JVMPORT022I Appending .X&DS to user-specifieddump template to enable multi-partdumps.

Explanation: You specified a dump template, by usingthe -Xdump:system:file= parameter or theJAVA_DUMP_TDUMP_PATTERN environmentvariable. The maximum amount of data that can bedumped in a single IEATDUMP file is 2 GB. Foraddress spaces larger than 2 GB, the z/OS operatingsystem generates multiple dump files. To enable thisbehavior, the suffix &DS is required in the dump name.The suffix is replaced with a counter that identifieswhich part of the dump is in the file. If you do not addthe suffix, the JVM appends it to the dump template.

System action: The JVM adds .X&DS to the dumptemplate, then continues to run.

User response: You can ignore this message, andallow the JVM to alter the dump file name, unless theextended dump file name is too long. If the file name istoo long, the JVM uses the default dump templateinstead. Avoid the message by including the &DS suffixin your dump template or by using the default dumptemplate.

JVMPORT023W IEATDUMP failed becauseuser-specified dump template was toolong. Retrying dump with defaulttemplate.

Explanation: You specified a dump template, by usingthe -Xdump:system:file= parameter or theJAVA_DUMP_TDUMP_PATTERN environmentvariable. When the system tried to take a dump byusing the template, the IEATDUMP routine returnedwith return code 0x8 and reason code 0x22, indicatingthat the dump failed because the name was too long.

System action: The JVM tries to take the dump againusing the default dump template.

User response: Specify a shorter dump template. Notethat, on the z/OS 64 operating system, the JVMappends .X&DS to the user-specified dump template, toenable multi-part z/OS dumps (required to store a full64-bit address space). If the template you specified wasclose to 44 characters long, the addition of .X&DS mightmake it too long.

JVMPORT024E IEATDUMP failed because wecouldn't allocate the dump dataset(likely disk full).

Explanation: The JVM attempted to take anIEATDUMP, but the dump routine returned with returncode 0x8 and reason code 0x26, indicating that thedump failed because the dump data set could not beallocated.

System action: The JVM continues, but fails to createa dump.

User response: The most common cause for this errormessage is that you have run out of space for dumpdata sets. Check your available dump storage.

JVMPORT025E Invalid lock type for file lockoperation. lockFlags: %1$d

Explanation: A file lock operation failed because thevalue of the flag that specifies the lock type was notvalid.

System action: The normal operation of the JVM isaffected, possibly resulting in a failure to load one ormore libraries.


JVMPORT026E File specified is a directory

Explanation: A file-open operation failed when thesystem attempted to open a directory as a file.



JVMPORT027E mmap failed due to invalid memoryprotection parameter.

Explanation: The value for the memory protectionparameter is not valid.



JVMPORT028E mmap failed due to invalid mappingoptions.

Explanation: The value for the flag parameter thatspecifies mapping options is not valid.



JVMPORT029E Invalid handle. file handle: %1$d.

Explanation: A file map operation failed because a filehandle was not valid.


JVMPORT022I • JVMPORT029E

IBM VM messages 31


JVMPORT030W %s setting "%s" specifies that thecore dump is to be piped to an externalprogram. Attempting to rename eithercore or core.%d.

Explanation: Linux tools such as ABRT and Apportuse the information in the /proc/sys/kernel/core_pattern file to redirect the core file to an externalprogram, for example to create bug reports.

System action: The virtual machine looks in thecurrent directory for a file called either core orcore.process ID, depending on the contents of the/proc/sys/kernel/core_uses_pid file.

User response: Refer to the documentation for theexternal program specified in the /proc/sys/kernel/core_pattern file.

JVMPORT031E The LE condition %s%i, whichcorresponds to a software-raised POSIXsignal, was received

Explanation: The JVM was instructed at startup to runwith Language Environment® (LE) condition handlersinstead of POSIX signal handlers. A LE condition thatcorresponds to a software-raised POSIX signal wasreceived.

System action: The JVM creates a dump containingdiagnostic data and ends.


JVMPORT034W Attempted to attach shared memorycreated in storage protection key %lu,but currently running in key %lu.

Explanation: Shared memory could not be openedbecause the z/OS storage protection key used to createthe shared memory is not compatible with the currentstorage protection key.


User response: Any problems are reported using adifferent message. Check for other error messages.

JVMPORT035E __malloc31 failed to allocate bufferon z/OS

Explanation: The __malloc31 process failed to allocatea buffer.

System action: The JVM continues, but hypervisorrelated information is not provided.


JVMPORT036E Unexpected return code from CSRSIservice on z/OS

Explanation: An unexpected return code is receivedfrom the CSRSI service on z/OS.

System action: The JVM continues, but hypervisorrelated information is not provided.


JVMPORT038E Malformed value forIBM_JAVA_HYPERVISOR_SETTINGS

Explanation: The IBM_JAVA_HYPERVISOR_SETTINGSenvironment variable is missing a closing quotecharacter.


User response: Correct theIBM_JAVA_HYPERVISOR_SETTINGS environment variableand try again.

JVMPORT046E The executable could not be opened

Explanation: The executable file could not be opened.

System action: The process shuts down.

User response: This message is accompanied byanother message that provides more detail.

JVMPORT048E Failed to create system dumpbecause a non-regular file \"%s\" existswith the same name as the expectedsystem dump file

Explanation: The JVM did not produce a systemdump because a non-regular file exists with the samename as the expected system dump file. Thenon-regular file might be a directory, symbolic link,pipe, or socket.


User response: Check whether the name of anon-regular file in the current working directory of theJava application clashes with one of the followingnames or settings:

v The default system dump file name, which is core orcore.<process ID>.

v 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.

JVMPORT030W • JVMPORT048E


SHRC messagesShared classes messages.

JVMSHRC004E Cannot destroy cache "%s"

Explanation: The shared class cache could not bedestroyed.

System action: Processing continues.

User response: Other messages might indicate thereason why the cache has not been destroyed.Investigate these messages.

JVMSHRC005I No shared class caches available

Explanation: There are no shared class caches on thesystem that can be processed by the commandrequested.



JVMSHRC006I Number of caches expired within last%1$d minutes is %2$d

Explanation: This is an information message.



JVMSHRC007I Failed to remove shared class cache"%s"

Explanation: The shared class cache could not beremoved.


User response: Other messages might indicate thereason why the cache has not been removed.Investigate these messages.

JVMSHRC010I Shared cache "%s" is destroyed

Explanation: The shared class cache has beendestroyed as requested.

System action: A JVM is not created and a failuremessage is issued, as expected.

User response: No action is required. This is aninformation message issued when you destroy a sharedclass cache.

JVMSHRC012I Cannot remove shared cache "%s" asthere are JVMs still attached to thecache

Explanation: The shared class cache cannot beremoved because a process, or processes, are stillattached.

System action: The JVM ends, unless you havespecified the nonfatal option with-Xshareclasses:nonfatal, in which case the JVMcontinues without using shared classes.

User response: Wait until any processes using theshared class cache have ended and then remove it.

JVMSHRC013E Shared cache "%s" memory removefailed

Explanation: The shared class cache cannot beremoved because there is shared memory associatedwith the cache that cannot be removed.



JVMSHRC014E Shared cache "%s" semaphoreremove failed

Explanation: The shared class cache cannot beremoved because there is a shared semaphoreassociated with the cache that cannot be removed.



JVMSHRC015E Shared Class Cache Error: Invalidflag

Explanation: An error occurred during shared classprocessing.



JVMSHRC017E Error code: %d

Explanation: This message shows the error coderelating to a error that will have been the subject of aprevious message.

System action: The JVM ends, unless you havespecified the nonfatal option with

JVMSHRC004E • JVMSHRC017E

IBM VM messages 33

"-Xshareclasses:nonfatal", in which case the JVMcontinues without using shared classes.

User response: Contact your IBM servicerepresentative, unless previous messages indicate adifferent response.

JVMSHRC018E cannot allocate memory

Explanation: The system is unable to obtain sufficientmemory.


User response: The system might be low on resources.Try again when the system is more lightly loaded. Ifthe situation persists, contact your IBM servicerepresentative.

JVMSHRC019E request length is too small

Explanation: The size requested for the shared classcache is too small.


User response: Increase the size for the shared classcache using the -Xscmx parameter or allow it to take thedefault value by not specifying the -Xscmx option.

JVMSHRC020E An error has occurred while openingsemaphore

Explanation: An error has occurred during sharedclass processing. Further messages might follow,providing more detail.


User response: Contact your IBM servicerepresentative, unless subsequent messages indicateotherwise.

JVMSHRC021E An unknown error code has beenreturned

Explanation: An error has occurred during sharedclass processing. This message is followed by details ofthe numeric error code returned.



JVMSHRC022E Error creating shared memory region

Explanation: An error has occurred during sharedclass processing.



JVMSHRC023E Cache does not exist

Explanation: An attempt has been made to open ashared class cache that does not exist.



JVMSHRC024E shared memory detach error




JVMSHRC025E error attaching shared memory


System action: If the cache is damaged, the JVMattempts to re-create it. Otherwise the JVM ends, unlessyou have specified the nonfatal option with-Xshareclasses:nonfatal, in which case the JVMcontinues without using shared classes.




JVMSHRC026E Cannot create cache of requestedsize: Please check your SHMMAX andSHMMIN settings

Explanation: The system cannot create a shared classcache of the size requested by the -Xscmx parameter. If-Xscmx is not specified the default is 16MB.


User response: Refer to the product documentationfor information about shared memory size limits foryour operating system. Restart the JVM with anacceptable shared cache size.

JVMSHRC027E Shared cache name is too long

Explanation: The name specified for the shared classcache is too long for the operating system.


User response: Specify a shorter name for the sharedclass cache and restart the JVM.

JVMSHRC028E Permission Denied

Explanation: The system does not have permission toaccess a system resource.


User response: Check earlier messages to find theresource that cannot be accessed. Only the user whocreates the shared class cache has access to it, unlessthe -Xshareclasses:groupAccess option is specified. Inthis case, a user must belong to the same group as theuser who created the shared class cache.

JVMSHRC029E Not enough memory left on thesystem

Explanation: There is not enough memory available tocreate the shared cache memory or semaphore. Aprevious message indicates the shared cache memoryor semaphore concerned.


User response: The system might be low on resources.Try again when the system is more lightly loaded. If

the situation persists, contact your IBM servicerepresentative.

JVMSHRC030E The Shared Class Cache you areattaching has invalid header.

Explanation: The shared class cache you are trying touse is invalid.

System action: If the cache is damaged, the JVMattempts to re-create it. Otherwise the JVM ends, unlessyou have specified the nonfatal option with-Xshareclasses:nonfatal, in which case the JVMcontinues without using shared classes.


JVMSHRC057E Wrong parameters for expire option

Explanation: The value specified for the expireparameter of -Xshareclasses is invalid.


User response: Correct the value for the expire optionand restart the JVM. The value must be a positiveinteger.

JVMSHRC058E Cannot allocate memory forClasspathItem inshrinit::hookStoreSharedClass

Explanation: An error has occurred in shared classprocessing.



JVMSHRC059E Cannot allocate memory forClasspathItem inshrinit::hookFindSharedClass





IBM VM messages 35


JVMSHRC060E Cannot allocate memory for stringbuffer in shrinit::hookFindSharedClass




JVMSHRC061E Cache name should not be longerthan 64 chars. Cache not created.

Explanation: The name of the shared class cachespecified to the JVM exceeds the maximum length.


User response: Change the shared class cache name sothat it does not exceed the maximum allowed length.

JVMSHRC063E Cannot allocate memory forsharedClassConfig in shrinit




JVMSHRC064E Failed to create configMonitor inshrinit



User response: This might be due to problems withthe operating system. Restart the JVM. If the situationpersists, contact your IBM service representative.

JVMSHRC065E Cannot allocate pool in shrinit




JVMSHRC066I Locking of local hashtables disabled

Explanation: This message confirms that locking oflocal hashtables for the shared class cache has beendisabled as requested.


User response: No action is required. The message isissued when verbose messages are requested.

JVMSHRC067I Timestamp checking disabled

Explanation: This message confirms that sharedclasses timestamp checking has been disabled asrequested.



JVMSHRC068I Local caching of classpaths disabled

Explanation: This message indicates that the cachingof classpaths in the shared class cache has beendisabled as requested.



JVMSHRC069I Concurrent store contentionreduction disabled

Explanation: This message confirms that sharedclasses concurrent store contention reduction has beendisabled as requested.



JVMSHRC060E • JVMSHRC069I


JVMSHRC070I Incremental updates disabled

Explanation: This message confirms that sharedclasses incremental updates have been disabled asrequested.



JVMSHRC071E Command-line option "%s" requiressub-option

Explanation: The specified command-line optionrequires further information.


User response: Update the command-line option andtry again.

JVMSHRC072E Command-line option "%s"unrecognized

Explanation: The specified command-line option isnot recognized.


User response: Correct or remove the invalidcommand-line option and try again.

JVMSHRC077E Failed to create linkedListImpl poolin SH_ClasspathManagerImpl2




JVMSHRC080E Cannot allocate memory forhashtable entry




JVMSHRC082E Cannot create identifiedMutex inSH_ClasspathManagerImpl2




JVMSHRC083E Cannot allocate memory foridentifiedClasspaths array inSH_ClasspathManagerImpl2




JVMSHRC084E Cannot allocate memory for linkedlist item




JVMSHRC086E Cannot enter ClasspathManagerhashtable mutex



JVMSHRC070I • JVMSHRC086E

IBM VM messages 37


JVMSHRC087E MarkStale failed duringClasspathManager::update()




JVMSHRC088E Failed to create cache asROMImageSegment in SH_CacheMap




JVMSHRC089E Cannot create refresh mutex inSH_CacheMap




JVMSHRC090E Failed to get cache mutex inSH_CacheMap startup




JVMSHRC091E Read corrupt data for item 0x%p(invalid dataType)


System action: The cache is marked as corrupt andthe JVM continues.


JVMSHRC092E ADD failure when reading cache




JVMSHRC093I Detected unexpected termination ofanother JVM during update

Explanation: The JVM detected that another JVMended unexpectedly while updating the shared classcache.


User response: No action required. This message is forinformation only.

JVMSHRC095E Attempts to call markStale on sharedcache items have failed




JVMSHRC096I Shared cache "%s" is full. Use -Xscmxto set cache size.

Explanation: The named shared class cache is full andno further classes can be added to it.

System action: The JVM continues. The named sharedcache is still operational and continues to provideincreased performance for loading the classes itcontains. However, classes not contained in the cacheare loaded from their source.

User response: To gain the full benefit of sharedclasses, delete and re-create the named cache. Specify a



larger shared class cache size using the -Xscmxparameter.

JVMSHRC097E Shared cache "%s" is corrupt. Nonew JVMs will be allowed to connect tothe cache. Existing JVMs can continue tofunction, but cannot update the cache.

Explanation: The shared class cache named in themessage is damaged.

System action: The JVM attempts to re-create thecache before starting. If the cache cannot be re-createdthe JVM ends, unless you have specified the nonfataloption with -Xshareclasses:nonfatal.

User response: Remove the shared class cache namedin the message and restart the JVM. If the situationpersists, contact your IBM service representative.

JVMSHRC125E Could not allocate memory for stringbuffer in SH_CacheMap




JVMSHRC126E Request made to add too many itemsto ClasspathItem




JVMSHRC127E SH_CompositeCache::enterMutexfailed with return code %d. Warning:your cache may be corrupt.

Explanation: An error has occurred while trying toupdate the shared class cache.



JVMSHRC128E SH_CompositeCache::exitMutexfailed with return code %d. Warning:your cache may be corrupt.




JVMSHRC129E Attempt to set readerCount to -1!




JVMSHRC130E Attempt to allocate while commit isstill pending

Explanation: An error has occurred while updatingthe shared class cache.

System action: Processing continues, if possible.


JVMSHRC134E Failed to create pool inSH_ROMClassManagerImpl




JVMSHRC137E SAFE MODE: Warning: ROMClass%.*s does not match ROMClass in cache

Explanation: This message is issued when runningshared classes in safe mode and a mismatch inROMClass bytes is detected. This message will befollowed by further details of the class sizes and detailsof the mismatched bytes.


User response: None required. This message is forinformation only. The mismatch in bytes does not meanthat an error has occurred, but could indicate, forexample, that the class has changed since originallystored in the cache.


IBM VM messages 39

JVMSHRC147E Character %.*s not valid for cachename

Explanation: The shared class cache name specified tothe JVM contains invalid characters.


User response: Correct the shared class cache name sothat all characters are valid and restart the JVM.

JVMSHRC154E Escape character %.*s not valid forcache name

Explanation: An invalid escape character has beenspecified in a shared class cache name.


User response: Specify a valid escape character. Validescape characters are %%u for username and %%g forgroup name. Group name is not valid for Windows.

JVMSHRC155E Error copying username into cachename

Explanation: The system could not obtain theusername for inclusion in the shared class cache name.



JVMSHRC156E Error copying groupname into cachename

Explanation: The system could not obtain thegroupname for inclusion in the shared class cachename.



JVMSHRC157I Unable to allocate %1$d bytes ofshared memory requested. Succesfullyallocated maximum shared memorypermitted (%2$d bytes). (To increaseavailable shared memory, modify systemSHMMAX value)

Explanation: The system could not create a sharedclass cache of the size requested (1$).

System action: A cache of the maximum sizepermitted for the system is created. The JVM continues.

User response: If you require a larger cache, removeand re-create the cache, increasing the value ofSHMMAX.

JVMSHRC158I Created shared class cache "%1$s"

Explanation: A shared class cache with the givenname has been created.


User response: No action is required. This message isissued when verbose shared class messages arerequested.

JVMSHRC159I Opened shared class cache "%1$s"

Explanation: An existing shared class cache has beenopened.



JVMSHRC160E The wait for the creation mutexwhile opening semaphore has timed out

Explanation: An error has occurred with sharedclasses processing.


User response: If the condition persists, contact yourIBM service representative.

JVMSHRC161E The wait for the creation mutexwhile creating shared memory has timedout






JVMSHRC162E The wait for the creation mutexwhile opening shared memory hastimed out




JVMSHRC166I Attached to cache "%1$s", size=%2$dbytes

Explanation: The JVM is attached to the cache named1$, which is 2$ bytes in size.



JVMSHRC168I Total shared class bytes read=%1$lld.Total bytes stored=%2$d

Explanation: This message details the number of bytesread from the shared classes cache (1$), and thenumber of bytes stored in the cache (2$).


User response: No action is required. This message isissued when verbose shared class messages arerequested, and the JVM ends.

JVMSHRC169I Change detected in %2$.*1$s......marked %3$d cached classes stale

Explanation: A change is detected in classpath 2$,causing 3$ classes to be marked as "stale" in the sharedclasses cache.



JVMSHRC171E z/OS cannot create cache ofrequested size: Please check your z/OSsystem BPXPRMxx settings

Explanation: z/OS cannot create a shared classescache of the requested size.


User response: If you need a cache of this size, askyour system programmer to increase the z/OS systemBPXPRMxx settings.

JVMSHRC172E Cannot create cache of requestedsize due to Operating Systemrestrictions

Explanation: The size of the cache you requestedcannot be created by the operating system.


User response: Refer to information about cache sizelimits in the Java documentation.

JVMSHRC179E The ROMClass segment has beencorrupted. Error reading ROMClass at0x%p




JVMSHRC180E Cannot allocate memory forhashtable entry in ScopeManagerImpl




JVMSHRC181E Cannot enter ScopeManagerImplhashtable mutex





IBM VM messages 41

JVMSHRC190E -Xscminaot value should not begreater than -Xscmaxaot value

Explanation: The value for -Xscminaot cannot begreater than -Xscmaxaot.


User response: Change the value of -Xscminaot to beless than -Xscmaxaot.

JVMSHRC191I -Xscminaot value is greater than-Xscmx value, so it has been set to equal-Xscmx value

Explanation: The value for -Xscminaot cannot begreater than -Xscmx.


User response: No action is required. The value ischanged automatically.

JVMSHRC192I -Xscmaxaot value is greater than-Xscmx value, so it has been set tounlimited

Explanation: The value for -Xscmaxaot cannot begreater than -Xscmx.


User response: No action is required. The value ischanged automatically.

JVMSHRC202E Failed to initialize pools in sharedclass Manager

Explanation: An error has occurred while initializingshared classes.



JVMSHRC203E Cannot create hashtable in sharedclass Manager




JVMSHRC204E Cannot create hashtable mutex inshared class Manager




JVMSHRC220E Port layer error code = %1$d

Explanation: This message shows the last portableerror code stored in the J9 Port layer. It indicates thelast error encountered.

System action: The JVM ends, unless-Xshareclasses:nonfatal is specified, in which case itcontinues without using shared classes.


JVMSHRC221E Platform error message: %1$s

Explanation: This message shows the last portableerror code stored in the J9 Port layer, indicating the lasterror encountered.



JVMSHRC222E Persistent shared class caches cannotbe created/used as memory mappingdoes not support the requiredcapabilities




JVMSHRC223E Persistent shared class caches cannotbe created/used as file locking is notsupported





-Xshareclasses:nonfatal, in which case the JVMcontinues without using shared classes.


JVMSHRC225E Error obtaining cache file path




JVMSHRC226E Error opening shared class cache file




JVMSHRC227E Error acquiring shared class cachefile header write lock




JVMSHRC228E Error updating shared class cachelast attached time




JVMSHRC229E Error: shared class cache file has aninvalid header




JVMSHRC230E Error initialising shared cache dataheader




JVMSHRC231E Error setting shared class cache filelength




JVMSHRC232E Cannot create a cache in readonlymode

Explanation: An error has occurred within sharedclasses processing.


User response: Remove the read-only option from thecommand-line and restart the JVM.

JVMSHRC233E Error creating shared class cache fileheader


System action: The JVM ends, unless you havespecified the nonfatal option with-Xshareclasses:nonfatal, in which case the JVM


IBM VM messages 43

continues without using shared classes.


JVMSHRC234E Error acquiring shared class cachefile attach read lock




JVMSHRC235E Error releasing shared class cachefile attach read lock




JVMSHRC236I Created shared classes persistentcache %1$s

Explanation: Shared cache %1$s has been created as apersistent cache. This message is produced when-Xshareclasses:verbose is specified.



JVMSHRC237I Opened shared classes persistentcache %1$s

Explanation: Shared classes persistent cache %1$s hasbeen opened. This message is produced when-Xshareclasses:verbose is specified.



JVMSHRC241E Error: unable to delete shared classcache file




JVMSHRC242E Error updating shared class cachefile last detached time




JVMSHRC244E Error obtaining shared class cachefile length




JVMSHRC245E Error mapping shared class cachefile




JVMSHRC246I Attached shared classes persistentcache %1$s

Explanation: Shared classes persistent cache %1$s hasbeen successfully attached to the process. This messagemight appear multiple times in verbose output.



JVMSHRC247E Error shared class cache file headereyecatcher is invalid






JVMSHRC250E Cache cannot be opened read-only asit has not yet initialized

Explanation: The cache has not completedinitialization and cannot be opened in read-only mode.


User response: Wait until the cache has initialized orremove the read-only option.

JVMSHRC254E Error setting length of shared classcache file




JVMSHRC255E Error updating shared class cachefile last detached time on JVM exit




JVMSHRC256I Persistent shared cache "%1$s" hasbeen destroyed

Explanation: The shared cache 1$ has been removedas requested. This message is only issued if verboseshared classes messages has been requested with-Xshareclasses:verbose.

System action: When the cache is removed, the JVMends.


JVMSHRC257E Cannot allocate memory for linkedlist item in Manager





JVMSHRC258E Cannot allocate memory forhashtable entry in Manager




JVMSHRC259E Cannot enter Manager hashtablemutex




JVMSHRC260E Failed to create pool inByteDataManager




JVMSHRC269I The system does not support memorypage protection

Explanation: Memory page protection is notsupported on the runtime platform. This feature isdisabled.

System action: Pages of the shared class cache are notprotected against accidental corruption.


JVMSHRC271E Unrecognised sub-option for optionmprotect=

Explanation: The sub-option you provided formprotect= was not recognized.



IBM VM messages 45

User response: Provide a valid sub-option and restartthe JVM.

JVMSHRC272I Full memory page protectionsuccessfully enabled for cache

Explanation: Every memory page of the cache hasbeen protected.

System action: If any page of the cache is accessedillegally, the JVM ends.


JVMSHRC273I Default memory page protectionsuccessfully enabled for cache

Explanation: All memory pages of the cachecontaining runtime data have been protected.

System action: If any protected page of the cache isaccessed illegally, the JVM will end.


JVMSHRC274I Memory page protection disabled forcache

Explanation: The cache memory is not protectedagainst accidental corruption.

System action: The cache is not protected.


JVMSHRC277E To run "%s" utility on nonpersistentclass cache "%s", you must also use"nonpersistent" suboption

Explanation: The JVM cannot run the utility on thenonpersistent cache because it needs the nonpersistentsuboption set.


User response: Add the nonpersistent suboption andrestart the JVM.

JVMSHRC278I Note that utility "%s" cannot operateon incompatible class cache "%s". Pleaseuse a JVM of the correct level.

Explanation: The JVM cannot run the utility on thecache because it is not compatible.



JVMSHRC282I The page size of the operatingsystem is incompatible with this cache.Attempting to re-create the cache.

Explanation: The cache is divided up on page

boundaries. If there is a page size mismatch, the cacheis unusable.

System action: The JVM tries to remove and re-createthe cache.


JVMSHRC284E Cannot create a cache in readonlymode



User response: Remove the read-only option fromyour command-line and restart the JVM.

JVMSHRC285I Opened shared class persistent cache%1$s read-only

Explanation: Shared classes persistent cache %1$s hasbeen opened for read-only access. This message isproduced when -Xshareclasses:verbose is specified.



JVMSHRC286I Opened shared class cache %1$sread-only

Explanation: Shared classes cache %1$s has beenopened for read-only access. This message is producedwhen -Xshareclasses:verbose is specified.



JVMSHRC287E Persistent cache cannot be located ona networked file system. Either select"nonpersistent" or a different cacheDir.



User response: Use the "nonpersistent" option.

JVMSHRC291E Cannot allocate memory forhashtable entry inROMClassResourceManager






JVMSHRC292E Cannot enterROMClassResourceManager hashtablemutex




JVMSHRC296I Running with option "noCoreMmap"will mean that IBM will be unlikely toassist with any crashes as class data willbe missing from system dumps

Explanation: Without CORE_MMAP set to "yes", thesystem dumps do not contain the required class data.


User response: If possible, run with the environmentvariable CORE_MMAP set to "yes" and remove the"noCoreMmap" option.

JVMSHRC297I To use persistent shared class cacheson AIX, environment variableCORE_MMAP must be set to "yes"

Explanation: Without CORE_MMAP set to "yes", thesystem dumps will not contain the required class data.


User response: Set CORE_MMAP or use nonpersistentcaches.

JVMSHRC298E To run "%s" utility on persistentclass cache "%s", use the "persistent"suboption

Explanation: The JVM cannot run the utility on thepersistent cache, because the expected type isnonpersistent.


User response: Add the persistent suboption.

JVMSHRC318E Error recovery: destroying sharedmemory.



-Xshareclasses:nonfatal, in which case the JVMcontinues without using shared classes.


JVMSHRC319E Error recovery: closing sharedmemory.




JVMSHRC320E Error recovery: destroying sharedmemory semaphores.




JVMSHRC321E Error recovery: closing sharedmemory semaphores.




JVMSHRC322E Failed initializing semaphores forshared class cache. Warning: your cachemay be corrupt. If you experienceproblems using the shared cache, youmay need to destroy and re-create it.





IBM VM messages 47

JVMSHRC323E ERROR: Entering the shared classcache header mutex failed. Warning:your cache may be corrupt. If youexperience problems using the sharedcache, you may need to destroy andre-create it.




JVMSHRC324E ERROR: Exiting the shared classcache header mutex failed. Warning:your cache may be corrupt. If youexperience problems using the sharedcache, you may need to destroy andre-create it.




JVMSHRC327ESH_OSCachesysv::acquireWriteLock()call to j9shsem_wait has failed witherror %d.

Explanation: An error occurred waiting on asemaphore.



JVMSHRC328E System V IPC reported the followingerror '%s'

Explanation: An error occurred during the use ofSystem V IPC functions in the JVM.


User response: Contact your IBM servicerepresentative if this problem persists.

JVMSHRC329E SH_CompositeCacheImpl::enterReadWriteAreaMutex failed toacquire the string table mutex (returncode %d).

Explanation: An error has prevented updates to theshared class cache.

System action: The JVM attempts to continue.


JVMSHRC330ESH_CompositeCacheImpl::runExitCodefailed to acquire the write area mutex(return code %d).

Explanation: An error has prevented updates to theshared class cache during shutdown.

System action: The JVM attempts to continue theshutdown process.


JVMSHRC334E Error recovery failed: Destroyingshared memory has failed.



User response: Consult the diagnostic information inthe Java documentation.

JVMSHRC335E Error recovery failed: Destroyingshared semaphore has failed.






System action: The JVM ends, unless-Xshareclasses:nonfatal is specified, in which caseprocessing continues without using shared classes.





Explanation: This message shows the platform specificerror code and message related to the last error thatwas stored in the J9 Port layer. If the message does notindicate an error, there is probably no platform errorassociated with this port layer error.

System action: The JVM ends, unless-Xshareclasses:nonfatal is specified, in which caseprocessing continues without using shared classes.




System action: The JVM failed to clean up a System VIPC resource during error recovery.



Explanation: This message shows the platform specificerror code and message related to the last error thatwas stored in the J9 Port layer. If the message does notindicate an error, there is probably no platform errorassociated with this port layer error.

System action: The JVM failed to clean up a System VIPC resource during error recovery.


JVMSHRC340E Shared Cache CRC check failed.Stored CRC %1$x, calculated CRC %2$x

Explanation: This message shows the CRC valueswhen the cache startup CRC check fails

System action: The JVM attempts to re-create thecache before starting. If this process fails, the JVM ends,unless you have specified the nonfatal option with-Xshareclasses:nonfatal.


JVMSHRC361E Error while attaching to the sharedmemory during open/create


System action: The JVM ends, unless you have

specified the nonfatal option with-Xshareclasses:nonfatal, in which case the JVMcontinues without using shared classes.


JVMSHRC363E Cannot allocate api for sharedclasses in shrinit

Explanation: An error has occurred in shared classinitialization.



JVMSHRC364ESH_OSCachesysv::acquireWriteLock()call to j9shsem_wait on semid %d hasfailed with error %d.

Explanation: An error occurred while waiting on asemaphore.



JVMSHRC375E The cache name is too long whenthe user name is included. There are %dbytes left in this buffer, and your username is %d bytes.

Explanation: The system cannot include the usernamein the shared class cache name.



JVMSHRC404E Failed to get a directory for the cache

Explanation: The directory path requested is biggerthan the internal buffer space.

System action: The JVM ends, unless you havespecified the nonfatal option with-Xshareclasses:nonfatal, in which case the JVM


IBM VM messages 49

continues without using shared classes.

User response: Use a shorter path or cache name.

JVMSHRC405E Failed to create a directory for thecache

Explanation: The directory specified for the sharedcache could not be created.


User response: Make sure that you have the correctfile permissions for the controldir or cachedir chosen.

JVMSHRC428I Removed older generation of sharedclass cache "%s"

Explanation: The older generation of the shared classcache was successfully removed.



JVMSHRC429I Failed to remove older generation ofshared class cache "%s"

Explanation: The older generation of the shared classcache cannot be removed.


User response: Run with the option-Xshareclasses:verbose enabled to see other messagesthat might indicate why the cache is not removed.

JVMSHRC430I Failed to remove current generationof shared class cache "%s"

Explanation: The current generation of the sharedclass cache cannot be removed.


User response: Other messages might be issuedindicating the reason why the cache is not removed.Investigate these messages.

JVMSHRC434E Value=%d passed by -Xitsn option isoutside of the range of prime numbervalues supported by the VM. Supportedrange = 0 - %u

Explanation: The value specified for the -Xitsn optionis larger than the biggest prime number supported bythe JVM.


User response: Check the value specified by the-Xitsn option on the command line. The supportedrange is shown in the error message.

JVMSHRC435I -Xitsn%2$u uses %1$u bytes ofmemory, which is larger than the sharedclasses cache size of %3$u bytes

Explanation: The Shared Intern Table is part of theshared cache, therefore it cannot be larger than theshared cache.

System action: A new Shared Intern Table size iscalculated, proportional to the shared cache size.Processing continues.

User response: Check the shared cache size. Check theintern string table node count, which is specified by the-Xitsn option.

JVMSHRC436E Error acquiring shared class cachefile header write lock




JVMSHRC437E Error releasing shared class cachefile header read lock




JVMSHRC442E Shared cache "%s" is corrupt.Corruption code is %d. Corrupt value is0x%x. No new JVMs will be allowed toconnect to the cache. Existing JVMs cancontinue to function, but cannot updatethe cache.

Explanation: The shared class cache is corrupt.

System action: The JVM attempts to re-create thecache before starting. If this process fails, the JVM endsunless you have specified the nonfatal option with-Xshareclasses:nonfatal.

User response: Remove the shared class cache and tryagain. If the situation persists, contact your IBM servicerepresentative.



JVMSHRC443I Cache CRC is incorrect indicating acorrupt cache. Incorrect cache CRC:0x%x.




JVMSHRC444I Read corrupt data for cache entryheader 0x%p (invalid item length)




JVMSHRC445E Size of cache is too small to beuseful. Invalid cache size: 0x%x.




JVMSHRC446E Failed to acquire header write lockduring cache startup with error code:%d.




JVMSHRC447E Cache header eyecatcher is not valid.Address of eyecatcher string in cacheheader: 0x%p.




JVMSHRC448E Cache size field in cache header isnot valid. Cache size in cache header is:0x%x.




JVMSHRC449E Padding is non zero. Padding bytesin cache header are: %u.




JVMSHRC450E Data length field in cache header isnot valid. Data length in cache headeris: %u.




JVMSHRC451E Data start field in cache header isnot valid. Data start address in cacheheader is: 0x%p.




JVMSHRC457E Invalid cache name, the cache name"%.*s" contains only whitespace or isempty

Explanation: The specified shared class cache namecontains only white space characters, or no characters.


User response: Change the shared class cache name to


IBM VM messages 51

include non-whitespace characters, and start the JVMagain.

JVMSHRC461E -Xscminjitdata value should not begreater than -Xscmaxjitdata value

Explanation: The value for -Xscminjitdata cannot belarger than -Xscmaxjitdata.


User response: Change the value of -Xscminjitdata tobe 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

Explanation: The value specified for the-Xscminjitdata option cannot be greater than the valuefor the -Xscmx option.

System action: The value for the -Xscminjitdataoption is changed and the JVM continues.


JVMSHRC463I -Xscmaxjitdata value is greater than-Xscmx value, so it has been set tounlimited

Explanation: The value specified for the-Xscmaxjitdata option cannot be greater than the valuespecified for the -Xscmx option.

System action: The value of the -Xscmaxjitdataoption is changed automatically and the JVMcontinues.


JVMSHRC488E Total of -Xscminaot and-Xscminjitdata values should not begreater than available cache size

Explanation: The total value of the -Xscminaot and-Xscminjitdata options cannot be greater than theavailable cache size.


User response: Change the values of the -Xscminaotand -Xscminjitdata options so that the total of thesevalues does not exceed the available cache size.

JVMSHRC500E The debug area is corrupt becausefree space low address %p, is greaterthan free space high address %p




JVMSHRC501E The debug area is corrupt becausethe 'line number table data' low address%p, is greater than the high address %p




JVMSHRC502E The debug area is corrupt becausethe 'local variable table data' lowaddress %p, is greater than the highaddress %p




JVMSHRC503E The debug area is corrupt becausestoring 'line number table' %d bytes,and 'local variable table' %d bytes, willresult in a 'line number table data' highaddress of %p, which will be greaterthan the new 'local variable table data'low address %p




JVMSHRC504E Cache data start is null. data start:%p






JVMSHRC505E The debug area is corrupt becausefree space high address %p minus thefree space low address %p exceeds thedebug region size of %lu bytes




JVMSHRC506E The debug area is corrupt becauseits size of %lu is larger than the totalcache size of %u stored in the cacheheader




JVMSHRC508E Acquired a different semaphore thanpreviously used with this cache. oldsemid=%d, new semid=%d




JVMSHRC511I Composite cache has badinitialization flag value. The value ofccInitComplete is %lu

Explanation: The value of the initialization flag for thecomposite cache is incorrect.



JVMSHRC514E Invalid setting for cacheDirPermoption. This must be unix style filepermission in the range of 0700 - 0777 or1700 - 1777 (in octal representation).

Explanation: The value specified for the cacheDirPermparameter is not in a valid format.


User response: Run the command again with a valid

cacheDirPerm value. Use UNIX-style file permissions inoctal representation in the range of 0700 - 0777 or 1700- 1777.

JVMSHRC517E Unrecognised sub-option for optionprintallstats= . Use printallstats=help tosee available options.

Explanation: The suboption provided forprintallstats= is not recognized.


User response: Run printallstats=help to see a listof valid options and try again.

JVMSHRC547E Cannot allocate memory forcharacter array in shrinit

Explanation: An error has occurred when parsingshared class command-line options.



JVMSHRC549E -Xshareclasses:checkStringTableResetmay fail. String table is not largeenough. It needs to be more than to OSpage size. Table size = %d, Page size =%d




JVMSHRC550E ROUND_TO_PAGE_SIZE runtimeflag is missing.-Xshareclasses:checkStringTableResetrequires string table be rounded to pagesize.





IBM VM messages 53

JVMSHRC551E Cache \"%s\" is marked as full.Failed to allocate block size = %d.

Explanation: The JVM is unable to store the requesteddata in the cache because the cache is marked as full.



JVMSHRC552E Cannot allocate requested block sizefor cache \"%s\". Available bytes = %d,Requested bytes = %d

Explanation: There is not enough free memory in theshared class cache to store the amount of datarequested.



JVMSHRC557E Unrecognised sub-option for optionprintstats= . Use printstats=help to seeavailable options.

Explanation: The suboption provided for printstats=is not recognized.


User response: Run printstats=help for a list of validoptions and try again.

JVMSHRC559E Failed to create a directory \"%s\"for the shared class cache

Explanation: The directory specified for the sharedclass cache could not be created.

System action: The JVM ends, unless you specifiedthe nonfatal option with -Xshareclasses:nonfatal, inwhich case the JVM continues without using sharedclasses.

User response: Make sure that you have the rightpermissions for the controldir or cachedir chosen.

JVMSHRC560E Internal cache name is not proper.




JVMSHRC561E Failed to initialize the shared classescache, there is not enough space in thefile system. Available free disk spacebytes = %lld, requested bytes = %lld.



User response: Increase the amount of space availablein your file system and try again.

JVMSHRC562I Read corrupt data for cache entryheader 0x%p (invalid item length of %ubytes)




JVMSHRC572E Opening a Realtime cache, which isnot compatible with this JVM, use the-Xrealtime JVM option to access thiscache

Explanation: A standard JVM is accessing a real-timecache.


User response: To use a real-time JVM, specify the-Xrealtime option. If you do not want to use areal-time JVM, use a different cache name.

JVMSHRC590E The "enableBCI" sub-option wasspecified but the existing cache was notcreated with the "enableBCI"sub-option.

Explanation: An error occurred when processingshared class options.


User response: Remove the enableBCI suboption,which is incompatible with this shared classes cacheand try again.



JVMSHRC594E The-Xshareclasses:cacheRetransformedsub-option is incompatible with ashared cache created with the enableBCIsub-option



User response: Remove the cacheRetransformedsuboption, which is incompatible with this sharedclasses cache and try again.

JVMSHRC595E Command-line options \"%s\" and\"%s\" are incompatible

Explanation: The JVM found incompatible suboptionswhen processing the shared class options.


User response: Remove one of the incompatible-Xshareclasses suboptions and try again.

JVMSHRC598E The raw class data area is corruptbecause its size of %lu is larger than thetotal cache size of %lu.




JVMSHRC599E The raw class data area free space iscorrupt ('free space start'=%p, 'free spaceend'=%p, 'free size'=%lu bytes)




JVMSHRC600E The raw class data area is corruptbecause storing %u bytes will exceedthe available area free space ('free spacestart'=%p, 'free space end'=%p).




JVMSHRC605E The memory size for \"%s\" is toolarge, or specifies units other than'K','M', or 'G'.

Explanation: The memory size is too large, or specifiesunits other than K, M, or G.


User response: Correct or remove the incorrectcommand-line option and try again.

JVMSHRC611E The "disableBCI" sub-option isspecified but the existing cache wascreated with the "enableBCI"sub-option.



User response: Remove the disableBCI suboption,which is incompatible with this shared classes cacheand try again.

JVMSHRC613E An error has occurred while openingsemaphore. Control file is found to becorrupt.



User response: Check any messages that follow, whichmight indicate the problem. For further assistance,contact your IBM service representative.

JVMSHRC614E An error has occurred while openingsemaphore. Mismatch in semaphore ID.





IBM VM messages 55

JVMSHRC615E An error has occurred while openingsemaphore. Mismatch in semaphore key.




JVMSHRC616E An error has occurred while openingsemaphore. Mismatch in number ofsemaphores in the semaphore set.




JVMSHRC617E An error has occurred while openingsemaphore. Semaphore marker notfound in the semaphore set.




JVMSHRC618E Semaphore control file is notreadable.

Explanation: The JVM cannot read the semaphorecontrol file.


User response: Check that the semaphore control filehas read/write permissions and try again. If thesituation persists, contact your IBM servicerepresentative.

JVMSHRC619E Semaphore control file is read only.

Explanation: The semaphore control file has only readpermission.


User response: Check that the semaphore control filehas read/write permissions and try again. If thesituation persists, contact your IBM servicerepresentative.

JVMSHRC620E Error opening shared memoryregion. Control file is found to becorrupt.




JVMSHRC621E Error opening shared memoryregion. Mismatch in shared memory ID.




JVMSHRC622E Error opening shared memoryregion. Mismatch in shared memorykey.






JVMSHRC623E Error opening shared memoryregion. Check for group id failed.




JVMSHRC624E Error opening shared memoryregion. Check for user id failed.




JVMSHRC625E Error opening shared memoryregion. Check for shared memory sizefailed.




JVMSHRC626I Recreation of shared memory controlfile is not allowed when retrievingcache stats.

Explanation: This message provides information only.



JVMSHRC627I Recreation of shared memory controlfile is not allowed when running inread-only mode.

Explanation: This message is for information only.



JVMSHRC628E Shared memory control file is notreadable.

Explanation: The JVM cannot read the shared memorycontrol file.


User response: Check that the shared memory controlfile has read/write permissions and try again. If thesituation persists, contact your IBM servicerepresentative.

JVMSHRC629E Shared memory control file is readonly.

Explanation: The shared memory control file has onlyread permission.


User response: Check that the shared memory controlfile has read/write permissions and try again. If thesituation persists, contact your IBM servicerepresentative.

JVMSHRC630I Space is full for storingnon-AOT/non-JIT data, such as classes,in shared cache \"%s\".

Explanation: The available space for storingnon-AOT/non-JIT data, such as classes, in the namedshared classes cache is full. No further data can beadded.

System action: The JVM continues. The named sharedcache is still operational and continues to provideincreased performance for loading the classes that arestored. However, classes that are not contained in thecache are always loaded from their source.

User response: To gain the full benefit of sharedclasses, delete and re-create the named cache,specifying a larger shared class cache size with the-Xscmx parameter.


IBM VM messages 57

JVMSHRC631I Space reserved for AOT data inshared cache \"%s\" is full. Use-Xscminaot to increase space reservedfor AOT data.

Explanation: The available space for storing AOT datain the named shared classes cache is full. No furtherAOT data can be added.

System action: The JVM continues. The named sharedcache is still operational and continues to provideincreased performance for loading the classes that arestored. However, no more AOT compiled methods canbe added to the cache.

User response: To allow the JVM to store more AOTcompiled methods into the shared classes cache,increase the value that is specified by the -Xscminaotoption.

JVMSHRC632I Space reserved for JIT data in sharedcache \"%s\" is full. Use -Xscminjitdatato increase space reserved for JIT data.

Explanation: The available space for storing JIT datain the named shared classes cache is full. No further JITdata can be added.

System action: The JVM continues. The named sharedcache is still operational and continues to provideincreased performance for loading the classes that arestored. However, no more JIT-related data can be addedto the cache.

User response: To allow the JVM to store moreJIT-related data into the shared classes cache, increasethe value that is specified by the -Xscminjitdataoption.

JVMSHRC633E The"-XX:+StoreIntermediateClassfile" optionwas specified but the existing cache wasnot created with the"-XX:+StoreIntermediateClassfile"option.



User response: Remove the incompatible option andtry again.

JVMSHRC634E The "-XX:-StoreIntermediateClassfile" option wasspecified but the existing cache wascreated with the"-XX:+StoreIntermediateClassfile"option.



User response: Remove the option-XX:-StoreIntermediateClassfile from the commandline to use the existing shared classes cache.

JVMSHRC637E The-Xshareclasses:cacheRetransformedsub-option is incompatible with anexisting BCI enabled shared cache.



User response: Remove the incompatible suboptionand try again.

JVMSHRC638I Cache creation with thecacheRetransformed option forcesdisableBCI mode.

Explanation: When you use the option-Xshareclasses:cacheRetransformed, the shared cachethat is created does not support Byte CodeInstrumentation (BCI). Using this option is equivalentto setting -Xshareclasses:disableBCI.


User response: No action is required. This message isfor information only.

JVMSHRC639E Only shared cache utility optionscan be used in combination with -Xmt.Put other shared cache options in thejavad.options file.

Explanation: Shared cache runtime options must bespecified in the javad.options file. The javad processmust be restarted before any shared classes cacheoptions take effect.


User response: Replace the incompatible-Xshareclasses option with a -Xshareclasses utilityoption and try again.



JVMSHRC646E The JVM could not check thepermissions of the semaphore setassociated with the shared cache.

Explanation: An error occurred during shared classesprocessing.



JVMSHRC647E The JVM detected effective user idof the process is the owner but not thecreator of semaphore set associated withthe shared cache. JVM will not attach tothe shared cache to prevent accessingunintended shared cache.



User response: Delete the existing shared classes cacheand restart to create a new shared classes cache.

JVMSHRC648E The JVM is not configured to accesssemaphore set associated with existingnon-persistent shared class cache. Toattach to the non-persistent shared classcache, use 'groupAccess' sub-option.



User response: Modify the existing -Xshareclassesoption to add a groupAccess sub option and start again.

JVMSHRC649E The JVM does not permit access tothe shared cache's semaphore set createdand owned by another user not in itsgroup.



User response: Specify a different cache name or

directory to avoid a conflict with the existing sharedclasses cache. This cache was created by another userthat is not in the same group.

JVMSHRC650E The JVM could not check thepermissions of the shared memoryassociated with the shared cache.




JVMSHRC651E The JVM detected effective user idof the process is the owner but not thecreator of shared memory associatedwith the shared cache. JVM will notattach to the shared cache to preventaccessing unintended shared cache.



User response: Delete the existing shared classes cacheand restart to create a new shared classes cache.

JVMSHRC652E The JVM is not configured to accessshared memory associated with existingnon-persistent shared class cache. Toattach to the non-persistent shared classcache, use 'groupAccess' sub-option.



User response: Modify the existing -Xshareclassesoption to add the groupAccess sub option and tryagain.

JVMSHRC653E The JVM is not configured to accessshared memory associated with existingnon-persistent shared class cache. Toattach to the non-persistent shared classcache, use 'groupAccess' and 'readonly'sub-option.


IBM VM messages 59



User response: Modify the existing -Xshareclassesoption to add the groupAccess and readOnly suboptions and try again.

JVMSHRC654E The JVM does not permit access tothe shared cache's shared memoryregion created and owned by anotheruser not in its group.



User response: Specify a different cache name ordirectory to avoid a conflict with an existing sharedclasses cache. This cache was created by another userthat is not in the same group.

JVMSHRC656E The JVM is not configured to accessshared cache file. To attach to the sharedclass cache, use 'groupAccess' suboption.

Explanation: An error occurred within shared classesprocessing.

System action: The Java VM ends, unless youspecified the nonfatal option by using the-Xshareclasses:nonfatal parameter, in which case theJava VM continues without using shared classes.

User response: Modify the existing -Xshareclasses:option to add the groupAccess suboption, then restartthe Java VM.

JVMSHRC657E The JVM does not permit access tothe shared cache file because the JVMprocess's user ID and group ID aredifferent from the shared cache fileowner's user ID and group ID, and theJVM process's user ID does not belongto the shared cache file owner's group.



User response: Specify a different cache name ordirectory to avoid conflict with an existing shared cache

that is created by another user who is in a differentgroup.

JVMSHRC658E The JVM could not check thepermissions of the shared cache file.




JVMSHRC659E An error has occurred while openingshared memory

Explanation: An error occurred in shared classprocessing. Further messages might follow, providingmore detail.



JVMSHRC660E The JVM failed to associatesemaphore set id=%d with the sharedclass cache.

Explanation: This message displays the ID of thesemaphore set that the Java VM failed to associate withthe shared class cache due to an error that is indicatedin previous messages.

System action: The Java VM continues.

User response: Use the ipcrm command to remove thesemaphore set that is indicated in the error message, ifit still exists and is not in use.

JVMSHRC661E The JVM failed to associate sharedmemory id=%d with the shared classcache.

Explanation: This message displays the ID of theshared memory that the Java VM failed to associatewith the shared class cache due to an error that isindicated in previous messages.


User response: Use the ipcrm command to remove theshared memory that is indicated in the error message,if it still exists and is not in use.



JVMSHRC662E Error recovery: destroyed semaphoreset associated with shared class cache.

Explanation: An error occurred in shared classprocessing, and as part of error recovery the Java VMdestroyed the semaphore set that was associated withthe shared class cache.

System action: The Java VM detected an error duringshared class processing and destroyed the semaphoreset in an attempt to recover.


JVMSHRC663I Error recovery: destroyed semaphoreset with id=%d associated with sharedclass cache.

Explanation: An error occurred in shared classprocessing, and as part of error recovery the Java VMdestroyed the semaphore set that as associated with theshared class cache.

System action: The Java VM detected an error duringshared class processing and destroyed the semaphoreset in an attempt to recover.


JVMSHRC664E Error recovery failed: Failed todestroy the semaphore set withsemid=%d associated with shared classcache. Only creator or owner or userwith administrative privileges candestroy the semaphore set.

Explanation: An error occurred in shared classprocessing. The Java virtual machine's attempt todestroy the semaphore set as part of error recoveryfailed because the operating system allows only thecreator, owner, or a user with administrative privilegesto destroy the semaphore set.



JVMSHRC665E Error recovery failed: Failed todestroy the semaphore set withsemid=%d associated with shared classcache.

Explanation: An error occurred in shared classprocessing. The Java virtual machine's attempt todestroy the semaphore set as part of error recoveryfailed.

System action: The Java VM ends, unless youspecified the nonfatal option by using the

-Xshareclasses:nonfatal parameter, in which case theJava VM continues without using shared classes.


JVMSHRC666E Error recovery: destroyed sharedmemory associated with shared classcache.

Explanation: An error occurred in shared classprocessing and as part of error recovery the Java VMdestroyed the shared memory that was associated withthe shared class cache.

System action: The Java VM detected an error duringshared class processing and destroyed the sharedmemory in an attempt to recover.


JVMSHRC667I Error recovery: destroyed sharedmemory with id=%d associated withshared class cache.

Explanation: An error occurred in shared classprocessing and as part of error recovery the Java VMdestroyed the shared memory that was associated withthe shared class cache.

System action: The Java VM detected an error duringshared class processing and destroyed the sharedmemory in an attempt to recover.


JVMSHRC668E Error recovery failed: Failed todestroy the shared memory withshmid=%d associated with shared classcache. Only creator or owner or userwith administrative privileges candestroy the shared memory.

Explanation: An error occurred in shared classprocessing. The Java virtual machine's attempt todestroy the shared memory as part of error recoveryfailed because the operating system allows only thecreator, owner, or a user with administrative privilegesto destroy the shared memory.




IBM VM messages 61

JVMSHRC669E Error recovery failed: Failed todestroy the shared memory withshmid=%d associated with shared classcache.

Explanation: An error occurred in shared classprocessing. The Java virtual machine's attempt todestroy the shared memory as part of error recoveryfailed.



JVMSHRC670I Error recovery: attempting to useshared cache in readonly mode if theshared memory region exists, inresponse to "-Xshareclasses:nonfatal"option.

Explanation: An error occurred in shared classprocessing. The presence of the-Xshareclasses:nonfatal option causes the Java VM toattempt to use the shared cache in read-only mode.

System action: The Java VM attempts to attach to theshared memory segment of the shared class cache inread-only mode if it exists.


JVMSHRC671E User is not allowed to destroy thesemaphore set with semid=%d. Onlycreator or owner or user withadministrative privileges can destroy thesemaphore set.

Explanation: The operating system allows only thecreator, owner, or a user with administrative privilegesto destroy the semaphore set.



JVMSHRC672E Failed to destroy semaphore setassociated with shared class cache.

Explanation: An error occurred while destroying thesemaphore set that is associated with the shared classcache.



JVMSHRC673E Failed to destroy semaphore set withsemid=%d associated with shared classcache.

Explanation: An error occurred while destroying thesemaphore set that is associated with the shared classcache.



JVMSHRC674E User is not allowed to destroy theshared memory with shmid=%d. Onlycreator or owner or user withadministrative privileges can destroy theshared memory.

Explanation: The operating system allows only thecreator, owner, or a user with administrative privilegesto destroy the shared memory.



JVMSHRC675E Failed to destroy shared memoryassociated with shared class cache.

Explanation: An error occurred while destroying theshared memory that is associated with the shared classcache.



JVMSHRC676E Failed to destroy shared memorywith shmid=%d associated with sharedclass cache.

Explanation: An error occurred while destroying theshared memory that is associated with the shared classcache.




Explanation: This message shows the last portableerror code that is stored in the J9 Port layer. Thismessage indicates the last error that was encountered.

System action: The Java VM failed to clean up aSystem V IPC resource.





Explanation: This message shows the platform-specificerror code and message that is related to the last errorthat was stored in the J9 Port layer.

System action: The Java VM failed to clean up aSystem V IPC resource.


JVMSHRC679E Error recovery failure: Failed toremove the semaphore set control file%s associated with shared class cache.

Explanation: An error occurred during shared classprocessing. The Java virtual machine's attempt toremove the control file as part of error recovery failed.


User response: If the Java VM fails to start, removethe control files manually.

JVMSHRC680E Error recovery failure: Failed toremove the semaphore set control file%s associated with shared class cache.

Explanation: An error occurred during shared classprocessing. The Java virtual machine's attempt toremove the control file as part of error recovery failed.


User response: If the Java VM fails to start, removethe control files manually.

JVMSHRC681E System limit for maximum numberof semaphores or the system widemaximum number of semaphores hasbeen reached.

Explanation: The Java VM failed to create a newsemaphore set for the shared class cache because thesystem limit was reached.

System action: If you specified the-Xshareclasses:nonfatal option, the Java VM tries touse an existing shared class cache in read-only mode. Ifthe cache does not exist, the Java VM continueswithout the shared class cache. If you did not specifythe -Xshareclasses:nonfatal option, the Java VM ends.

User response: Contact your system administrator toincrease the system limit on semaphore resources, orclean up any unused semaphore sets in the system thenrestart the Java VM.

JVMSHRC682E System limit for maximum numberof shared memory regions orsystem-wide limit on memory allocatedto shared memory regions has beenreached.

Explanation: The Java VM failed to create a newshared memory region for the shared class cachebecause the system limit was reached.

System action: If you specified the-Xshareclasses:nonfatal option the Java VM continueswithout the shared class cache, otherwise the Java VMends.

User response: Contact your system administrator toincrease the system limit on shared memory resources,or clean up any unused shared memory regions in thesystem then restart the Java VM.

JVMSHRC683E System limit on the total number ofopen files has been reached.

Explanation: The Java VM failed to create a newcontrol file for the shared class cache because thesystem limit was reached.

System action: If you specified the-Xshareclasses:nonfatal option and this erroroccurred when creating a semaphore control file, theJava VM tries to use an existing shared class cache inread-only mode. If the cache does not exist, the JavaVM continues without the shared class cache. If thiserror occurred when creating a shared memory controlfile, the Java VM continues without the shared classcache. If you did not specify the-Xshareclasses:nonfatal option, the Java VM ends.

User response: Contact your system administrator toincrease the system limit on maximum open files, orclose any unused files then restart the Java VM.

JVMSHRC684E An error has occurred while openingsemaphore. Control file could not belocked.

Explanation: An error has occurred in shared classprocessing. Further messages might follow, providingmore detail.

System action: If you specified the-Xshareclasses:nonfatal option, the Java VM tries touse an existing shared class cache in read-only mode. Ifthe cache does not exist, the Java VM continueswithout the shared class cache. If you did not specifythe -Xshareclasses:nonfatal option, the Java VM ends.



IBM VM messages 63

JVMSHRC685E An error has occurred while openingshared memory. Control file could notbe locked.

Explanation: An error occurred in shared classprocessing. Further messages might follow, providingmore detail.

System action: If you specified the-Xshareclasses:nonfatal option, the Java VMcontinues without the shared class cache, otherwise theJava VM ends.


JVMSHRC686I Failed to startup shared class cache.Continue without using it as-Xshareclasses:nonfatal is specified

Explanation: An error occurred during shared classcache start. You specified the -Xshareclasses:nonfataloption, so the Java VM will continue without using theshared class cache.

System action: The Java VM continues without theshared class cache.

User response: Contact your IBM servicerepresentative to understand why the shared classcache could not be started. Previous error messagesmight indicate the reason.

JVMSHRC687E A new shared class cache cannot becreated when running with-Xshareclasses:readonly option

Explanation: An error occurred during shared classcache start. The Java VM cannot create a new sharedclass cache when the -Xshareclasses:readonly optionis specified.

System action: The Java VM ends unless you specifiedthe -Xshareclasses:nonfatal option, in which case theJava VM continues without the shared class cache.

User response: Remove the readonly suboption fromthe -Xshareclasses option, then restart the Java VM.The readonly suboption is useful only if the sharedclass cache already exists.

JVMSHRC697E Failed to get a directory for theshared cache

Explanation: The directory path requested is biggerthan the internal buffer space.

System action: The JVM fails to complete theoperation of creating a snapshot of the non-persistentshared cache.

User response: Use a shorter directory path or cachename.

JVMSHRC698I Non-persistent shared cache \"%s\"has been restored successfully from thesnapshot

Explanation: The non-persistent shared cache issuccessfully restored from the snapshot.


User response: No action is required. This message isonly for information.

JVMSHRC699E Failed to restore the non-persistentshared cache \"%s\" from the snapshot

Explanation: An error occurred when the JVMattempted to restore the non-persistent cache.

System action: The JVM fails to complete theoperation of restoring a non-persistent shared cachefrom the snapshot.

User response: Other messages might indicate thereason why the cache cannot be restored from thesnapshot.

JVMSHRC700I Snapshot of non-persistent sharedcache \"%s\" has been created

Explanation: The JVM successfully created thesnapshot of an existing non-persistent shared cache.



JVMSHRC701E Failed to create a snapshot ofnon-persistent shared cache \"%s\"

Explanation: An error occurred when the JVMattempted to create a snapshot of a non-persistentshared cache.

System action: The JVM fails to complete theoperation of creating the snapshot of a non-persistentshared cache.

User response: Other messages might indicate thereason why the snapshot failed to be created.

JVMSHRC702I Failed to get a directory for theshared cache snapshot

Explanation: The directory path that is requested isbigger than the internal buffer space.

System action: The JVM fails to complete the requiredoperation on the shared cache snapshot.

User response: Use a shorter directory path or cachename.



JVMSHRC703E Failed to open the shared cachesnapshot file \"%s\"

Explanation: An error occurs when the JVM attemptsto open the shared cache snapshot file.

System action: The JVM fails to complete the requiredoperation on the shared cache snapshot file.

User response: Previous error messages might indicatethe reason for this failure. If this is not the case, contactyour IBM service representative.


Explanation: This message shows the last portableerror code that was encountered.

System action: The JVM fails to complete the requiredoperation on the shared cache snapshot.

User response: A later message might provide moreinformation about this error code and the action thatcan be taken. If this is not the case, contact your IBMservice representative.


Explanation: This message shows the platform-specificerror code and message that relates to the last portableerror code that was encountered. This code mightindicate a success message, in which case there isprobably no associated platform error.


User response: If an appropriate action cannot bedetermined from the error message, contact your IBMservice representative.

JVMSHRC706E Failed to acquire file lock on theshared cache snapshot file

Explanation: An error occurs when the JVM attemptsto acquire a file lock on the shared cache snapshot file.


User response: Previous error messages might indicatethe reason for the failure. If not, contact your IBMservice representative.

JVMSHRC707E Failed to acquire the mutex of cache\"%s\"

Explanation: An error occurs when the JVM attemptsto acquire a cache mutex.


User response: Verify that the system has enough

native resources for the JVM. If the problem persists,contact your IBM service representative.

JVMSHRC708E Failed to truncate the existingnon-persistent shared cache snapshotfile \"%s\"

Explanation: An error occurs when the JVM attemptsto truncate the non-persistent shared cache snapshotfile.

System action: The JVM fails to complete theoperation.

User response: Previous error messages might indicatethe reason. Contact your IBM service representative.

JVMSHRC710E Failed to write into thenon-persistent shared cache snapshotfile \"%s\"

Explanation: An error occurs when the JVM attemptsto write to a non-persistent shared cache snapshot file.

System action: The JVM fails to complete theoperation.

User response: Previous error messages might indicatethe reason for the failure, for example, the disk mightbe full. If this is not the case, contact your IBM servicerepresentative.

JVMSHRC711E Failed to reposition the offset of thefile descriptor in the non-persistentshared cache snapshot file \"%s\"

Explanation: An error occurs when the JVM attemptsto reposition the offset of the file descriptor in thenon-persistent shared cache snapshot file.


User response: Previous error messages might indicatethe reason for the failure. If this is not the case, contactyour IBM service representative.

JVMSHRC713E Failed to get the length of the sharedcache snapshot file \"%s\"

Explanation: An error occurs when the JVM attemptsto obtain the length of the snapshot file.

System action: The JVM fails to complete theoperation of destroying a shared cache snapshot.



IBM VM messages 65

JVMSHRC714I No shared cache snapshots available

Explanation: There are no snapshots present in thecacheDir that can be processed by the commandrequested.



JVMSHRC715I Removed older generation of sharedcache snapshot \"%s\"

Explanation: The JVM successfully removes an oldergeneration of the indicated shared cache snapshot.

System action: JVM processing continues.


JVMSHRC716I Failed to remove older generation ofshared cache snapshot \"%s\"

Explanation: The JVM is unable to remove the oldergeneration of the indicated shared cache snapshot.

System action: JVM processing continues.


JVMSHRC717I Failed to remove current generationof shared cache snapshot \"%s\"

Explanation: The JVM is unable to remove the currentgeneration of the indicated shared cache snapshot.

System action: The JVM fails to remove the snapshotof a shared cache.

User response: Previous error messages might indicatethe reason for this failure. If this is not the case, contactyour IBM service representative.

JVMSHRC718E Shared cache snapshot does not exist

Explanation: The JVM attempts to remove a sharedcache snapshot that does not exist.



JVMSHRC719I Shared cache snapshot \"%s\" isdestroyed

Explanation: The named shared cache snapshot isremoved, as requested.



JVMSHRC720I Recreation of shared memory controlfile is not allowed when creating asnapshot of the cache

Explanation: The JVM cannot create a snapshot of theshared cache because a valid shared cache does notexist.



JVMSHRC721E The JVM is not configured to accessthe non-persistent shared cachesnapshot file \"%s\". To open the file,use 'groupAccess' sub-option.


System action: The JVM fails to restore anon-persistent shared cache from the snapshot.

User response: Modify your -Xshareclasses: optionto add the groupAccess suboption and try again. Thesnapshot might have been created by another user inthe same group as the current user.

JVMSHRC722E The JVM does not permit access tothe shared cache snapshot file \"%s\"because the JVM process's user ID andgroup ID are different from the sharedcache snapshot file owner's user ID andgroup ID, and the JVM process's userID does not belong to the shared cachesnapshot file owner's group.



User response: Specify a different cache name ordirectory. This action avoids a conflict with an existingshared cache snapshot that was created by another userthat is not in the same group.

JVMSHRC723E The JVM could not check thepermissions of the shared cachesnapshot file \"%s\"






JVMSHRC724E Shared cache snapshot file \"%s\"does not exist

Explanation: The shared cache snapshot file is notfound on the disk.

System action: The JVM fails to restore a shared cachefrom the snapshot.


JVMSHRC725E The length of the non-persistentshared cache snapshot file \"%s\" isinvalid. The length of the file is %lldbytes. A valid snapshot file is at least%d bytes and at most %lld bytes.

Explanation: The length of the file is not valid


User response: Check that the file is a valid sharedcache snapshot file.

JVMSHRC726E Non-persistent shared cache \"%s\"already exists. It cannot be restoredfrom the snapshot.

Explanation: Only a new non-persistent shared cachecan be restored from a snapshot.


User response: Check that the non-persistent cachedoes not exist before restoring the cache from thesnapshot.

JVMSHRC727E An error has occurred in creating thenew non-persistent shared cache

Explanation: The JVM cannot start the new cache.


User response: Verify that the system has enoughnative resources for the JVM. If the problem persists,contact your IBM service representative.

JVMSHRC728E Failed to read the non-persistentshared cache snapshot file \"%s\"

Explanation: An error occurs when reading thenon-persistent shared cache snapshot file.


User response: Previous error messages might indicatethe reason for the error. If this is not the case, contactyour IBM service representative.

JVMSHRC729E The snapshot was created by adifferent JVM build and doesn't matchthe running JVM

Explanation: An error occurs when the JVM attemptsto start the restored cache. The build ID in the snapshotis different from the ID of the current JVM.


User response: Use a JVM that matches the snapshot,or destroy the snapshot.

JVMSHRC730I The JVM has created shared cachewith '-Xshareclasses:restrictClasspaths'option. Subsequent JVM invocationswill not be able to store classpaths intothe shared cache

Explanation: When the-Xshareclasses:restrictClasspaths option is used,subsequent JVMs cannot store class paths into theshared cache unless they are running with the-Xshareclasses:allowClasspaths option.



JVMSHRC731I The JVM has ignored'-Xshareclasses:restrictClasspaths' optionas the existing shared cache was createdwithout'-Xshareclasses:restrictClasspaths' option

Explanation: -Xshareclasses:restrictClasspaths isapplicable only when the JVM is initializing a newshared cache.


User response: For this option to be effective youmust remove the existing shared cache and restart theJVM.

JVMSHRC732I The JVM can store classpaths intothe shared cache created with'-Xshareclasses:restrictClasspaths' option

Explanation: The JVM can store class paths into theshared cache because the-Xshareclasses:allowClasspaths option is alsospecified.




IBM VM messages 67

JVMSHRC733I The JVM cannot store classpaths intothe shared cache, since the cache wascreated with the'-Xshareclasses:restrictClasspaths' option

Explanation: The JVM attaches to an existing sharedcache created with the-Xshareclasses:restrictClasspaths option.



JVMSHRC735I Use a %d-bit JVM to perform therequested operation on the %d-bitshared cache \"%s\" as the %d-bit JVMcannot verify that the shared memorywas created by the JVM

Explanation: The JVM cannot verify the size of theshared cache. The requested operation is not carriedout to avoid accidental access to shared memory ofanother application.


User response: You must use a JVM that has the sameaddress mode as the shared cache to carry out therequested operation.

JVMSHRC743E Invalid method specification(s) foroption \"%s\"

Explanation: The method specification provided wasnot recognized.


User response: Specify a valid method specificationand try again.

JVMSHRC744I Invalidated the %d AOT method(s)

Explanation: Successfully found the AOT method(s)and performed the required operation.



JVMSHRC745I Revalidated the %d AOT method(s)

Explanation: Successfully found the AOT method andperformed the required operation.



JVMSHRC746I Found the %d AOT method(s)

Explanation: Successfully found the AOT method andperformed the required operation.



JVMSHRC747E Failed to invalidate the AOTmethod(s)

Explanation: An error occurred while performing therequested operation on the AOT method.


User response: Previous messages might indicate thereason for the error. Contact your IBM servicerepresentative.

JVMSHRC748E Failed to revalidate the AOTmethod(s)

Explanation: An error occurred while attempting therequested operation on the AOT method.


User response: Previous messages might indicate thereason for this error. Contact your IBM servicerepresentative.

JVMSHRC749E Failed to find the AOT method(s)

Explanation: An error occurred while attempting therequested operation on the AOT method.


User response: Previous messages might indicate thereason for this error. Contact your IBM servicerepresentative.

JVMSHRC750I No AOT methods match the methodspecification(s)

Explanation: There are no AOT methods in the cachethat match the method specification.



JVMSHRC751E Failed to parse the methodspecifications. No more than %d methodspecifications are allowed.

Explanation: Too many method specifications arespecified.


User response: Reduce the number of methodspecifications and try again. The maximum limit is 64.



JVMSHRC752E Failed to parse the methodspecification(s)

Explanation: An error occurred while parsing themethod specification.


User response: Correct the format of the methodspecification and try again.

JVMSHRC753E Failed to get the cache write mutex

Explanation: An error occurred when acquiring thewrite mutex of the cache.


User response: Verify that the system has enoughnative resources for the JVM to work properly. If theproblem persists, contact your IBM servicerepresentative.

JVMSHRC754I Recreation of shared memory controlfile is not allowed.

Explanation: The required operation cannot completebecause a valid shared cache does not exist.


User response: None required.

JVMSHRC762E Error getting stats of the shared classcache file when verifying its groupaccess permission.

Explanation: An error has occurred during sharedclasses processing.



JVMSHRC765I Memory page protection on runtimedata, string read-write data and partiallyfilled pages is successfully enabled

Explanation: Memory pages of the cache that containruntime data, string read/write data, and partiallyfilled pages, are protected.

System action: If any protected page of the cache isaccessed illegally, the Java VM crashes.

User response: No action required.

JVMSHRC769I Memory page protection on runtimedata and partially filled pages issuccessfully enabled

Explanation: Memory pages of the cache that containruntime data and partially filled pages are protected.



JVMSHRC773I Memory page protection on runtimedata and string read-write data issuccessfully enabled

Explanation: Memory pages of the cache that containruntime data and string read/write data are protected.



JVMSHRC777I Memory page protection on runtimedata is successfully enabled

Explanation: Memory pages of the cache that containruntime data are protected.

System action: If any protected page of the cache isaccessed illegally, the JVM will crash.


JVMSHRC781I The JVM has enabled shared cachepartial page protection as the existingshared cache was created with partialpage protection enabled.

Explanation: The Java VM is attached to an existingshared cache, which was created with partial protectionenabled. Any Java VM attaching to an existing sharedcache enables partial page protection, irrespective ofcommand line options.

System action: The Java VM protects both partiallyfilled pages and full pages in the shared class cache.

User response: Remove the existing shared cache andrestart the Java VM. This action makes the-Xshareclasses:mprotect=nopartialpages or-Xshareclasses:mprotect=none option effective.

JVMSHRC782I The JVM has disabled protectingpartially filled pages. If-Xshareclasses:mprotect=onfind isspecified, it is also ignored.

Explanation: The Java VM is attached to an existingshared cache that was created with the-Xshareclasses:mprotect=nopartialpages option. AnyJVM attaching to this type of cache disables partialpage protection, irrespective of command line options.


IBM VM messages 69

System action: The Java VM protects only full pagesin the shared class cache. Partially filled pages are notprotected.

User response: Remove the existing shared cache andrestart the Java VM. By default, the Java VM protectspartially filled pages in the shared cache after thestartup phase.

JVMSHRC816I The JVM has enabled shared cachepartial page protection on startup as theexisting shared cache was created withpartial page protection enabled duringstartup.

Explanation: The Java VM is attached to an existingshared cache that was created with partial protectionenabled during startup. Any Java VM attaching to thistype of cache enables partial page protection duringstartup, irrespective of command line options.

System action: The Java VM starts protecting partiallyfilled pages during startup.


JVMSHRC817I The JVM has not enabled protectingshared cache partially filled pages onstartup.

Explanation: The Java VM is attached to an existingshared cache that was not created with the-Xshareclasses:mprotectOnStartup option. Any JavaVM attaching to this type of cache enables partial pageprotection after the startup phase.

System action: The Java VM protects partially filledpages when the startup phase is complete.

User response: Remove the existing shared cache andrestart the Java VM with the-Xshareclasses:mprotectOnStartup option.

JVMSHRC818I Compressed references persistentshared cache \"%1$s\" has beendestroyed. Use option-Xnocompressedrefs if you want todestroy a non-compressed referencescache.

Explanation: The compressed references cache '1$' isremoved as requested.

System action: The Java VM stops when theprocessing is complete.


JVMSHRC823I Non-compressed references persistentshared cache \"%1$s\" has beendestroyed. Use option -Xcompressedrefsif you want to destroy a compressedreferences cache.

Explanation: The non-compressed references cache '1$'is destroyed as requested.

System action: The Java VM stops when theprocessing is complete.


JVMSHRC828I Compressed references shared cache\"%s\" is destroyed. Use option-Xnocompressedrefs if you want todestroy a non-compressed referencescache.

Explanation: The compressed references shared classcache is removed as requested.

System action: A Java VM is not created and a failuremessage is issued. However, this failure message is anormal response when you request a shared class cacheto be removed.


JVMSHRC833I Non-compressed references sharedcache \"%s\" is destroyed. Use option-Xcompressedrefs if you want to destroya compressed references cache.

Explanation: The non-compressed references sharedclass cache is removed as requested.

System action: A Java VM is not created and a failuremessage is issued. However, this failure message is anormal response when you request a shared class cacheto be removed.


JVMSHRC838I Compressed references shared cachesnapshot \"%s\" is destroyed. Useoption -Xnocompressedrefs if you wantto destroy a non-compressed referencescache snapshot.

Explanation: The compressed references shared cachesnapshot is removed as requested.



JVMSHRC843I Non-compressed references sharedcache snapshot \"%s\" is destroyed. Useoption -Xcompressedrefs if you want todestroy a compressed references cachesnapshot.

Explanation: The non-compressed references sharedcache snapshot is removed as requested.



JVMSHRC816I • JVMSHRC843I


TRCE messagesTrace engine messages.

JVMTRCE000E Trace option unrecognized:-Xtrace:%s

Explanation: An option used with the -Xtraceparameter is not known.


User response: Use -Xtrace:help to find the correctsyntax for the -Xtrace option and try again.

JVMTRCE001E Error processing trace option:-Xtrace:%s

Explanation: An option used with the -Xtraceparameter could not be processed correctly due to asyntax error.



JVMTRCE002E Error processing trace option:-Xtrace:%s=%s

Explanation: An option used with the -Xtraceparameter could not be processed correctly due to aproblem with the option or the arguments used.



JVMTRCE003E Error processing trace option, detail:%s

Explanation: An option used with the -Xtraceparameter could not be processed correctly due to theproblem described in the detail string.



JVMTRCE004W Error opening trace file: %s

Explanation: The specified trace file could not beopened.

System action: The JVM continues but trace data isnot written to this file.

User response: If you need to collect the trace data,restart the JVM specifying a trace file that can beopened.

JVMTRCE005W Error writing header to trace file: %s

Explanation: The specified trace file could not bewritten to.



JVMTRCE006W Error writing %d bytes to trace file:%s rc: %d

Explanation: The specified trace file could not bewritten to.



JVMTRCE007W Error opening next trace filegeneration: %s

Explanation: The specified trace file could not beopened when the JVM attempted to open the next tracefile in a cycle of generational trace files.



JVMTRCE008W Error performing seek in tracefile:%s

Explanation: The JVM could not find an expectedlocation in the specified trace file.



JVMTRCE009W Error writing to snap file

Explanation: The JVM could not write trace data to asnap file while the JVM was running.



JVMTRCE000E • JVMTRCE009W

IBM VM messages 71

JVMTRCE010W Native memory allocation failure,falling back to nodynamic trace settings.

Explanation: The JVM could not allocate space foranother trace buffer.

System action: The JVM continues but trace reusesexisting buffers. Trace points that are not written todisk before a new buffer is required might be lost.

User response: No action is required. However, toreduce the amount of trace points produced, change thetrace options.

JVMTRCE011W Module not configured for trace: %s

Explanation: The JVM could not configure trace forthe specified module, typically due to a native out ofmemory situation.

System action: The JVM continues but there is notrace data generated for this module.

User response: Contact your IBM servicerepresentative. You might need to obtain additionalinformation by running with -Xtrace:debug=<n>.

JVMTRCE012W Unable to open trace point counterfile %s, counters redirected to stderr.

Explanation: The JVM could not open the specifiedfile for the trace point counts at shutdown.

System action: The JVM writes the counterinformation to stderr at shutdown.

User response: If you need to collect the trace data,restart the JVM specifying a trace file that can bewritten to.

JVMTRCE013I Writing trace count info to %s

Explanation: The JVM is writing trace counterinformation to the specified location at shutdown.

System action: The JVM writes the counterinformation to that location at shutdown.

User response: No action required. This message is forinformation only.

JVMTRCE014E Trace engine initialization failed,trace not enabled

Explanation: The JVM cannot start the trace engine.



JVMTRCE015E Error registering trace writesubscriber

Explanation: The JVM cannot start the trace subscriberthread that writes trace buffers to disk.

System action: The JVM continues but trace data isnot written to disk.


JVMTRCE016E Storage for RasGlobalStorage notavailable, trace not enabled

Explanation: The JVM could not be initialized.



JVMTRCE017E Unable to allocate RAS thread localstorage key

Explanation: The JVM could not initialize.



JVMTRCE018E Unable to allocate UTE thread localstorage key




JVMTRCE019E Trace engine failed to initializeproperly, RC = %d




JVMTRCE020W Timeout occurred during traceengine termination

Explanation: A timeout occurred during JVMshutdown while the trace engine is waiting for tracesubscriber threads to finish.

System action: The JVM ends without waiting fortrace subscriber threads to finish.


JVMTRCE010W • JVMTRCE020W


VERB messagesVerbose messages.

JVMVERB000I Verbose stack: "%2$.*1$s" used%3$zd/%4$zd bytes on Java/C stacks

Explanation: Indicates how much stack is used oneach stack for a thread when you specify the-verbose:stack parameter.



JVMVERB002I Verbose stack: maximum stack usewas %1$zd/%2$zd bytes on Java/Cstacks

Explanation: Indicates the largest stack usage for eachstack for all threads when you specify the-verbose:stack parameter.



JVMVERB003E Error: -Xverbosegclog number offiles must be greater than 0

Explanation: Either you specified the -Xverbosegclogparameter with a value of 0 for the number of files, orthe parameter could not be parsed.


User response: Use a number greater than 0 for thenumber of files.

JVMVERB004E Error: -Xverbosegclog number ofcycles must be greater than 0

Explanation: Either you specified the -Xverbosegclogparameter with a value of 0 for the number of cycles,or the parameter could not be parsed.


User response: Use a value greater than 0 for thenumber of cycles.

JVMVERB005E Error: -Xverbosegclog missingfilename

Explanation: You used the -Xverbosegclog parameterwithout specifying a file name.


User response: Specify a valid file name when usingthe -Xverbosegclog parameter.

JVMVERB018W Invalid classpath entry: %s (file I/Ofailed)

Explanation: The JVM could not open the specified.zip file. The file might not exist or the file permissionsmight not allow access by the JVM.

System action: The JVM either ignores the issue orthrows a java/io/IOException exception.

User response: Check that the specified .zip file existsand has appropriate permissions.

JVMVERB019W Invalid classpath entry: %s (fileread failed)

Explanation: The JVM could not read part of thespecified .zip file. The file might be corrupt ortruncated.


User response: If the .zip file is corrupt or truncated,replace it with a valid copy.

JVMVERB020W Invalid classpath entry: %s (filecorrupt)

Explanation: The specified .zip file is corrupt.


User response: Replace the corrupt .zip file with avalid copy.

JVMVERB021W Invalid classpath entry: %s(unsupported file type)

Explanation: The specified .zip file type isunsupported


User response: Replace the specified .zip file with asupported .zip file type.

JVMVERB022W Invalid classpath entry: %s(unknown file type)

Explanation: The specified .zip file type is unknown.


User response: Replace the specified .zip file with a.zip file of a supported type.

JVMVERB000I • JVMVERB022W

IBM VM messages 73

JVMVERB023W Invalid classpath entry: %s(unknown error)

Explanation: An unexpected error occurred whilereading the specified .zip file.


User response: If the problem persists, contact yourIBM Service representative.

JVMVERB024W Invalid classpath entry: %s (jxemissing rom.classes)

Explanation: A rom.classes entry could not be foundin the specified JXE file.


User response: Replace the JXE file with a valid copythat contains a rom.classes entry.

JVMVERB025W Invalid classpath entry: %s (jxecorrupt image header)

Explanation: The specified JXE file had a corruptheader.


User response: Replace the corrupt JXE file with avalid copy.

JVMVERB026W Invalid classpath entry: %s(opposite endian jxe not supported)

Explanation: The Endian nature of the specified JXEfile was not correct for this platform.


User response: Replace the JXE file with one of thecorrect endianness.

JVMVERB027I Verbose stack: Running thread"%2$.*1$s" is using %3$zd/%4$zd byteson Java/C stacks

Explanation: Indicates how much memory was usedfor the Java and C stacks for a thread. This message isissued when you specify the -verbose:stack parameter.



JVMVERB028I Verbose stack: Unable to print thestack info for currently running threads

Explanation: The JVM was unable to obtain a lock forthe currently running threads.



JVMVERB023W • JVMVERB028I


VMUT messagesJVM utility messages.

JVMVMUT003W Options file not found

Explanation: You used the -Xoptionsfile parameterto specify an options file, but the file could not beopened.

System action: The JVM ignores the specified optionsfile.

User response: Correct the command-line parameter.

JVMVMUT004W Malformed option: '%s'

Explanation: The specified option could not be parsed.

System action: The JVM ignores the option.


JVMVMUT005W Option too large: '%s'

Explanation: The specified option is larger than themaximum permitted value.

System action: The JVM ignores the option.


JVMVMUT006E Malformed option %s found in-Xoptionsfile

Explanation: You used the -Xoptionsfile parameterto specify a file. The file contains a token withinquotation marks, but the closing quotation mark ismissing.


User response: Add the missing quotation mark to thefile that is specified by the -Xoptionsfile parameter.

JVMVMUT007E Malformed value forJAVA_TOOL_OPTIONS

Explanation: The JAVA_TOOL_OPTIONS environmentvariable contains a token within quotation marks, butthe closing quotation mark is missing.


User response: Correct the JAVA_TOOL_OPTIONSenvironment variable.

JVMVMUT008E Malformed value forIBM_JAVA_OPTIONS

Explanation: The IBM_JAVA_OPTIONS environmentvariable contains a token within quotation marks, butthe closing quotation mark is missing.


User response: Correct the IBM_JAVA_OPTIONSenvironment variable.

JVMVMUT009E Malformed value for -Xservice

Explanation: The -Xservice command-line optioncontains a token within quotation marks, but theclosing quotation mark is missing.



JVMVMUT010W Malformed option value, option"%1$s%3$.*2$s" contains trailingcharacters "%4$s" which have beenignored

Explanation: The specified option value could not beparsed.

System action: The JVM ignores the option value.


JVMVMUT011E Could not allocate memory forcommand line option array

Explanation: The JVM tried to allocate memory tocopy command-line options, but failed.


User response: Check the available memory in yourprocess or system. Increase the memory that isavailable to start the JVM, then try again.

JVMVMUT013E Options file %s invalid

Explanation: An options file specified with the-Xoptionsfile option cannot be opened or is too large.


User response: Check the size and contents of theoption file.

ZIPS messagesCompressed file messages.

JVMZIPS000W Unable to open %1$s (%2$s) Explanation: The JVM attempted to load the J9 zlib

JVMVMUT003W • JVMZIPS000W

IBM VM messages 75

library, but the operation failed.



JVMZIPS001W Unable to open %s (Missing export)

Explanation: The JVM attempted to find an exportedsymbol in the J9 zlib library, but the operation failed.



JVMZIPS001W


Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those

© Copyright IBM Corp. 2011, 2018 77

websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data discussed herein is presented as derived under specificoperating conditions. Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable 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 mustinclude a copyright notice as follows:


© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. _enter the year or years_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational 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 andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, IntelXeon, Intel SpeedStep, Itanium, and Pentium are trademarks of Intel Corporationin the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Notices 79

https://www.ibm.com/legal/us/en/copytrade.shtml

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see: (i) IBM’s Privacy Policy at https://www.ibm.com/privacy ; (ii)IBM’s Online Privacy Statement at https://www.ibm.com/privacy/details (inparticular, the section entitled “Cookies, Web Beacons and Other Technologies”);and (iii) the “IBM Software Products and Software-as-a-Service Privacy Statement”at https://www.ibm.com/software/info/product-privacy.


https://www.ibm.com/privacy

https://www.ibm.com/privacy/details

https://www.ibm.com/software/info/product-privacy

Notices 81

IBM®

Printed in USA

ibm sdk, java technology edition: ibm vm messagesattempting to pr oduce a dump. system action: the...

Documents