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