IBM SDK, Java Technology Edition: IBM VM messages · PDF fileSystem action: The JVM will...

Click here to load reader

  • date post

    16-Sep-2018
  • Category

    Documents

  • view

    425
  • download

    7

Embed Size (px)

Transcript of IBM SDK, Java Technology Edition: IBM VM messages · PDF fileSystem action: The JVM will...

  • IBM SDK, Java Technology EditionVersion 1

    IBM VM messages

    IBM

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

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

    System action: The JVM ends.

    User response: Contact your IBM servicerepresentative.

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

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

    System action: The JVM ends.

    Copyright IBM Corp. 2011, 2018 1

  • User response: Contact your IBM servicerepresentative.

    DUMP messagesDump agent messages.

    JVMDUMP000E Dump option unrecognized:-Xdump:%s

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

    System action: The JVM ends.

    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.

    System action: The JVM ends.

    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.

    System action: The JVM ends.

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

    JVMDUMP003E Dump agent unrecognized: %s

    Explanation: An unsupported dump type has beenrequested.

    System action: The JVM ends.

    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.

    System action: The JVM continues.

    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.

    System action: INTERNAL USE ONLY

    User response: INTERNAL USE ONLY

    JVMDUMP017I Aborting: Cannot compress file (%s)

    Explanation: The JVM cannot compress a file.

    System action: INTERNAL USE ONLY

    User response: INTERNAL USE ONLY

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

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

    System action: INTERNAL USE ONLY

    User response: INTERNAL USE ONLY

    JVMDUMP019I JVM requesting %s dump

    Explanation: A dump file of the type specified 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.

    System action: The JVM continues.

    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