/******************************************************************************/ /* Document : Some Java exceptions, messages and errors. */ /* Doc. Version : 2 */ /* File : messages_java.txt */ /* Purpose : Some Java exceptions and messages for reference for anybody */ /* who might be interested. */ /* Date : 26/05/2009 */ /* Compiled by : Albert van der Sel */ /* Best use : Use find/search of your editor to search for a errorcode or */ /* exception, or any other identifier. */ /* Because an identifier may be repeated multiple times */ /* in this note, you should also repeat the search troughout */ /* this note. */ /******************************************************************************/ Remarks: (1): Java Exceptions don't have error codes, they are distinguished by the Exception class that is thrown, for example: java.lang.OutOfMemory, ArrayIndexOutOfBoundsException, etc.. But in all frameworks where Java is used, like Application Servers etc.., many sorts of "errors" or "messages" are possible. So, here is a (very) small collection of those exceptions and errormessages. (2): This collection is quite unstructured. The only structure applied, is the division of similar content into various "sections". ============================================= SECTION 0: Some Java terms: ============================================= In the Java programming language, all source code is first written in plain text files ending with the ".java" extension. You can then compile the source files into ".class" files, with the javac compiler. A .class file does not contain code that is native to your processor; it instead contains "bytecodes" which is the "machine language" of the "JVM", the Java Virtual Machine (Java VM). The JVM can run .class or .jar files. -- So, you could even use a simple flat file editor, create a .java file, and compile it with the javac compiler. And suppose you had entered correct code, you can then run it in the JVM. -- Ofcourse, most developers will use advanced graphical java development tools. The JVM is available on almost any platform, so you can use your program almost anywhere. Some terms which we will see often with Java are: >>> JDK or SDK: Java Development Kit (JDK) Software Development Kit (SDK) The JDK is a set of utilities to aid development. Among others are: javac The compiler for the Java programming language. java The launcher for Java applications. javadoc API documentation generator. appletviewer Run and debug applets without a web browser. jar Manage Java Archive (JAR) files. jdb The Java Debugger. javah C header and stub generator. Used to write native methods. javap Class file disassembler extcheck Utility to detect Jar conflicts. javald Utility that creates a convenient wrapper file that captures the necessary environment needed to run a Java application. etc.. The JDK is a subset of the SDK, which includes more features and documentation. Ofcourse, everybody will talk about the SDK, because "more is better". >>> CLASSPATH: The CLASSPATH is an environment variable that tells the Java compiler javac, or other SDK tool, where to look for class files to import, or for java JVM where to find class files to interpret (to run). So, it also tells the Java Virtual Machine where to look for user-defined classes and packages in Java programs. The class path can be set using either the -classpath option when calling an SDK tool (the preferred method) or by setting the CLASSPATH environment variable. The -classpath option is preferred because you can set it individually for each application without affecting other applications and without other applications modifying its value. $ sdkTool -classpath classpath1:classpath2... -or- $ export CLASSPATH classpath1:classpath2... # assuming a shell like bash, korn etc.. >>> JVM The Java Virtual Machine, which executes your java applications. These applications are build on executable code, or bytecodes, which the JVM "can understand". It resembles a "virtual machine" which runs your code. The JVM is available on most platforms (Windows, Unix, Midrange and Mainframe systems etc..), so your programs are highly portable. >>> JRE Java Runtime Environment This is the base of software, needed to support the JVM. The JVM runtime executes .class or .jar files, emulating the JVM instruction set by interpreting it, or using a just-in-time compiler (JIT) such as Sun's HotSpot. JIT compiling, not interpreting, is used in most JVMs today to achieve greater speed. Ahead-of-time compilers that enable the developer to precompile class files into native code for a particular platforms also exist. Like most virtual machines, the Java Virtual Machine has a stack-based architecture which resembles a bit the situation of a microprocessor. The JVM, which is the instance of the JRE (Java Runtime Environment), comes into action when a Java program is executed. When execution is complete, this instance is garbage-collected. JIT is the part of the JVM that is used to speed up the execution time. JIT compiles parts of the byte code that have similar functionality at the same time, and hence reduces the amount of time needed for compilation. >>> J2EE: J2EE is a true and extended framework. The platform was known as Java 2 Platform, Enterprise Edition or J2EE until the name was changed to Java EE in version 5. The current version is called Java EE 5. The previous version is called J2EE 1.4. Java EE includes several API specifications, such as JDBC, RMI, e-mail, JMS, web services, XML, etc, and defines how to coordinate them. Java EE also features some specifications unique to Java EE for components. These include Enterprise JavaBeans, servlets, portlets (following the Java Portlet specification), JavaServer Pages and several web service technologies. This allows developers to create enterprise applications that are portable and scalable, and that integrate with legacy technologies. A Java EE application server can handle transactions, security, scalability, concurrency and management of the components that are deployed to it, in order to enable developers to concentrate more on the business logic of the components rather than on infrastructure and integration tasks. The J2EE platform uses a multi-tiered distributed application model for both enterprise applications Application logic is divided into “components” according to function, and the various application components that make up a J2EE application are installed on different machines depending on the tier in the multi-tiered J2EE environment to which the application component belongs ============================================= SECTION 1: The infamous JVMXM008 error ============================================= Problem: JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine. This error may arise due to various causes. The most common observed cause, is incorrect permission on some mount point. In the following, some cases are presented, which may resemble your situation: Case 1: ======= Incorrect underlying mount point permission's prevent WebSphere Application Server from starting Technote (troubleshooting) Problem(Abstract) When the filesystem in which Application Server is mounted has incorrect mount point permission's the server may not start when attempting to start the server as a non-root user. Attempting to execute the $WAS_HOME/java/bin/java as this non-root user causes the following error. /usr/WebSphere/DeploymentManager/java/bin> java -version JVM not found: libjvm.a - libjvm.a /usr/WebSphere/DeploymentManager/bin> startManager.sh JVMXM008: Error occurred while initialising System ClassException in thread "main" Could not create JVM. Cause The JVM is Unable to initialize because the user does not have the proper permission to access the necessary files due to incorrect underlying mount point permission's. Resolving the problem Unmount the file system and change the permission's of the mount point to 777 (rwxrwxrwx). Mount the file system and run Application Server as a non-root user. Cross Reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK Case 2: ======= WebSphere Application Server V6.1's Java on AIX will not start as a non-root user and will report error "JVMXM008" or "JVM not found: libjvm.a - libjvm.a" Technote (troubleshooting) Problem(Abstract) When attempting to run WebSphere Application Server V6.1 as a non-root user on AIX, it may fail to initialize. It produces an error message, "JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine." or a different error message, "JVM not found: libjvm.a - libjvm.a". Running the same process as the root user does not produce any problems. Symptom This article describes an issue clients may encounter after successfully installing WebSphere Application Server V6.1 on AIX as either the root user or a non-root user. Attempting to use any WebSphere tools, such as the profile creation utility, fail immediately. The cause of all those failures is because WebSphere Application Server's Java SDK does not initialize properly when run as the non-root user. Testing Java in the reveals specific errors, as shown in the examples below. Examples In these examples illustrating the Java initialization errors, assume that WebSphere Application Server has been successfully installed as a non-root user to the /usr/WAS directory. Example One: Java fails to initialize when running it from a location outside its directory Running these commands... cd / /usr/WAS/java/jre/bin/java -version ...produces this error: JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine. Example Two: Java fails to initialize when running it from inside its "bin" directory Running these commands... cd /usr/WAS/java/jre/bin ./java -version ...produces this error: JVM not found: libjvm.a - libjvm.a The error shown in Example Two occurs even though the libjvm.a file is present in the proper location and has correct permissions. Cause If the mount point for the filesystem to which WebSphere is installed is not set up correctly, this can cause problems for Java initialization. Resolving the problem In situations where Java initializes properly when run as the root user but fails when run as a non-root user, check the following points: The WebSphere Application Server V6.1 installation should be successful. Check the installation's "log.txt" file to ensure that the installation ended with a "success" message. A non-root user must have read access to all files installed with WebSphere Application Server V6.1, including all of the files in the product's "java" subdirectory. This can be accomplished by granting ownership of all the product's files to that non-root user. A non-root user should also have access to the AIX system libraries, such as the libraries in /usr/lib and /usr/ccs/lib . If each of those points are checked and appear to be in good order, then there is one more aspect of the WebSphere configuration to review. Follow these steps to check and correct an issue which could lead to problems when initializing Java as a non-root user: Locate the mount point of the filesystem where WebSphere Application Server V6.1 is mounted on. Unmount that filesystem. Check the permissions of the blank directory which acts as the mount point for the filesystem. The permissions should be at least "755". The ownership and permissions of that directory must be configured in a manner which allows the non-root user read access to that directory. Check that the directory which acts as the mount point is empty. If the directory contains anything, remove that content so that the directory becomes empty. Remount the WebSphere Application Server V6.1 filesystem. Java should initialize properly as a non-root user once the issues with the mount point permissions are resolved. Case 3: ======= JVMXM008 workaround Brian D. Carlstrom wrote: At Stanford I have my own automated regression infrastructure that runs processor simulations remotely via ssh. One problem that has existed for months is this error from jbuild.linkImage: JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine. I noticed that Sergiy Kyrylkov had posted in his blog about a similar issue when running JikesRVM regressions from cron: http://sergiy.kyrylkov.name/blog/Jikes%20RVM/ I found that if I forced the ssh remote bash to be a login shell, I did not get the error. Eventually I narrowed it down to the fact that /etc/profile was sourcing /etc/profile.d/lang.sh which was setting the LANG environment variable. I found that if I my remote command set LANG explicitly, I can build jikesrvm over ssh without the JVMXM008 error. I just wanted to post the workaround to the list in case it helps someone else. I don't know if it is needed for later SDKs, but my version of JikesRVM seems to only work with 1.4.1, nothing earlier, nothing later. For the record, this is on Fedora Core 4 on G5 machines running IBM's SDK 1.4.1-SR2 with a jikesrvm source tree from last updated at "2005-12-09 03:00:00". We are frozen until after some paper deadlines this month... I hope I'll have time soon to try this workaround on UNM machines. Case 4: ======= Q: Hi When I try to install PT 8.46.02 in AIX box, I m got the below error message. "JVMXM008: Error occurred while initializing System Class Exception in thread "main" Could not create the Java virtual machine". Any help could really appreciate. A: set java_home class path before installing Case 5: ======= Thursday, 27 November 2008 JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine. « Problems running gmi to upgrade Tivoli Directory Integrator TDI | Main Trying to get IBM Websphere running as non root user (wasadmin:wasgroup), we got the following error at startup: JVMXM008: Error occured while initialising System ClassException in thread "main" Could not create the Java virtual machine. This problem also occurs, just running java -version somewhere under /usr/ibm. (/usr/ibm/WebSphere or /usr/ibm/WebSphere/Appserver etc.) Everywhere else in the filesystem, there was no problem and java spits out its version string. The cause was, that the /usr/ibm/WebSphere/Appserver filesystem was a mounted volumegroup. /dev/volg /usr/ibm Althoug the rights on /usr/ibm looked good, when the FS was mounted, the JVM did not work. drwxr-xr-x 13 root system 4096 Jul 29 17:56 /usr/ibm The root cause shows up, when the /usr/ibm fs gets unmounted: drwxr-x--- 13 root system 4096 Jan 01 17:56 /usr/ibm So changing the /usr/ibm directory rights while the fs was unmounted solved the problem. Posted by awaldman at 4:35 PM in IBM TIM TDI ============================================= SECTION 2: : Lists of Java exceptions: ============================================= List 1: ======= AclNotFoundException ActivationException AlreadyBoundException ApplicationException ArrayOutOfBoundsException AWTException BackingStoreException BadLocationException BatchUpdateException CertificateException ChangedCharSetException CharacterCodingException CharConversionException ClassNotFoundException CloneNotSupportedException ClosedChannelException DataFormatException DestroyFailedException EOFException ExpandVetoException FileLockInterruptionException FileNotFoundException FontFormatException GeneralSecurityException GSSException IIOException IllegalAccessException IllegalArgumentException InstantiationException InterruptedException InterruptedIOException IntrospectionException InvalidMidiDataException InvalidPreferencesFormatException InvocationTargetException IOException LastOwnerException LineUnavailableException MalformedURLException MidiUnavailableException MimeTypeParseException NamingException NegativeArraySizeException NoninvertibleTransformException NoSuchElement NoSuchFieldException NoSuchMethodException NotBoundException NotOwnerException NumberFormatException ObjectStreamException ParseException ParserConfigurationException PrinterException PrintException PrivilegedActionException PropertyVetoException ProtocolException RefreshFailedException RemarshalException RemoteException RuntimeException SAXException ServerNotActiveException SocketException SQLException SQLWarning SSLException SyncFailedException TooManyListenersException TransformerException UnknownHostException UnknownServiceException UnsupportedAudioFileException UnsupportedCallbackException UnsupportedEncodingException UnsupportedFlavorException UnsupportedLookAndFeelException UnsupportedOperationException URISyntaxException UserException UTFDataFormatException XAException ZipException List 2: ======= Exception in Java are classified on the basis of the exception handled by the java compiler. Java consists of the following type of built in exceptions: 1.Checked Exception:- These exception are the object of the Exception class or any of its subclasses except Runtime Exception class. These condition arises due to invalid input, problem with your network connectivity and problem in database. java.io.IOException is a checked exception. This exception is thrown when there is an error in input-output operation. In this case operation is normally terminated. >>> List of Checked Exceptions- Following are the list of various checked exception that defined in the java.lang package. Exception Reason for Exception ClassNotFoundException This Exception occurs when Java run-time system fail to find the specified class mentioned in the program Instantiation Exception This Exception occurs when you create an object of an abstract class and interface Illegal Access Exception This Exception occurs when you create an object of an abstract class and interface Not Such Method Exception This Exception occurs when the method you call does not exist in class 2. Unchecked Exception:- These Exception arises during run-time ,that occur due to invalid argument passed to method. The java Compiler does not check the program error during compilation. For Example when you divide a number by zero, run-time exception is raised. Exception Reason for Exception Arithmetic Exception These Exception occurs, when you divide a number by zero causes an Arithmetic Exception Class Cast Exception These Exception occurs, when you try to assign a reference variable of a class to an incompatible reference variable of another class Array Store Exception These Exception occurs, when you assign an array which is not compatible with the data type of that array Array Index Out Of Bounds Exception These Exception occurs, when you assign an array which is not compatible with the data type of that array Null Pointer Exception These Exception occurs, when you try to implement an application without referencing the object and allocating to a memory Number Format Exception These Exception occurs, when you try to convert a string variable in an incorrect format to integer (numeric format) that is not compatible with each other Negative ArraySize Exception These are Exception, when you declare an array of negative size. List 3: ======= IDL and Java CORBA has two types of exceptions: standard system exceptions which are fully specified by the OMG and user exceptions which are defined by the individual application programmer. CORBA exceptions are a little different from Java exception objects, but those differences are largely handled in the mapping from IDL to Java. Topics in this section include: Differences Between CORBA and Java Exceptions System Exceptions System Exception Structure Minor Codes Completion Status User Exceptions Minor Code Meanings Differences Between CORBA and Java Exceptions To specify an exception in IDL, the interface designer uses the raises keyword. This is similar to the throws specification in Java. When you use the exception keyword in IDL you create a user-defined exception. The standard system exceptions need not (and cannot) be specified this way. System Exceptions CORBA defines a set of standard system exceptions, which are generally raised by the ORB libraries to signal systemic error conditions like: Server-side system exceptions, such as resource exhaustion or activation failure. Communication system exceptions, for example, losing contact with the object, host down, or cannot talk to ORB daemon (orbd). Client-side system exceptions, such as invalid operand type or anything that occurs before a request is sent or after the result comes back. All IDL operations can throw system exceptions when invoked. The interface designer need not specify anything to enable operations in the interface to throw system exceptions -- the capability is automatic. This makes sense because no matter how trivial an operation's implementation is, the potential of an operation invocation coming from a client that is in another process, and perhaps (likely) on another machine, means that a whole range of errors is possible. Therefore, a CORBA client should always catch CORBA system exceptions. Moreover, developers cannot rely on the Java compiler to notify them of a system exception they should catch, because CORBA system exceptions are descendants of java.lang.RuntimeException. System Exception Structure All CORBA system exceptions have the same structure: exception { // descriptive of error unsigned long minor; // more detail about error CompletionStatus completed; // yes, no, maybe } System exceptions are subtypes of java.lang.RuntimeException through org.omg.CORBA.SystemException: java.lang.Exception | +--java.lang.RuntimeException | +--org.omg.CORBA.SystemException | +--BAD_PARAM | +--//etc. Minor Codes All CORBA system exceptions have a minor code field, a number that provides additional information about the nature of the failure that caused the exception. Minor code meanings are not specified by the OMG; each ORB vendor specifies appropriate minor codes for that implementation. For the meaning of minor codes thrown by the Java ORB, see Minor code meanings . Completion Status All CORBA system exceptions have a completion status field, indicating the status of the operation that threw the exception. The completion codes are: COMPLETED_YES The object implementation has completed processing prior to the exception being raised. COMPLETED_NO The object implementation was not invoked prior to the exception being raised. COMPLETED_MAYBE The status of the invocation is unknown. User Exceptions CORBA user exceptions are subtypes of java.lang.Exception through org.omg.CORBA.UserException: java.lang.Exception | +--org.omg.CORBA.UserException | +-- Stocks.BadSymbol | +--//etc. Each user-defined exception specified in IDL results in a generated Java exception class. These exceptions are entirely defined and implemented by the programmer Minor Code Meanings System exceptions all have a field minor that allows CORBA vendors to provide additional information about the cause of the exception. The table below lists the minor codes of Java IDL's system exceptions, along with their significance. ORB Minor Codes and Their Meanings Code Meaning BAD_PARAM Exception Minor Codes 1 A null parameter was passed to a Java IDL method. COMM_FAILURE Exception Minor Codes 1 Unable to connect to the host and port specified in the object reference, or in the object reference obtained after location/object forward. 2 Error occurred while trying to write to the socket. The socket has been closed by the other side, or is aborted. 3 Error occurred while trying to write to the socket. The connection is no longer alive. 6 Unable to successfully connect to the server after several attempts. DATA_CONVERSION Exception Minor Codes 1 Encountered a bad hexadecimal character while doing ORB string_to_object operation. 2 The length of the given IOR for string_to_object() is odd. It must be even. 3 The string given to string_to_object() does not start with IOR: and hence is a bad stringified IOR. 4 Unable to perform ORB resolve_initial_references operation due to the host or the port being incorrect or unspecified, or the remote host does not support the Java IDL bootstrap protocol. INTERNAL Exception Minor Codes 3 Bad status returned in the IIOP Reply message by the server. 6 When unmarshaling, the repository id of the user exception was found to be of incorrect length. 7 Unable to determine local hostname using the Java APIs InetAddress.getLocalHost().getHostName(). 8 Unable to create the listener thread on the specific port. Either the port is already in use, there was an error creating the daemon thread, or security restrictions prevent listening. 9 Bad locate reply status found in the IIOP locate reply. 10 Error encountered while stringifying an object reference. 11 IIOP message with bad GIOP v1.0 message type found. 14 Error encountered while unmarshaling the user exception. 18 Internal initialization error. INV_OBJREF Exception Minor Codes 1 An IOR with no profile was encountered. MARSHAL Exception Minor Codes 4 Error occured while unmarshaling an object reference. 5 Marshalling/unmarshaling unsupported IDL types like wide characters and wide strings. 6 Character encountered while marshaling or unmarshaling a character or string that is not ISO Latin-1 (8859.1) compliant. It is not in the range of 0 to 255. NO_IMPLEMENT Exception Minor Codes 1 Dynamic Skeleton Interface is not implemented. OBJ_ADAPTER Exception Minor Codes 1 No object adapter was found matching the one in the object key when dispatching the request on the server side to the object adapter layer. 2 No object adapter was found matching the one in the object key when dispatching the locate request on the server side to the object adapter layer. 4 Error occured when trying to connect a servant to the ORB. OBJ_NOT_EXIST Exception Minor Codes 1 Locate request got a response indicating that the object is not known to the locator. 2 Server id of the server that received the request does not match the server id baked into the object key of the object reference that was invoked upon. 4 No skeleton was found on the server side that matches the contents of the object key inside the object reference. UNKNOWN Exception Minor Codes 1 Unknown user exception encountered while unmarshaling: the server returned a user exception that does not match any expected by the client. 3 Unknown runtime exception thrown by the server implementation. Name Server Minor Codes and Their Meanings Code Meaning INITIALIZE Exception Minor Codes 150 Transient name service caught a SystemException while initializing. 151 Transient name service caught a Java exception while initializing. INTERNAL Exception Minor Codes 100 An AlreadyBound exception was thrown in a rebind operation. 101 An AlreadyBound exception was thrown in a rebind_context operation. 102 Binding type passed to the internal binding implementation was not BindingType.nobject or BindingType.ncontext. 103 Object reference was bound as a context, but it could not be narrowed to CosNaming.NamingContext. 200 Implementation of the bind operation encountered a previous binding. 201 Implementation of the list operation caught a Java exception while creating the list iterator. 202 Implementation of the new_context operation caught a Java exception while creating the new NamingContext servant. 203 Implementaton of the destroy operation caught a Java exception while disconnecting from the ORB. List 4: ======= Exceptions Meaning ArithmeticException Arithmetic error, such as divide-by-zero. ArrayIndexOutOfBoundsException Array index is out-of-bounds. ArrayStoreException Assignment to an array element of an incompatible type. ClassCastException Invalid cast. IllegalArgumentException Illegal argument used to invoke a method. IllegalMonitorStateException Illegal monitor operation, such as waiting on an unlocked thread. IllegalStateException Environment or application is in incorrect state. IllegalThreadStateException Requested operation not compatible with current thread state. IndexOutOfBoundsException Some type of index is out-of-bounds. NegativeArraySizeException Array created with a negative size. NullPointerException Invalid use of a null reference. NumberFormatException Invalid conversion of a string to a numeric Format SecurityException Attempt to violate security. StringIndexOutOfBounds Attempt to index outside the bounds of a string UnsupportedOperationException An unsupported operation was encountered List of few Checked Exceptions available in Java are: Exception Meaning ClassNotFoundException Class not found. CloneNotSupportedException Attempt to clone an object that does not implement the Cloneable interface. IllegalAccessException Access to a class is denied. InstantiationException Attempt to create an object of an abstract class or interface. InterruptedException One thread has been interrupted by another thread. NoSuchFieldException A requested field does not exist. NoSuchMethodException A requested method does not exist. List 5: ======= R Runtime java.lang.RuntimeException E Error java.lang.Error C Checked java.lang.Exception Exception Name Type Package Notes AbstractMethodError E java.lang AccessControlException R java.security This is an exception that is thrown whenever a reference is made to a non-existent ACL (Access Control List). notes. AccessException C java.rmi Thrown by certain methods of the java.rmi.Naming class. AclNotFoundException C java.security.acl Thrown whenever a reference is made to a non-existent ACL (Access Control List). ActivateFailedException C java.rmi.activation thrown by the RMI runtime when activation fails during a remote call to an activatable object. ActivationException C java.rmi.activation AlreadyBoundException C javax.naming ApplicationException C org.omg.CORBA.portable Used for reporting application level exceptions between ORBs and stubs ArithmeticException R java.lang Most commonly a divide by zero. notes. ArrayIndexOutOfBoundsException R java.lang Can be handled more generically with IndexOutOfBoundsException. notes. ArrayStoreException R java.lang Thrown to indicate that an attempt has been made to store the wrong type of object into an array of objects. notes. AttributeInUseException C javax.naming.directory AttributeModificationException C javax.naming.directory AuthenticationException C javax.naming AuthenticationNotSupportedException C javax.naming AWTError E java.awt AWTError E java/awt AWTException C java.awt BadLocationException C javax.swing.text This exception is to report bad locations within a document model. BatchUpdateException C java.sql BindException C java.net Signals that an error occurred while attempting to bind a socket to a local address and port CannotProceedException C javax.naming CannotRedoException R javax.swing.undo CannotUndoException R javax.swing.undo CertificateEncodingException C java.security.cert CertificateException C java.security.cert CertificateExpiredException C java.security.cert CertificateNotYetValidException C java.security.cert CertificateParsingException C java.security.cert ChangedCharSetException C javax.swing.text CharConversionException C java.io ClassCastException R java.lang notes. ClassCircularityError E java.lang ClassFormatError E java.lang notes. ClassNotFoundException C java.lang notes. CloneNotSupportedException C java.lang CMMException R java.awt.color CommunicationException C javax.naming ConcurrentModificationException R java.util This exception may be thrown by methods that have detected concurrent modification of a backing object when such modification is not permissible. E.g. two threads modifying a HashMap simultaneously. notes. ConfigurationException C javax.naming ConnectException C java.rmi ConnectIOException C java.rmi ContextNotEmptyException C javax.naming CRLException C java.security.cert CRL (Certificate Revocation List) Exception. DataFormatException C java.util.zip DigestException C java.security EmptyStackException R java.util Thrown by methods in the Stack class to indicate that the stack is empty. Does not refer to the system stack. EOFException C java.io notes. Error E java.lang Catches any serious error such as OutOfMemoryError that you unlikely can recover from. Exception C java.lang generic. Catches any specify Exception plus general Runtime exceptions, but not Errors. ExceptionInInitializerError E java.lang notes. ExceptionInInitializerError E java.lang ExpandVetoException C javax.swing.tree ExportException C java.rmi.server FileNotFoundException C java.io FontFormatException C java.awt GeneralSecurityException C java.security IllegalAccessError E java.lang notes. IllegalAccessException C java.lang Thrown when an application tries to load in a class, but the currently executing method does not have access to the definition of the specified class, because the class is not public and in another package. IllegalArgumentException R java.lang Most common exception to reject a bad parameter to a method. IllegalComponentStateException R java.awt IllegalMonitorStateException R java.lang IllegalPathStateException R java.awt.geom IllegalStateException R java.lang Signals that a method has been invoked at an illegal or inappropriate time. IllegalThreadStateException R java.lang ImagingOpException R java.awt.image IncompatibleClassChangeError E java.lang notes. IndexOutOfBoundsException R java.lang Similar to ArrayIndexOutOfBoundsException for ArrayList. IndirectionException R org.omg.CORBA.portable InstantiationError E java.lang InstantiationException C java.lang InsufficientResourcesException C javax.naming InternalError E java.lang InterruptedException C java.lang Thrown when a thread is waiting, sleeping, or otherwise paused for a long time and another thread interrupts it using the interrupt method in class Thread. InterruptedIOException C java.io InterruptedNamingException C javax.naming IntrospectionException C java.beans InvalidAlgorithmParameterException C java.security This is a GeneralSecurityException. See IllegalArgumentException. InvalidAttributeIdentifierException C javax.naming.directory InvalidAttributesException C javax.naming.directory InvalidAttributeValueException C javax.naming.directory InvalidClassException C java.io notes. InvalidDnDOperationException R java.awt.dnd InvalidKeyException C java.security InvalidKeySpecException C java.security.spec InvalidMidiDataException C javax.sound.midi InvalidNameException C javax.naming InvalidObjectException C java.io InvalidParameterException R java.security InvalidParameterSpecException C java.security.spec InvalidSearchControlsException C javax.naming.directory InvalidSearchFilterException C javax.naming.directory InvalidTransactionException C javax.transaction InvocationTargetException C java.lang.reflect IOException C java.io JarException C java.util.jar KeyException C java.security KeyManagementException C java.security KeyStoreException C java.security LastOwnerException C java.security.acl LdapReferralException C javax.naming.ldap LimitExceededException C javax.naming LineUnavailableException C javax.sound.sampled LinkageError E java.lang LinkException C javax.naming LinkLoopException C javax.naming MalformedLinkException C javax.naming MalformedURLException C java.net MarshalException C java.rmi MidiUnavailableException C javax.sound.midi MimeTypeParseException C java.awt.datatransfer MissingResourceException R java.util NameAlreadyBoundException C javax.naming NameNotFoundException C javax.naming NamingException C javax.naming NamingSecurityException C javax.naming NegativeArraySizeException R java.lang NoClassDefFoundError E java.lang notes. NoInitialContextException C javax.naming NoninvertibleTransformException C java.awt.geom NoPermissionException C javax.naming NoRouteToHostException C java.net NoSuchAlgorithmException C java.security NoSuchAttributeException C javax.naming.directory NoSuchElementException R java.util NoSuchFieldError E java.lang NoSuchFieldException C java.lang NoSuchMethodError E java.lang notes. NoSuchMethodException C java.lang NoSuchObjectException C java.rmi NoSuchProviderException C java.security notes. NotActiveException C java.io Thrown when serialization or deserialization is not active NotBoundException C java.rmi NotContextException C javax.naming NotOwnerException C java.security.acl NotSerializableException C java.io notes. NullPointerException R java.lang Actually a null reference exception. notes. NumberFormatException R java.lang Commonly thrown when a String is converted to internal binary numeric format. notes. ObjectStreamException C java.io OperationNotSupportedException C javax.naming OptionalDataException C java.io Unexpected data appeared in an ObjectInputStream trying to read an Object. Occurs when the stream contains primitive data instead of the object that is expected by readObject. The EOF flag in the exception is true indicating that no more primitive data is available. The count field contains the number of bytes available to read. OutOfMemoryError E java.lang By the time this happens it is almost too late. gc has already done what it could. Possibly some process has just started gobbling RAM, or perhaps the problem you are trying to solve is just too big for the size of the allotted virtual ram. You can control that with the java.exe command line switches. ParseException C java.text PartialResultException C javax.naming PolicyError E org.omg.CORBA PrinterAbortException C java.awt.print PrinterException C java.awt.print PrinterIOException C java.awt.print PrivilegedActionException C java.security ProfileDataException R java.awt.color PropertyVetoException C java.beans ProtocolException C java.net ProviderException R java.security RasterFormatException R java.awt.image ReferralException C javax.naming RemarshalException C org.omg.CORBA.portable RemoteException C java.rmi RMISecurityException C java.rmi RuntimeException R java.lang Error that can occur in almost any code e.g. NullPointerException. Use this when to catch general errors when no specific exception is being thrown. SchemaViolationException C javax.naming.directory SecurityException R java.lang ServerCloneException C java.rmi.server ServerError E java.rmi ServerException C java.rmi ServerNotActiveException C java.rmi.server ServerRuntimeException C java.rmi ServiceUnavailableException C javax.naming SignatureException C java.security SizeLimitExceededException C javax.naming SkeletonMismatchException C java.rmi.server SkeletonNotFoundException C java.rmi.server SocketException C java.net SocketSecurityException C java.rmi.server SQLException C java.sql StackOverflowError E java.lang notes. StreamCorruptedException C java.io ObjectStream data are scrambled. notes. StringIndexOutOfBoundsException R java.lang Can be handled more generically with IndexOutOfBoundsException. notes. StubNotFoundException C java.rmi SyncFailedException C java.io SystemException R org.omg.CORBA TimeLimitExceededException C javax.naming TooManyListenersException C java.util TransactionRequiredException C javax.transaction TransactionRolledbackException C javax.transaction UndeclaredThrowableException R java.lang.reflect UnexpectedException R java.rmi UnknownError E java.lang UnknownException R org.omg.CORBA.portable UnknownGroupException C java.rmi.activation UnknownHostException C java.rmi UnknownHostException C java.net UnknownObjectException C java.rmi.activation UnknownServiceException C java.net UnknownUserException C org.omg.CORBA UnmarshalException C java.rmi notes. UnrecoverableKeyException C java.security UnsatisfiedLinkError E java.lang notes. UnsupportedAudioFileException C javax.sound.sampled UnsupportedClassVersionError E java.lang notes. UnsupportedDataTypeException C java.io undocumented. notes. UnsupportedEncodingException C java.io UnsupportedFlavorException C java.awt.datatransfer UnsupportedLookAndFeelException C javax.swing UnsupportedOperationException R java.lang Use for code not yet implemented, or that you deliberately did not implement. UserException C org.omg.CORBA UTFDataFormatException C java.io VerifyError E java.lang notes. VirtualMachineError E java.lang WriteAbortedException C java.io ZipException C java.util.zip notes. ========================================================= SECTION 3: : A few common Java exceptions in more detail: ========================================================= 3.1. java.lang.OutOfMemory 3.2. javax.naming.NameNotFoundException 3.3. javax.servlet.ServletException 3.4. java.lang.StringIndexOutOfBoundsException 3.5. java.net.SocketException 3.6. java.io.IOException 3.7. java.io.FileNotFoundException 3.8. java.util.MissingResourceException 3.9. java.lang.ClassNotFoundException 3.10.java.lang.StringIndexOutOfBoundsException 3.11.java.io.InterruptedIOException 3.12 java.lang.NullPointerException 3.1: java.lang.OutOfMemory =========================== ------- Note 1: ------- The Java process has two memory areas: the Java heap, and the "native heap", which combine total the memory usage of the process. The Java heap is controlled via the -Xms and -Xmx setting, and the space available to the native heap is that which isn't used by the Java heap. The act of reducing the maximum Java heap size has made the "native heap" bigger, and this is the area that was memory constrained. We know this because the OutOfMemoryError was generated the message informed you that the JVM was unable to allocate a new native stack, this is allocated onto the native heap (there is also a Java thread object which is created and allocated onto the Java heap). It is entirely possible that the amount of "native heap" available to the JVM was insufficient to allocate the underlying resources to run the Java process under the load that was being driven through it. The native heap is now 500MB bigger, and unless there is a memory leak or the load is significantly increased, this change should prevent any OutOfMemoryErrors based on the native heap. ------- Note 2: ------- Old thread, but the "essence" is still true. A: Hi, I'm experiment with Tomcat with simple "Hello World" servlet. When I send 50 concurrent requests, I got java.lang.outOfMemory error. Tomcat works fine upto 40 concurrent requests for the same servlet. I'm using Tomcat 3.1M1 with Java 1.2 on Solaris 2.7. We try to add -mx swith to the Java invocation in tomcat.sh (line 102) $JAVACMD -mx96m org.apache.tomcat.shell.Startup "$@" & And it still out of memory. Any suggestion? Lishin Q: Hi Lishin This could be to do with exceeding max file-descriptors - this gave us the error below (45 connections) We are running tomcat on Solaris 2.6. Each new connection uses at least one socket connection, which is treated as a file-descriptor. There is a default limit (user) of 64 file descriptors To check this try: ulimit -n To increase this try ulimit -n There will be a system limit - for Solaris this is default 1024: system limit: ulimit -Hn I hope this helps - I had a very frustrating time solving this one! Joe. ------- Note 3: ------- LDR_CNTRL Purpose: Allows tuning of the kernel loader. Values: Default: Not set Possible Values: PREREAD_SHLIB, LOADPUBLIC, IGNOREUNLOAD, USERREGS, MAXDATA, DSA, PRIVSEG_LOADS Display: echo $LDR_CNTRL Change: LDR_CNTRL={PREREAD_SHLIB | LOADPUBLIC| ...} export LDR_CNTRLChange takes effect immediately in this shell. Change is effective until logging out of this shell. Permanent change is made by adding the following line to the /etc/environment file: LDR_CNTRL={PREREAD_SHLIB | LOADPUBLIC| ...} Diagnosis: N/A Tuning: The LDR_CNTRL environment variable can be used to control one or more aspects of the system loader behavior. You can specify multiple options with the LDR_CNTRL variable. When doing this, separate the options using an @ character (that is, LDR_CNTRL=PREREAD_SHLIB@LOADPUBLIC). Specifying the PREREAD_SHLIB option will cause entire libraries to be read as soon as they are accessed. With VMM readahead tuned, a library can be read in from disk and be cached in memory by the time the program starts to access its pages. While this method can use more memory, it can enhance performance of programs that use many shared library pages providing the access pattern is non-sequential. (for example, Catia). Specifying the LOADPUBLIC option directs the system loader to load all modules requested by an application into the global shared library segment. If a module cannot be loaded publicly into the global shared library segment then it is loaded privately for the application. Specifying the IGNOREUNLOAD option will cause modules that are marked to be unloaded and used again (if the module has not been unloaded already). As a side effect of this option, you can end up with two different data instances for the module. Specifying the USERREGS option will tell the system to save all general-purpose user registers across system calls made by an application. This can be helpful in applications doing garbage collection. Specifying the MAXDATA option sets the maximum heap size for a process, including overriding any MAXDATA value specified in an executable. If you want to use Large Program Support with a data heap size of 0x30000000, then specify LDR_CNTRL=MAXDATA=0x30000000. To turn off Large Program Support, specify LDR_CNTRL=MAXDATA=0. Specifying the DSA (Dynamic Segment Allocation) option tells the system loader to run applications using Very Large Program Support. The DSA option is only valid for 32-bit applications. Specifying the PRIVSEG_LOADS option directs the system loader to put dynamically loaded private modules into the process private segment. This might improve the availability of memory in large memory model applications that perform private dynamic loads and tend to run out of memory in the process heap. If the process private segment lacks sufficient space, the PRIVSEG_LOADS option has no effect. The PRIVSEG_LOADS option is only valid for 32-bit applications with a non-zero MAXDATA value. ------- Note 4: ------- http://www.freshblurbs.com/explaining-java-lang-outofmemoryerror-permgen-space Explaining java.lang.OutOfMemoryError: PermGen space Thu, 05/19/2005 - 07:00. Tags: java performance Most probably, a lot of Java developers have seen OutOfMemory error one time or other. However these errors come in different forms and shapes. The more common is: "Exception in thread "main" java.lang.OutOfMemoryError: Java heap space" and indicates that the Heap utilization has exceeded the value set by -Xmx. This is not the only error message, of this type, however. One more interesting flavor of the same error message, less common but hence even more troublesome is: "java.lang.OutOfMemoryError: PermGen space". Most of the memory profiler tools are unable to detect this problem, so it is even more troublesome and therefor - interesting. To understand this error message and fix it, we have to remember that, for optimized, more efficient garbage-collecting Java Heap is managed in generations - memory segments holding objects of different ages. Garbage collection algorithms in each generation are different. Objects are allocated in a generation for younger objects - the Young Generation, and because of infant mortality most objects die there. When the young generation fills up it causes a Minor Collection. Assuming high infant mortality, minor collections are garbage-collected frequently. Some surviving objects are moved to a Tenured Generation. When the Tenured Generation needs to be collected there is a Major Collection that is often much slower because it involves all live objects. Each generation contains variables of different length of life and different GC policies are applied to them. There is a third generation too - Permanent Generation. The permanent generation is special because it holds meta-data describing user classes (classes that are not part of the Java language). Examples of such meta-data are objects describing classes and methods and they are stored in the Permanent Generation. Applications with large code-base can quickly fill up this segment of the heap which will cause java.lang.OutOfMemoryError: PermGen no matter how high your -Xmx and how much memory you have on the machine. Sun JVMs allow you to resize the different generations of the heap, including the permanent generation. On a Sun JVM (1.3.1 and above) you can configure the initial permanent generation size and the maximum permanent generation size. To set a new initial size on Sun JVM use the -XX:PermSize=64m option when starting the virtual machine. To set the maximum permanent generation size use -XX:MaxPermSize=128m option. If you set the initial size and maximum size to equal values you may be able to avoid some full garbage collections that may occur if/when the permanent generation needs to be resized. The default values differ from among different versions but for Sun JVMs upper limit is typically 64MB. Some of the default values for Sun JVMs are listed below. JDK 1.3.1_06 Initial Size Maximum Size Client JVM 1MB 32MB Server JVM 1MB 64MB JDK 1.4.1_01 Initial Size Maximum Size Client JVM 4MB 64MB Server JVM 4MB 64MB JDK 1.4.2 Initial Size Maximum Size Client JVM 4MB 64MB Server JVM 16MB 64MB JDK 1.5.0 Initial Size Maximum Size Client JVM 8MB 64MB Server JVM 16MB 64MB Following is a JSP code you can use to monitor memory utilization in different generations (including PermGen): <%@ page import="java.lang.management.*" %> <%@ page import="java.util.*" %> JVM Memory Monitor <% Iterator iter = ManagementFactory.getMemoryPoolMXBeans().iterator(); while (iter.hasNext()) { MemoryPoolMXBean item = (MemoryPoolMXBean) iter.next(); %> <% Iterator iter = ManagementFactory.getMemoryPoolMXBeans().iterator(); while (iter.hasNext()) { MemoryPoolMXBean item = (MemoryPoolMXBean) iter.next(); %> <% } %>

Memory MXBean

Heap Memory Usage<%= ManagementFactory.getMemoryMXBean().getHeapMemoryUsage() %>
Non-Heap Memory Usage<%= ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage() %>
 

Memory Pool MXBeans

<%= item.getName() %>
Type<%= item.getType() %>
Usage<%= item.getUsage() %>
Peak Usage<%= item.getPeakUsage() %>
Collection Usage<%= item.getCollectionUsage() %>
 
As of JBoss v3.2.8/4.0.2, the ServerInfo MBean registered under the name jboss.system:type=ServerInfo has been enhanced with a new operation listMemoryPools(boolean fancy) that presents information about the memory pools managed by the JVM. 3.2: javax.naming.NameNotFoundException: ======================================== ------- Note 1: ------- As the error already suggest, the "NameNotFound" suggests that "whatever structure" is called or referenced at a certain time, it just cannot be found or resolved. This can be caused by nummerous reasons, like for example not having set a resource link properly in some Application server, or a binding issue, or a repository/describing .xml file that's missing information, etc.. In most cases, you should try to follow this lead, and browse trough all relevant logfiles. ------- Note 2: ------- 3.3: javax.servlet.ServletException: ==================================== 3.4. java.lang.StringIndexOutOfBoundsException: =============================================== 3.5. java.net.SocketException: ============================== 3.6. java.io.IOException: ========================= 3.7. java.io.FileNotFoundException: =================================== 3.8. java.util.MissingResourceException: ======================================== 3.9. java.lang.ClassNotFoundException: ====================================== 3.10.java.lang.StringIndexOutOfBoundsException: =============================================== 3.11.java.io.InterruptedIOException: ==================================== 3.12.java.lang.NullPointerException: ==================================== ============================================= SECTION 4: Listing of IBM JVM Errors: ============================================= JVMCI001OutOfMemoryError, allocating a JNI global ref Explanation: A call to jni_NewGlobalRef() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java™ -Xmx option. JVMCI002OutOfMemoryError, stAllocObject for jni_AllocObject failed Explanation: A call to jni_AllocObject() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI003OutOfMemoryError, stAllocArray for jni_NewString failed Explanation: A call to jni_NewString() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI004OutOfMemoryError, stAllocObject for jni_NewString failed Explanation: A call to jni_NewString() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI005OutOfMemoryError, dcUTF2JavaString failed Explanation: A call to jni_NewStringUTF() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI006OutOfMemoryError, dcUnicode2UTF failed Explanation: A call to jni_GetStringUTFChars() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI007OutOfMemoryError, stAllocArray for jni_NewObjectArray failed Explanation: A call to jni_NewObjectArray() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI008OutOfMemoryError, eeGetFromJNIEnv failed Explanation: A call to jni_New##type##Array() has failed because not enough memory is available. ##type## can be any of: Boolean, Byte, Short, Char, Int, Long, Float, or Double. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI009OutOfMemoryError, IBMJVM_NewArray - stAllocArray for new array failed Explanation: A call to IBMJVM_NewArray() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI010OutOfMemoryError, sysMalloc failed Explanation: The invocation of a native method needed a buffer that is larger then the default preallocated 256 bytes, but was Unable to get enough storage. System action: The JVM throws an OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI011OutOfMemoryError, can't create a new array Explanation: JVM_GetClassSigners failed to get storage by way of stAllocArray. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI012OutOfMemoryError, stAllocArray failed Explanation: JVM_GetStackAccessControlContex failed to get storage by way of stAllocArray. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI013OutOfMemoryError, create clone failed Explanation: Object.clone() failed to get storage for an object. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI014OutOfMemoryError, stAllocArray failed Explanation: Object.clone() failed to get storage for an array. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI015OutOfMemoryError, cannot create any more threads due to memory or resource constraints Explanation: JVM_StartThread() call to xmCreateThread() returned either SYS_NOMEM or SYS_NORESOURCE. System action: The JVM throws an OutOfMemoryError. User response: Either not enough resources are available to create a new threads, or the C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. For z/OS the most common cause of this error is if MAXTHREADS or MAXTHREADTASKS in SYS1.PARMLIB member BPXPRMxx is set to too small a value. The smaller of these values limits the number of pthreads that can be created for a single process. Enter SETOMVS MAXTHREADS=n or SETOMVS MAXTHREADTASKS=n to change the values without requiring an IPL. For z/OS this error might also be caused by using BELOW instead of ANYWHERE on a LE run-time option, for example, ANYHEAP STACK or THREADSTACK. If the application is run with the LE run-time option RPTOPTS(ON), the LE run-time options are written to stderr on completion. JVMCI016OutOfMemoryError, stAllocArray failed Explanation: JVM_GetClassContext failed to get storage by way of stAllocArray. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI017OutOfMemoryError, can't allocate new object Explanation: JVM_AllocateNewObject failed to get storage by way of stAllocArray. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI018OutOfMemoryError, can't allocate new array Explanation: JVM_AllocateNewArray failed to get storage by way of stAllocArray. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI019OutOfMemoryError, can't allocate object Explanation: JVM_NewInstanceFromConstructor failed to get storage by way of stAllocArray. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI020OutOfMemoryError, stInternString failed Explanation: JVM_InternString failed to either locate a matching string, or add a new string. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI021OutOfMemoryError, translating exception message Explanation: Either not enough Java Stack is available, or cannot find C-to-Java-string converter NewStringJVMPlatform. System action: The JVM throws an OutOfMemoryError. User response: Specify a larger Java stack size when you start the JVM; for example, by using the Java -Xoss option. JVMCI022Cannot allocate memory in jvmpi_calloc Explanation: Profiler Interface could not get enough storage. System action: The JVM prints the message "**Out of Memory, aborting**" and terminates abnormally. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI023Cannot allocate memory to collect heap dump in jvmpi_heap_dump Explanation: Profiler Interface could not get enough storage. System action: The JVM prints the message "**Out of Memory, aborting**" and terminates abnormally. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI024Cannot allocate memory to collect heap dump in jvmpi_monitor_dump Explanation: Profiler Interface could not get enough storage. System action: The JVM prints the message .**Out of Memory, aborting**. and terminates abnormally. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI025 Unable to open options file %filename Explanation: JNI_CreateJVM initialization detected the -Xoptionsfile option, but could not open the specified file. System action: JNI_CreateJVM returns -1, to indicate that initialization of the JVM failed. User response: Ensure that -Xoptionsfile specifies a valid file that the JVM can read. JVMCI026 Unable to determine the size of the options file %filename Explanation: JNI_CreateJVM initialization detected the -Xoptionsfile option, but could not obtain size information about the specified file by using fseek(fd,0L,SEEK_END) and ftell(fd). System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Ensure that -Xoptionsfile specifies a valid file that is not a socket or PIPE. JVMCI027 Unable to obtain memory to process %filename Explanation: JNI_CreateJVM initialization detected the -Xoptionsfile option, but could not allocate memory that is equal to the size of the specified file. System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: Check the size of the file that -Xoptionsfile specifies. The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI028Error reading options file: %filename fread() returns %filesize: %strerror(errno) Explanation: JNI_CreateJVM initialization detected the -Xoptionsfile option, but could not read the specified file by using fread(). System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Investigate the description for the given errno, and ensure that -Xoptionsfile specifies a valid file that is not a socket or PIPE. JVMCI029 Unable to obtain memory Explanation: JNI_CreateJVM initialization detected the -Xoptionsfile option, but could not allocate memory that is equal to the size of the specified file plus the string " -Xoptionsfile=". System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: Check the size of the file that -Xoptionsfile specified. The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI030Bad entry in options file: %filename Explanation: JNI_CreateJVM initialization parsed the contents of the file that the -Xoptionsfile option specified, and expected to find an option string beginning with the character "-". System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Check the contents of the file that -Xoptionsfile specified. JVMCI031Bad entry in options file: %filename Explanation: JNI_CreateJVM initialization parsed the contents of the file that the -Xoptionsfile option specified, and expected to find an option string beginning with the character "-". System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Check the contents of the file that -Xoptionsfile specified. JVMCI032Error parsing system properties within options file - rc=%rc Explanation: JNI_CreateJVM initialization parsed the contents of the file that the -Xoptionsfile option specified, and found a problem while parsing a system property. System action: JNI_CreateJVM returns a negative number to indicate that initialization of the JVM failed. User response: Check the contents of the file that -Xoptionsfile specified. JVMCI033Error parsing java options within options file - rc=%rc Explanation: JNI_CreateJVM initialization parsed the contents of the file that the -Xoptionsfile option specified, and found a problem while parsing a Java option setting. System action: JNI_CreateJVM returns a negative number to indicate that initialization of the JVM failed. User response: Check the contents of the file that -Xoptionsfile specified. JVMCI034Cannot allocate memory during JVM initialization Explanation: JVM_StartThread attempted to create a new thread before JNI_CreateJVM was complete. System action: The JVM prints the message "**Out of Memory, aborting**" and terminates abnormally. User response: Determine why Thread.start() has been invoked before initialization of the JVM is complete. JVMCI035Cannot override bootclasspath in Worker JVM Explanation: In a shared class environment, JNI_CreateJVM initialization parsed the properties that were specified for a Worker JVM, and found a setting for either "java.endorsed.dirs" or "ibm.jvm.bootclasspath". System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Check the properties that are specified for Worker JVMs. JVMCI037Cannot use debugger (-Xdebug) with shared classes (-Xjvmset) Explanation: In a shared class environment, JNI_CreateJVM initialization does not allow -Xdebug to be specified. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Do not specify the java -Xdebug option in conjunction with -Xjvmset. JVMCI038Out of Shared Memory on property storage allocation Explanation: In a shared class environment, JNI_CreateJVM initialization failed to allocate shared memory for the purpose of copying shared system properties across the JVMSet. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Refer to the shared classes User Guide for options that control shared memory. JVMCI039Out of Shared Memory on property storage allocation Explanation: In a shared class environment, JNI_CreateJVM initialization failed to allocate shared memory for the purpose of copying shared system properties across the JVMSet. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Refer to the shared classes User Guide for options that control shared memory. JVMCI040Cannot configure system property %sharedpropertyname in Worker JVM Explanation: In a shared class environment, JNI_CreateJVM initialization found, for the specified property, an existing entry that is not allowed to be overwritten. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Remove duplicate references to the specified system property. JVMCI041unsafe get/set Explanation: A trusted system class has invoked Unsafe.getObject() with a NULL object. System action: The JVM throws a NullPointerException. User response: Contact your IBM® service representative. JVMCI042unsafe get/set Explanation: A trusted system class has invoked Unsafe.putObject() with a NULL object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI043unsafe get/set Explanation: A trusted system class has invoked Unsafe.get##type() with a NULL object. ##type## can be any of: Boolean, Byte, Short, Char, Int, or Float. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI044unsafe get/set Explanation: A trusted system class has invoked Unsafe.put##type() with a NULL object. ##type## can be any of: Boolean, Byte, Short, Char, Int, or Float. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI045Illegal size passed to allocateMemory Explanation: A trusted system class has invoked Unsafe.allocateMemory() with a negative size. System action: The JVM throws an IllegalArgumentException. User response: Contact your IBM service representative. JVMCI046allocateMemory failed Explanation: A trusted system class has invoked Unsafe.allocateMemory(), but it could not get enough storage. System action: The JVM throws an OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI047Illegal size passed to reallocateMemory Explanation: A trusted system class has invoked Unsafe.reallocateMemory() with a negative size. System action: The JVM throws an IllegalArgumentException. User response: Contact your IBM service representative. JVMCI048reallocateMemory failed Explanation: A trusted system class has invoked Unsafe.reallocateMemory(), but it could not get enough storage. System action: The JVM throws an OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI049Illegal size passed to copyMemory Explanation: A trusted system class has invoked Unsafe.copyMemory() with a negative size. System action: The JVM throws an IllegalArgumentException. User response: Contact your IBM service representative. JVMCI050Illegal size passed to setMemory Explanation: A trusted system class has invoked Unsafe.setMemory() with a negative size. System action: The JVM throws an IllegalArgumentException. User response: Contact your IBM service representative. JVMCI051Null field passed to staticFieldOffset Explanation: A trusted system class has invoked Unsafe.staticFieldOffset() with a NULL field object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI052defineClass Explanation: A trusted system class has invoked Unsafe.defineClass() with a NULL byte array. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI053defineClass Explanation: A trusted system class has invoked Unsafe.defineClass() with a with a negative length argument. System action: The JVM throws an ArrayIndexOutOfBoundsException. User response: Contact your IBM service representative. JVMCI054defineClass Explanation: A trusted system class has invoked Unsafe.defineClass(), but could not get enough storage. System action: The JVM throws an OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI055Cannot allocate assertion directives Explanation: Cannot allocate space for an instance of class AssertionStatusDirectives. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI056Cannot allocate assertion directives Explanation: Cannot allocate space for an instance of class AssertionStatusDirectives. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI057Cannot allocate assertion directives Explanation: Cannot allocate space for an instance of class AssertionStatusDirectives. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI058Unsafe_StaticFieldBase Explanation: A trusted system class has invoked Unsafe.staticFieldBase() with a NULL field object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI059Unsafe_EnsureClassInitialized Explanation: A trusted system class has invoked Unsafe.ensureClassInitialized() with a NULL class object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI060Unsafe_ArrayBaseOffSet Explanation: A trusted system class has invoked Unsafe.arrayBaseOffSet() with a non-array class. System action: The JVM throws an InvalidClassException. User response: Contact your IBM service representative. JVMCI061Unsafe_ArrayIndexScale Explanation: A trusted system class has invoked Unsafe.arrayIndexScale() with a non-array class. System action: The JVM throws an InvalidClassException. User response: Contact your IBM service representative. JVMCI062holdsLock Explanation: Thread.holdsLock() has been invoked with a NULL object argument. System action: The JVM throws a NullPointerException. User response: Examine invocations of Thread.holdsLock(). If you cannot solve the problem, contact your IBM service representative. JVMCI063OutOfMemoryError, GetStringChars failed Explanation: A call to jni_getStringChars() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI064unsafe getLong Explanation: A trusted system class has invoked Unsafe.getLong() with a NULL object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI065unsafe putLong Explanation: A trusted system class has invoked Unsafe.putLong() with a NULL object. System action: The JVM throws a NullPointerException. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI066unsafe getDouble Explanation: A trusted system class has invoked Unsafe.getDouble() with a NULL object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI067unsafe putDouble Explanation: A trusted system class has invoked Unsafe.putDouble() with a NULL object. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI068Cannot set system assertion status in Worker JVM Explanation: In a shared class environment, JNI_CreateJVM initialization parsed the properties that were specified for a Worker JVM, and found either -enablesystemassertions or -disablesystemassertions. Worker JVMs are not permitted to set these options. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Ensure that the properties that are specified for Worker JVMs do not include Java assert options. For help on assert options, run java -assert. JVMCI069Cannot set shared class maximum option -Xscmax in a Worker JVM Explanation: In a shared class environment, JNI_CreateJVM initialization parsed the properties that were specified for a Worker JVM, and found -Xscmax. Worker JVMs are not permitted to set this option. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Ensure that the properties that are specified for Worker JVMs do not include the Java option -Xscmax. JVMCI070JVMMI object enumeration - invalid class found at 0x%objectpointer Explanation: The monitoring interface was invoked to list objects in the heap, but could not obtain class information for an object. System action: The callback function for this object is not called and no further information is produced for this object. Enumeration continues with the next object in the heap. User response: Contact your IBM service representative. JVMCI071JVMMI object enumeration - object at 0x%objectpointer has null class block Explanation: The monitoring interface was invoked to list objects in the heap, but found a NULL class block for an object. System action: The callback function for this object is not called and no further information is produced for this object. Enumeration continues with the next object in the heap. User response: Contact your IBM service representative. JVMCI072JVMMI object enumeration - unrecognized array object at 0x%objectpointer Explanation: The monitoring interface was invoked to list objects in the heap, and determined that an object was a multidimensional primitive array, but could not determine the type of one of the dimensions. System action: The callback function for this object is not called, and enumeration continues. User response: Contact your IBM service representative. JVMCI073JVMMI object enumeration - unrecognized primitive array at 0x%objectpointer Explanation: The monitoring interface was invoked to list objects in the heap, and determined that an object was an array, but could not determine the type of array. System action: The callback function for this object is not called, and enumeration continues. User response: Contact your IBM service representative. JVMCI074Cannot allocate memory in jvmpi_interface Explanation: The monitoring interface could not get enough storage. System action: The JVM prints the message "**Out of Memory, aborting**" and terminates abnormally. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI075Cannot allocate memory in jvmpi_dump_object_event Explanation: The monitoring interface could not get enough storage. System action: The JVM prints the message "**Out of Memory, aborting**" and terminates abnormally. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI076JVM is requesting a heap dump Explanation: The monitoring interface was invoked to generate a dump of the heap. System action: A heap dump is requested. User response: None. JVMCI077Heap dump complete Explanation: The monitoring interface has generated a dump of the heap. System action: A heap dump has been generated. User response: None. JVMCI078NullPointerException, mangleMethodName passed NULL MethodBlock Explanation: During the invocation of a native method, a NULL method block was found. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI079NullPointerException, maxMangledMethodNameLength passed NULL MethodBlock Explanation: During the invocation of a native method, a NULL method block was found. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI080SetMirroredProtectionDomains NULL cb Explanation: SecureClassLoader.setMirroredProtectionDomain() was invoked with a NULL class. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI081Clone NULL this pointer Explanation: Object.clone() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI082GetClassLoader NULL cb Explanation: Class.getClassLoader() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI083IsInterface NULL cb Explanation: Class.isInterface() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI084GetClassSigners NULL cb Explanation: Class.getClassSigners() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI085SetClassSigners NULL cb Explanation: Class.setClassSigners() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI086GetProtectionDomain NULL cb Explanation: Class.getProtectionDomain() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI087SetProtectionDomain NULL cb Explanation: Class.setProtectionDomain() "this" instance is NULL. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI088OutOfMemoryError, _CharToByteLength cannot obtain TLS Explanation: A call to _CharToByteLength() has failed because it could not get thread local storage. System action: The JVM throws an OutOfMemoryError. _CharToByteLength() returns -2. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI089OutOfMemoryError, _CharToByteLength cannot allocate cache Explanation: A call to _CharToByteLength() has failed because it could not allocate storage. System action: The JVM throws an OutOfMemoryError. _CharToByteLength() returns -2. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI090OutOfMemoryError, _CharToByteLength cannot allocate buffer Explanation: A call to _CharToByteLength() has failed because it could not allocate storage. System action: The JVM throws an OutOfMemoryError. _CharToByteLength() returns -2. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI091Null field passed to objectFieldOffset Explanation: Unsafe.ObjectFieldOffset() was invoked with a NULL field. System action: The JVM throws a NullPointerException. User response: Contact your IBM service representative. JVMCI092Out of Shared Memory on property storage allocation. Explanation: In a shared class environment, JNI_CreateJVM initialization failed to allocate shared memory for the copying of shared system properties across the JVMSet. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Refer to the shared classes User Guide for options that control shared memory. JVMCI093 Unable to load Core Interface - JVM Anchor Reference is missing Explanation: JNI_CreateJVM initialization found a null pointer to the JVM Anchor block. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI094 Unable to load Core Interface - JVM initialization argument is missing Explanation: JNI_CreateJVM initialization found a null pointer to the JVM initialization arguments. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI095JavaVM Init Args is not present, jvm pointer = %p Explanation: JNI_CreateJVM initialization found a null pointer to the JVM initialization arguments. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI096 Unable to load HPI - JVM initialization arguments missing Explanation: JNI_CreateJVM initialization found a null pointer to the JVM initialization arguments. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI097JVM Instance is not present Explanation: JNI_CreateJVM initialization found a null pointer to the JVM Anchor block. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI098xmloadJVMHelperLib %s %s, failed Explanation: JNI_CreateJVM initialization could not load the indicated shared library with its associated options. Message JVMCI158 might also be printed. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI099 Unable to trace user arguments - JVM Instance is not present Explanation: JNI_CreateJVM initialization found a null pointer to the JVM Anchor block. System action: JNI_CreateJVM continues, but without tracing user arguments. User response: Contact your IBM service representative. JVMCI100 Unable to trace user arguments - no arguments supplied, jvm pointer = %p Explanation: JNI_CreateJVM initialization found a null pointer to the JVM initialization arguments. System action: JNI_CreateJVM continues, but without tracing user arguments. User response: Contact your IBM service representative. JVMCI101Property Table is not present Explanation: JNI_CreateJVM initialization found a null pointer to the JVM property table. System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI102Out of Memory on property storage allocation Explanation: JNI_CreateJVM initialization could not allocate storage for a property table entry. System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI103Out of Memory on property add Explanation: JNI_CreateJVM initialization could not allocate storage for a property table entry name or value field. System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI104Failed to locate entry point %s Explanation: JNI_CreateJVM initialization could not locate an entry point named ciInit in the Core Interface Library that was specified with the -Dibm.load.ci= argument. System action: JNI_CreateJVM continues, but with the default core interface. User response: Check whether the library that was specified by -Dibm.load.ci= contains an entry point for ciInit. JVMCI106Failed to find library %s Explanation: JNI_CreateJVM initialization could not locate the core interface library that was specified with the -Dibm.load.ci= argument. System action: JNI_CreateJVM continues, but with the default core interface. User response: Check whether the library that was specified by -Dibm.load.ci= is accessible to the JVM. JVMCI107 Unable to allocate memory for Library Name Property Explanation: JNI_CreateJVM initialization could not allocate storage to store the string ibm.load.XX.nt. System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI108 Unable to allocate memory for Initial Function Name Explanation: JNI_CreateJVM initialization could not allocate storage to store the string xxInit. System action: JNI_CreateJVM returns -4 to indicate that initialization of the JVM failed. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI109No initialization point found for sub component %s Explanation: JNI_CreateJVM initialization could not locate a default initialization entry point of the form xxInit for the indicated sub component xx. System action: JNI_CreateJVM attempts to continue. User response: Contact your IBM service representative. JVMCI110ciFacade is not present Explanation: JNI_CreateJVM initialization found a null pointer to the JVM core interface facade. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI111ciFacade version is not supported %d Explanation: JNI_CreateJVM initialization found an nonvalid version number as indicated. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI112Unrecognized JNI version: 0x%08x Explanation: JNI_CreateJVM initialization found an nonvalid version number as indicated. System action: JNI_CreateJVM returns -3 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI113Cannot obtain iconv converters Explanation: JNI_CreateJVM initialization could not initialize iconv converters. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI114Cannot obtain system-specific information Explanation: JNI_CreateJVM initialization could not obtain system properties (home directory/DLL directory/system classpath, calculated from the location of libjava.so). System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI115IBM_JAVA_OPTIONS error Explanation: JNI_CreateJVM initialization could not obtain storage to store the value of the IBM_JAVA_OPTIONS environment variable. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCI116Error setting JVM default options - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Check the options that are passed to the JVM. If you cannot solve the problem, contact your IBM service representative. JVMCI117Bad IBM_JAVA_OPTIONS: %s Explanation: JNI_CreateJVM initialization expects options to begin with a "-" (hyphen). System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Check the options that are passed to the JVM. If you cannot solve the problem, contact your IBM service representative. JVMCI118Error parsing IBM_JAVA_OPTIONS system properties - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Check the options that are passed to the JVM. If you cannot solve the problem, contact your IBM service representative. JVMCI119Error parsing IBM_JAVA_OPTIONS java options - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Check the options that are passed to the JVM. If you cannot solve the problem, contact your IBM service representative. JVMCI120 Unable to parse System Properties - no argument supplied, jvm pointer = %p Explanation: JNI_CreateJVM initialization found a null pointer to the JVM initialization arguments. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI121 Unable to parse 1.2 format System Properties - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Check the options that are passed to the JVM. If you cannot solve the problem, contact your IBM service representative. JVMCI122 Unable to parse supplied options - no argument supplied, jvm pointer = %p Explanation: JNI_CreateJVM initialization found a null pointer to the JVM initialization arguments. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI123 Unable to parse 1.2 format supplied options - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Check the options that are passed to the JVM. If you cannot solve the problem, contact your IBM service representative. JVMCI124Bad Service Option: %s Explanation: JNI_CreateJVM initialization expects individual options to begin with a "-" (hyphen). System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Examine the -Xservice= options that are indicated in the message. Correct as necessary. JVMCI125Bad Service Option: %s Explanation: JNI_CreateJVM initialization expects individual options to begin with a "-" (hyphen). System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Examine the -Xservice= options that are indicated in the message. Correct as necessary. JVMCI126Error parsing Service system properties - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Examine the -Xservice= options that are indicated in the message. Correct as necessary. JVMCI127Error parsing Service java options - rc=%d Explanation: JNI_CreateJVM initialization detected an error while parsing JVM options. This message might be preceded by other, more-specific messages. System action: JNI_CreateJVM returns the code that is shown in the message, to indicate that initialization of the JVM failed. User response: Examine the -Xservice= options that are indicated in the message. Correct as necessary. JVMCI128Illegal option: %s Explanation: JNI_CreateJVM initialization detected a -verbose option that had no following "." (period) character. The string that follows -verbose is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -verbose: options that are passed to the JVM. Correct as necessary. JVMCI129Unrecognized verbose option: %s Explanation: JNI_CreateJVM initialization detected a -verbose option that had no valid option following the "." (period) character. The string that follows -verbose is shown in the message System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -verbose options that are passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI130Illegal option: %s Explanation: JNI_CreateJVM initialization detected an -verify option that had no valid option following. The string following -verify is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -verify option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI131Invalid number of threads: %s Explanation: JNI_CreateJVM initialization detected an -Xgcthreads option that had no positive integer following. The string that follows -Xgcthreads is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xgcthreads option that is passed to the JVM. Correct as necessary. JVMCI133Bad concurrent GC level: %s Explanation: JNI_CreateJVM initialization detected an -Xconcurrentlevel option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xconcurrentlevel is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xconcurrentlevel option that is passed to the JVM. Correct as necessary. JVMCI134Incorrect usage of -Xverbosegclog Explanation: JNI_CreateJVM initialization detected an -Xverbosegclog option that had no valid suboptions following. The string that follows -Xverbosegclog is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xverbosegclog option that is passed to the JVM. Correct as necessary. JVMCI135Illegal option: %s Explanation: JNI_CreateJVM initialization detected an -Xgcpolicy option that had no suboptions following. The string that follows -Xgcpolicy is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xgcpolicy option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI136Illegal option: %s Explanation: JNI_CreateJVM initialization detected an -Xgcpolicy option that had no valid suboption following. The string that follows -Xgcpolicy is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xgcpolicy option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI137Bad native stack size: %s Explanation: JNI_CreateJVM initialization detected an -Xss option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. Size must be equivalent to, or greater than, 1000 bytes. The string that follows -Xss is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xss option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI138Bad Java stack size: %s Explanation: JNI_CreateJVM initialization detected an -Xoss option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. Size must be equivalent to, or greater than, 1000 bytes. The string that follows -Xoss is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xoss option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI139Bad init heap size: %s Explanation: JNI_CreateJVM initialization detected an -Xms option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xms is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xms option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI140Bad max heap size: %s Explanation: JNI_CreateJVM initialization detected an -Xmx option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xmx is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xmx option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI141Bad maxHeapFreePercent size: %s Explanation: JNI_CreateJVM initialization detected an -Xmaxf option that had no valid value following. Valid values are 0 and 1. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xmaxf option that is passed to the JVM. Correct as necessary. JVMCI142Bad minHeapFreePercent size: %s Explanation: JNI_CreateJVM initialization detected an -Xminf option that had no valid value following. Valid values are 0 and 1. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xminf option that is passed to the JVM. Correct as necessary. JVMCI143Bad maxHeapExpansion size: %s Explanation: JNI_CreateJVM initialization detected an -Xmaxe option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xmaxe is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xmaxe option that is passed to the JVM. Correct as necessary. JVMCI144Bad minHeapExpansion size: %s Explanation: JNI_CreateJVM initialization detected an -Xmine option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xmine is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xmine option that is passed to the JVM. Correct as necessary. JVMCI146Bad initial Transient heap size: %s Explanation: In a shared class environment, JNI_CreateJVM initialization detected an -Xinitth option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xinitth is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xinitth option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI147Bad initial System heap size: %s Explanation: In a shared class environment, JNI_CreateJVM initialization detected an -Xinitsh option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xinitsh is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xinitsh option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI148Bad initial ACS heap size: %s Explanation: In a shared class environment, JNI_CreateJVM initialization detected an -Xinitacsh option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xinitacsh is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xinitacsh option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI149Bad shared memory size: %s Explanation: In a shared class environment, JNI_CreateJVM initialization detected a Master JVM -Xjvmset option that had no valid size following. You can specify sizes as a positive integers that are optionally suffixed with K, M or G to indicate units of KB, MB, or GB. The string that follows -Xjvmset is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xjvmset option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI150Invalid use of %s option Explanation: In a shared class environment, JNI_CreateJVM initialization detected a Worker JVM -Xjvmset option that had suboptions following. You must not specify suboptions for a Worker JVM. The string that follows -Xjvmset is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xjvmset option that is passed to the JVM. Correct as necessary. You can list valid options by running java -?. JVMCI151Invalid shared class option setting: %s Explanation: JNI_CreateJVM initialization detected an -Xscmax option that had no valid size following. Size must be a positive integer 2048 through 1048576. The string that follows -Xscmax is shown in the message. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xscmax option that is passed to the JVM. Correct as necessary. JVMCI152Invalid option : %s Explanation: JNI_CreateJVM initialization detected one of the -ea, -enableassertions, -da, or -disableassertions options that had no following "." (period) character. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the assert options that are passed to the JVM. Correct as necessary. You can list valid options by running java -assert. JVMCI153Invalid option, optionString pointer is null Explanation: JNI_CreateJVM initialization detected an option that started with -X, but had no further value. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the assert options that are passed to the JVM. Correct as necessary. You can list valid options by running java -assert. JVMCI155Specified options prevent use of JIT Explanation: JNI_CreateJVM initialization detected either the -Xt or the -Xmt option, and has disabled the JIT compiler.. System action: JNI_CreateJVM continues with the JIT compiler disabled. User response: None. JVMCI156OutOfMemoryError, IBMJVM_ResizeArray - stAllocArray for new array failed Explanation: A call to ExtendedSystem.resizeArray() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI157OutOfMemoryError, stClonePrimitiveArrayToSystemHeap for GetSystemHeapArray() failed Explanation: A call to ClassLoader.getSystemHeapArray() has failed because not enough memory is available. System action: The JVM throws an OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Xmx option. JVMCI158Can't load %s, because %s Explanation: JNI_CreateJVM initialization could not load the indicated shared library because of the reason indicated. Message JVMCI098 might also be printed. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI159 Unable to initialize JVM helper library %s Explanation: JNI_CreateJVM initialization could not call the OnLoad() entry point for the indicated shared library. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI160Corrupted JVM helper library %s Explanation: JNI_CreateJVM initialization could not call the OnLoad() entry point for the indicated shared library. System action: JNI_CreateJVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI161FATAL ERROR in native method: %s Explanation: A JNI function has found an unrecoverable error. Information that is specific to the error is included in the message. System action: The JVM prints a Java stack trace and ends. Dumps might be produced, depending upon the setting of the JAVA_DUMP_OPTS environment variable. User response: Examine the message detail and Java stack trace to determine the possible cause of the error. If you cannot solve the problem, contact your IBM service representative. JVMCI162Profiler error Explanation: JNI_CreateJavaVM has determined that the profiling interface is not initialized. System action: JNI_CreateJavaVM returns -1 to indicate that initialization of the JVM failed. User response: Contact your IBM service representative. JVMCI163Illegal string length in JVMMI heapdump Explanation: A string is greater than the maximum JVMMI reference buffer size of 1024 bytes. System action: The string is ignored and the JVM attempts to continue. User response: Contact your IBM service representative. JVMCI164Illegal option: %s Explanation: JNI_CreateJVM initialization detected a -Xifa option that had no valid value following. Valid values are on, off, force & project. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xifa option that is passed to the JVM. Correct as necessary JVMCI165Illegal option specified %s Explanation: JNI_CreateJVM initialization detected a -Xk option that had an invalid number of classes specified. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xk option that is passed to the JVM. Correct as necessary. JVMCI166Illegal option specified %s Explanation: JNI_CreateJVM initialization detected a -Xp option that had an invalid format for the following pCluster specification. The expected format is -Xp[,], where specifies the size of the initial pCluster in bytes and optionally specifies the size of overflow (subsequent) pClusters in bytes. You can use the K and M suffixes to set the -Xp arguments in Kilobytes and Megabytes. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xp option that is passed to the JVM. Correct as necessary. JVMCI167Bad pCluster initial size %s Explanation: JNI_CreateJVM initialization detected a -Xp option that had an invalid initial pCluster size specified. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xp option that is passed to the JVM. Correct as necessary. JVMCI168Bad pCluster overflow size %s Explanation: JNI_CreateJVM initialization detected a -Xp option that had an invalid overflow pCluster size specified. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xp option that is passed to the JVM. Correct as necessary. JVMCI169Initial pCluster size less than pCluster overflow %s Explanation: JNI_CreateJVM initialization detected a -Xp option of the form -Xpiiii[K][,oooo[K]] where iiii is less than oooo. System action: JNI_CreateJVM returns -6 to indicate that initialization of the JVM failed. User response: Examine the -Xp option that is passed to the JVM. Correct as necessary. JVM error messages for JVMCL JVMCL001OutOfMemoryError, dcUTF2JavaString failed Explanation: During the resolution of a Java™ constant pool string, the function that converts a UTF string type to an internal Java string type failed and returned a NULL value because of a lack of Java heap memory. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Mx option. JVMCL002OutOfMemoryError, stInternString failed Explanation: During the resolution of a Java constant pool string, the function that resolves a Java string to a single and unique equivalent inside the JVM failed and returned a NULL value because of a lack of Java heap memory. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap when you start the JVM; for example, by using the Java -Mx option. JVMCL003OutOfMemoryError, Unable to allocate storage for MethodTable Explanation: The system memory calloc (or shared memory alloced for a shared class in the sharable JVM) that was used to get storage for a method table has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. In a shared classes environment, see the shared classes User Guide for options that control shared memory. JVMCL004OutOfMemoryError, Unable to allocate storage for offset vector Explanation: While laying out the fields of a Java class in memory, storage is requested for the list of offsets of each field in the class. Not enough memory is available to honor this request. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL005OutOfMemoryError, Unable to allocate storage for interface table Explanation: The system memory calloc (or shared memory allocated for a shared classes environment in the sharable JVM) that was used to get storage for a interface table has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL006OutOfMemoryError, Unable to allocate storage for MethodBlock Explanation: The system memory calloc (or shared memory alloced for a shared classes in the sharable JVM) that was used to get storage for a (miranda) method block has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL007OutOfMemoryError, mbName returned NULL Explanation: The system memory alloc (or shared memory allocated for a shared classes in the sharable JVM) that was used to get storage for an entry in the cache of UTF8 strings has returned NULL during the preparation of a class-implemented method. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL008OutOfMemoryError, stAddToLoadedClasses failed Explanation: The function that adds a class object to the internal list in the JVM has failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL009OutOfMemoryError, sysMalloc for loading classes (file) failed Explanation: The malloc function that was used in class loading to create an internal buffer has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCL010OutOfMemoryError, sysMalloc for loading classes (zip) failed Explanation: The malloc function that was used in class loading to create an internal buffer has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCL011OutOfMemoryError, putPackage for loading classes (zip) failed Explanation: Adding a package table entry failed because of a lack of system memory (shared memory segment space in a shared classes environment). System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, the shared memory segment is full. See the sharable JVM documentation for information about how to increase the segment. JVMCL012OutOfMemoryError, allocation failed Explanation: Class allocation has failed for an array or primitive class. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Start the JVM with a larger maximum heap; for example, by using the Java -Mx option. In a shared classes environment the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for further information. JVMCL013OutOfMemoryError, Unable to allocate storage for pool buffer Explanation: The calloc system function (or classSharedMalloc in a sharable JVM environment) has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL014OutOfMemoryError, cbName returned NULL Explanation: Setting the class name of a class has failed, probably because of the inability to create a new UTF8 cache entry. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL015OutOfMemoryError, allocation of class mirror failed Explanation: The function that was used to allocate an unmovable byte array in the JVM has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL016OutOfMemoryError, jvmpi_load_class_hook returned NULL pointer Explanation: The JVMPI user-pluggable code has returned NULL in response to a class load event. System action: The JVM throws a java.lang.OutOfMemoryError. User response: If this is an unexpected result, investigate the code that uses the JVMPI interface to listen for the JVMPI CLASS_LOAD event. JVMCL017OutOfMemoryError, loading classes Explanation: A generic out of memory error has occurred. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. If this does not solve the problem, increase the process C-heap that is allocated to the JVM process, if possible. JVMCL018OutOfMemoryError, stAllocObject for new field instance failed Explanation: The Java heap is full. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL019OutOfMemoryError, stAllocArray for new array failed Explanation: The Java heap is full. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocate. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL020OutOfMemoryError, stAllocObject for new method failed Explanation: The Java heap is full. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL021OutOfMemoryError, stAllocObject for new constructor failed Explanation: The Java heap is full. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL022OutOfMemoryError, sysMalloc for inner classes failed Explanation: The malloc system function has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Contact your IBM® service representative. JVMCL023OutOfMemoryError, stAllocObject for new class failed Explanation: The Java heap is full. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL024OutOfMemoryError, add package to shared NameSpace failed Explanation: Both the Java system heap and alloced memory are needed to add a package to the shared name space and one of this cannot provide enough storage to do so. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL027OutOfMemoryError, allocating an array of objects Explanation: An unrecoverable internal processing error has occurred in the JVM. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL028OutOfMemoryError, name of inner array class is NULL Explanation: An unrecoverable internal processing error has occurred in the JVM. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Contact your IBM service representative. JVMCL029OutOfMemoryError, inner class name is NULL (multi-D array) Explanation: An unrecoverable internal processing error has occurred in the JVM. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Contact your IBM service representative. JVMCL030OutOfMemoryError, add into loader cache failed Explanation: An unrecoverable internal processing error has occurred in the JVM. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL031Maximum number of shared classes exceeded, use -Xscmax command eline option to increase the limit. Explanation: This message is issued if an application attempts to load more than the specified number (or the default number, if the option was not specified) of shareable classes. These include shareable application classes, middleware classes, and system classes. A JVM set normally loads at least 1500 system classes during initialization. System action: The JVM set is terminated. User response: Review the number of shared classes that are being loaded by the application, and, if necessary, set the -Xscmax command line option on the Master JVM to increase the limit. JVMCL032OutOfMemoryError, clAddUTF8String failed Explanation: The operation to add a string to the JVM internal cache failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL033OutOfMemoryError, creation of loader shadow failed, or promoteLoaderCaches failed Explanation: The system calloc function that was used to get storage from the system has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL034OutOfMemoryError, sysMalloc for bigger buffer failed Explanation: The system malloc function has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCL035OutOfMemoryError, allocation failed Explanation: The loading of a Java class has failed because not enough storage is available. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL036OutOfMemoryError, stAllocObject failed in WRAP Explanation: The loading of a Java class has failed because not enough storage is available. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL037OutOfMemoryError, stAllocObject failed in WRAP2 Explanation: The loading of a Java class has failed because not enough storage is available. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. In a shared classes environment, the storage area that is full depends on the type of class that is being allocated. See the sharable JVM documentation for more information about how to increase the memory that is available for class storage. JVMCL038OutOfMemoryError, Unable to allocate a loader cache entry Explanation: The JVM has been Unable to allocate storage during Java class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL039OutOfMemoryError, failure allocating constraint spill area Explanation: The JVM has been Unable to allocate storage during Java class loading. The system malloc function has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMCL042OutOfMemoryError, Unable to allocate NameSpace storage Explanation: The JVM has run out of memory during class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL044OutOfMemoryError, Unable to add name space cache entry Explanation: The JVM has run out of memory during class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL045OutOfMemoryError, stInternString failed Explanation: The JVM has run out of memory during class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL046OutOfMemoryError, stInternString failed Explanation: The JVM has run out of memory during class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL048Illegal re-definition of class Explanation: Two concurrent attempts to load a class have caused different class objects to be resolved. The error has occurred because a race condition exists between two threads that have loaded the same class, and because an unstable underlying source of class definitions, such as .class files, has been changed. System action: A Java linkageError exception is thrown. User response: You can either synchronize or control the multithreaded nature of the class loading, or prevent loading from occurring while the underlying class sources are being changed. Because class loading in one class loader is synchronized, this error is more likely to occur if multiple class-loaders in a delegation chain become the defining loader for the class over time because of changes in the underlying bytecode source location. JVMCL049Illegal re-definition of class Explanation: Two concurrent attempts to load a class have caused different class objects to be resolved. The error has occurred because a race condition exists between two threads that have loaded the same class, and because an unstable underlying source of class definitions, such as .class files, has been changed. System action: A Java linkageError exception is thrown. User response: You can either synchronize or control the multithreaded nature of the class loading, or prevent loading from occurring while the underlying class sources are being changed. Because class loading in one class loader is synchronized, this error is more likely to occur if multiple class-loaders in a delegation chain become the defining loader for the class over time because of changes in the underlying bytecode source location. JVMCL050OutOfMemoryError, stInternString failed Explanation: The JVM has run out of memory during class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL051OutOfMemoryError, stInternString failed Explanation: The JVM has run out of memory during class loading. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL052Cannot allocate memory in initializeHeap for heap segment Explanation: The malloc function that was used to initialize a Heap segment has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL053Cannot allocate memory in allocHeap for heap segment Explanation: The malloc function that was used to allocate a Heap segment has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL054Cannot allocate memory in allocHeap for heap segment Explanation: The malloc function that was used to allocate a Heap segment has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL055Cannot allocate memory in initializeClassCache for context class table Explanation: The calloc function that was used to allocate memory for the class cache for the context class table has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL056Cannot allocate memory in expandClassTable for Class cache Explanation: The calloc function that was used to allocate memory for the newly expanded class cache table has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL057Cannot allocate memory in initializeCPTable for context shadow table Explanation: The calloc function that was used to allocate memory for the backing shadow table has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVMCL058Can't find class java.lang.NoClassDefFoundError. Explanation: This message can be caused by a number of system and configuration issues, such as the incorrect classpath. System action: Check that the classpath is correct. If there has been any system maintenance applied recently, please check the error logs. User response: The system action above should resolve this issue. JVMCL200Classloader system property Explanation: The calloc function that was used to allocate memory for the backing shadow table has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. In a shared classes environment, see the shared classes User Guide for options that control shared memory, because the storage is managed by the JVM in this case. JVM error messages for JVMDC JVMDC001OutOfMemoryError, stAllocArray for cString2JavaString failed Explanation: * The Java™ heap is full. An attempt to allocate an array of characters from the Java heap failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the java -Mx option. JVMDC002OutOfMemoryError, makeByteString failed Explanation: The Java heap is full. An attempt to allocate an array of bytes from the Java heap failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the java -Mx option. JVMDC003OutOfMemoryError, stAllocArray for utf2JavaString failed Explanation: The Java heap is full. An attempt to allocate an array of characters from the Java heap failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. JVMDC004OutOfMemoryError, stAllocObject for utf2JavaString failed Explanation: The Java heap is full. An attempt to allocate a java/lang/String object failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. JVMDC005OutOfMemoryError, stAllocArray for utfClassName2JavaString failed Explanation: The Java heap is full. An attempt to allocate an array of characters from the Java heap failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. JVMDC006OutOfMemoryError, stInternString failed Explanation: During the conversion of a utf string to a Java string, the function that resolves a Java string to a single and unique equivalent inside the JVM failed and returned a NULL value because of a lack of java heap memory. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. JVMDC007OutOfMemoryError, stAllocObject for utfClassName2JavaString failed Explanation: The Java heap is full. An attempt to allocate a java/lang/String object failed. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Use a larger maximum heap to start the JVM; for example, by using the Java -Mx option. JVMDC008OutOfMemoryError, sysMalloc failed Explanation: The malloc function that was used to create a new buffer has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVMDC009OutOfMemoryError, sysMalloc failed Explanation: The malloc function that was used to create a buffer used while converting a platform string to a utf8 class name has returned NULL. System action: The JVM throws a java.lang.OutOfMemoryError. User response: The C-runtime heap of the process (not the Java object heap) is full. Increase the heap if that is possible in your environment. JVM error messages for JVMDBG JVMDBG001malloc failed to allocate bytes, time Explanation: The system malloc function has returned NULL System action: None for this message. The JVM might issue a further message. User response: Increase the available native storage. JVMDBG002strndup failed to allocate bytes, time Explanation: The system strndup function has returned NULL System action: None for this message. The JVM might issue a further message. User response: Increase the available native storage. JVMDBG003strdup failed, time Explanation: The system strdup function has returned NULL System action: None for this message. The JVM might issue a further message. User response: Increase the available native storage. JVMDBG004calloc failed to allocate an array of elements at bytes each, time Explanation: The system calloc function has returned NULL System action: None for this message. The JVM might issue a further message. User response: Increase the available native storage. JVMDBG005realloc failed to allocate bytes, time Explanation: The system realloc function has returned NULL System action: None for this message. The JVM might issue a further message. User response: Increase the available native storage. JVM error messages for JVMDG JVMDG009RC %d from sysMonitorEnter in getTraceLock Explanation: Internal error. System action: None. User response: Contact your IBM® service representative. JVMDG010RC %d from sysMonitorExit in freeTraceLock Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG011RC %d from sysMonitorEnter in postWriteThread Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG012RC %d from sysMonitorNotify in postWriteThread Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG013RC %d from sysMonitorExit in postWriteThread Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG015Malloc failure in addTraceCmd Explanation: During processing of the user-supplied trace options, a call to malloc was made to obtain a block of memory. This call failed. System action: The JVM is terminated. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG032 Unable to open properties file %s Explanation: The JVM was Unable to open the properties file that was listed in the message. System action: The JVM is terminated. User response: Ensure that the properties file that you have specified really exists. If the problem remains, contact your IBM service representative. JVMDG033 Unable to determine size of properties file %s Explanation: Having opened the trace properties file mentioned in the message, the JVM was Unable to determine its size. System action: The JVM is terminated. User response: Ensure that the file that you specified is a valid properties file, and that it is readable. If the problem remains, contact your IBM service representative. JVMDG034Cannot obtain memory to process %s Explanation: To process the trace properties file, it is read into memory. Unfortunately, the call to obtain the memory for this failed. System action: The JVM is terminated. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG035Error reading properties file %s Explanation: To process the trace properties file, it is read into memory. Unfortunately, the call to read it into memory has failed. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMDG037Unrecognized line in %s: "%s" Explanation: While reading the trace properties file, a line has been found that contains a keyword that is not recognized. The properties file name and the offending line are included in the text of the message. System action: The JVM is terminated. User response: Correct the line in error and try again. JVMDG046RC %d from sysMonitorEnter in trace write thread Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG047RC %d from sysMonitorWait in trace write thread Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG048RC %d from sysMonitorExit in trace write thread Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG060Error starting trace write thread Explanation: The trace write thread is responsible for writing trace data to disk. It could not be started. System action: The trace data is not written to disk. User response: Ensure that you are not running into a system thread limit. If the problem remains, contact your IBM service representative. JVMDG070Syntax error encountered at offset %d in:%s Explanation: The way in which you have specified which components are to have high use tracing enabled has caused a problem. System action: The JVM is terminated. User response: Correct the -Dibm.dg.trc.highuse=... parameter and try again. JVMDG078RC %d from sysMonitorEnter in dgTraceLock Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG079RC %d from sysMonitorExit in dgTraceUnlock Explanation: Internal error. System action: None. User response: Contact your IBM service representative. JVMDG080Cannot find class %s Explanation: The JVM was attempting to initialize the (named) Trace class, but it cannot find it. System action: The JVM is terminated. User response: Handle this problem in the same way that you would any other class-not-found condition. JVMDG081Exception %s occurred during trace initialization Explanation: The JVM was attempting to initialize the Trace class, but its initializeTrace() method has thrown the specified exception. System action: The JVM is terminated. User response: Depends on the exception that was thrown. JVMDG082Out of memory while processing properties file Explanation: The JVM was trying to allocate a block of memory to hold the traceFileSpec, but the malloc failed. System action: The JVM is terminated. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG100Cannot allocate memory for line terminator char(1) Explanation: The JVM was trying to malloc memory to hold a system specific line terminator character, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG101Cannot allocate memory for line terminator char(2). Explanation: The JVM was trying to malloc memory to hold a system specific line terminator character, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG102Cannot allocate memory for filename. Explanation: The JVM was trying to get a piece of memory to store the event output file name, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG103Cannot allocate memory in dgEventQueueAdd Explanation: The JVM was trying to get a piece of memory to store an event queue item, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG104Cannot allocate memory for printing a stack trace Explanation: The JVM was trying to get a piece of memory to store a Java™ stack trace, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG105Cannot allocate memory for new event list item Explanation: The JVM was trying to get a piece of memory to store an event list item, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG106Cannot allocate memory for adding an event class Explanation: The JVM was trying to get a piece of memory to store an event class, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG107Cannot allocate memory for printing a stack trace Explanation: The JVM was trying to get a piece of memory to store a Java stack trace, but the malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG109Cannot allocate memory for data in initDgData Explanation: On startup, the DG subcomponent has attempted to malloc three blocks of memory for the traceLock, traceTerminated, and writeEvent monitors. One or more of these mallocs has failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG124Cannot allocate memory in dgRegisterDumpRoutine -- Out of memory in rasDumpRegister Explanation: Each subcomponent registers its dump routine at startup so that it can be called back in the event of a Javadump. However, the malloc that was to add this routine to the list has failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG125Null method trace specification Explanation: The property -Dibm.dg.trc.methods= requires a following value that indicates which methods to trace. This value was omitted. System action: The JVM terminates. User response: Correct the parameter (for example, -Dibm.dg.trc.methods=*), then retry. JVMDG126Length of dgMethodFmt exceeded Explanation: The specification of the methods to trace is too long for the available buffer. System action: The JVM terminates. User response: Use fewer characters to specify the methods that you want to trace, then retry. JVMDG127Misplaced parentheses in method trace specification Explanation: The method specification cannot begin with ( or ). System action: The JVM terminates. User response: Correct the method specification and retry. JVMDG128Out of memory handling methods Explanation: Method trace requires a table of methods, but the malloc that was to create it failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG129At least one method is required Explanation: The property -Dibm.dg.trc.methods requires a following value that indicates which methods to trace. This value was omitted. System action: The JVM terminates. User response: Correct the parameter (for example, -Dibm.dg.trc.methods=*) and retry. JVMDG130Invalid wildcard in method trace Explanation: A wildcard has been detected at an illegal position in the methods property ("-Dibm.dg.trc.methods"). System action: The JVM terminates. User response: Correct the specification and retry. JVMDG135Error %d from JVMPI EnableEvent Explanation: Method trace uses the JVMPI method entry and exit events. One or both of these could not be enabled. System action: The JVM terminates. User response: Method trace and JVMPI cannot be used at the same time. If you were attempting to do this, this error message was to be expected. If not, contact your IBM service representative. JVMDG136Invalid method trace match flag %d Explanation: This message should never be issued. System action: None. User response: Contact your IBM service representative. JVMDG137Invalid Signature type = %d SIGNATURE_VOID = %c Explanation: This message should never be issued. System action: None. User response: Contact your IBM service representative. JVMDG138Invalid Signature type = %c Explanation: This message should never be issued. System action: None. User response: Contact your IBM service representative. JVMDG139Cannot obtain memory for dgMethodfmt Explanation: Method trace required a block of memory, but the malloc for it failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG140Invalid applid specified Explanation: The property -Dibm.dg.trc.applids must be followed by a list of applids, all of which must be of length greater than zero; for example, -Dibm.dg.trc.applids=applid1,,applid2 is not valid. System action: The JVM terminates. User response: Correct the list of applids and retry. JVMDG141Out of memory handling applids Explanation: Processing the list of applids includes mallocing a block of storage, but this malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG142At least one applid is required Explanation: The property -Dibm.dg.trc.applids must be followed by at least one applids. System action: The JVM terminates. User response: Retry, providing at least one applid. JVMDG147Illegal subcomponent id in dump routine registration Explanation: An unexpected error has occurred during dump routine registration. System action: This dump routine is not registered and will not be called in the event of a Javadump. User response: Contact your IBM service representative. JVMDG148Malloc failure in dg_main Explanation: A buffer was being malloced for use during a Javadump. The malloc failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG157Cannot obtain memory for Java stack trace Explanation: The JVM was invoked with the callstack option (-Dibm.dg.trc.callstack). On entry into a method, the saved stack of references to Java methods must be expanded, but the malloc to do this has failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG158Error in Java call stack trace Explanation: The JVM was invoked with the callstack option (-Dibm.dg.trc.callstack). On exit from a method, a sanity check of what had been stored away has failed. System action: The JVM terminates. User response: Contact your IBM service representative. JVMDG159Malloc failure in dg_main Explanation: The malloc of a block of memory that was required during DG subcomponent initialization has failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG160Cannot obtain memory for utcAppFormat Explanation: In utcAppFormat, a malloc request was Unable to be satisfied. System action: The JVM terminates. User response: This message indicates that native memory was exhausted. Increase the available memory or remove any extraneous memory usage. JVMDG161Tracepoint %6.6X truncated Explanation: During the expansion of an application trace tracepoint, the string buffer length was exceeded System action: The substitution of variables into the tracepoint stops at this point and the part-formatted string is returned. User response: Substitute less data into the application trace point. Consider splitting it into multiple trace points or validating data before invoking the tracepoint JVMDG162Could not allocate buffer Explanation: While checking whether backtrace was enabled, a malloc failure occurred. System action: The JVM terminates. User response: This message indicates that native memory was exhausted. Increase the available memory or remove any extraneous memory usage. JVMDG163The Backtrace trace option is not supported on this platform Explanation: "backtrace" was specified in one of the trace options. Not all platforms support this option. This platform does not. System action: The JVM terminates. User response: Remove the "backtrace" keyword from all command-line trace options and any trace properties file in use. Then reissue the command. JVMDG200Diagnostics system property %s%s%s Explanation: System properties that are associated with trace are echoed to stderr on startup so that you can be sure that they have been set. System action: This message is displayed for each trace property set. User response: This message is for information. It is not an error. JVMDG201Keyword abbreviation too short Explanation: Trace properties can be abbreviated to three characters but no fewer. System action: The JVM terminates. User response: Correct your specification of trace properties in the trace properties file to use no abbreviations that are shorter than three characters. Then retry. JVMDG202Invalid short form keyword Explanation: One of the supplied trace properties was not a recognized property name. System action: The JVM terminates. User response: Correct the property definitions and retry. JVMDG203Exception occurred while running user thread Explanation: A user thread that was started by JVMRI caused an exception that has been caught. System action: The user thread is terminated but the JVM continues. User response: Examine the code that your user thread was running, to determine the location of the problem. JVMDG205Out of memory in rasCreateThread Explanation: An attempt was made to allocate the memory that is required to create your JVMRI user thread, but the malloc failed. System action: JNI_ENOMEM is returned to the calling agent. User response: Try running the JVM with a larger maximum heap size (using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG206Out of memory in rasCreateThread Explanation: An attempt was made to allocate the memory that is required to store the name of your JVMRI user thread, but the malloc failed. System action: JNI_ENOMEM is returned to the calling agent. User response: Try running the JVM with a larger maximum heap size by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG207Cannot create thread in rasCreateThread Explanation: A JVMRI call was made to create the user thread, but for it failed for unspecified reasons. System action: JNI_ERR is returned to the calling agent. User response: Investigate the reasons why this thread creation might have failed; for example, system limits, security settings. JVMDG208Cannot create special thread in rasCreateThread Explanation: A JVMRI call was made to create the special user thread, but for it failed for unspecified reasons. System action: JNI_ERR is returned to the calling agent. User response: Investigate the reasons why this thread creation might have failed; for example, system limits, security settings. JVMDG209No Javacore, JVM is not initialized rasGenerateJavacore Explanation: A JVMRI call to create a Javadump was received, but because the JVM has not yet finished initializing, this is not permitted. System action: JNI_ERR is returned to the calling agent. User response: Modify your agent so that you do not attempt to take a Javadump until the system has finished initializing. JVMDG210Exception %d received during dump routine. Explanation: A JVMRI call to run a dump routine was actioned, but the dump routine found an exception. System action: The dump routine will be truncated at this point. User response: If the exception is persistent and unexpected, contact your IBM service representative. JVMDG211Invalid component ID rasRunDumpRoutine Explanation: A JVMRI call was made to run a specified dump routine but the dump routine that was specified does not exist. System action: JNI_ERR is returned to the calling agent. User response: Correct the error, specifying the ID of an existing component. JVMDG212Invalid component Name specified Explanation: The JVMRI call rasGetComponentDataArea() was made to get information about a specified component data area, but the specified component does not exist. System action: JNI_ERR is returned to the calling agent. User response: Allowable components are: "ci", "dg", "cl", "dc", "lk", "xe", "xm", and "st". The component names can also be supplied in uppercase, but NOT in mixed case. JVMDG213Cannot create thread in rasStartThreads Explanation: A JVMRI call was made to start a user thread. It was deferred until initialization was complete, but now it has been actioned and has failed for unspecified reasons. System action: The thread is not started. User response: Investigate the reasons why this thread creation might have failed; for example, system limits, security settings. JVMDG214Cannot create special thread in rasStartThreads Explanation: A JVMRI call was made to start a special user thread. It was deferred until initialization was complete, but now it has been actioned and has failed for unspecified reasons. System action: The thread is not started. User response: Investigate the reasons why this thread creation might have failed; for example, system limits, security settings. JVMDG215Dump Handler has Processed %s Signal %i. Explanation: The Dump Handler has successfully handled the signal (specified). The selected dumps have been produced. System action: For information only. User response: The dumps that you selected (by use of the environment variable JAVA_DUMP_OPTS) should now be available for your use in debugging your problem or for sending to your IBM service representative. JVMDG217Dump Handler is Processing a Signal - Please Wait. Explanation: A signal has been raised and is being processed by the dump handler. System action: At this point, depending upon the options that have been set, Javadump, core dump, and CEEDUMP (z/OS® only) can be taken. This message is for information only and does not indicate a further failure. User response: None. JVMDG218Dump Handler Caught Internal Exception %d Processing Signal %i. Explanation: An exception (specified) was found during an attempt to process the original signal (specified). System action: Diagnostic information (dumps) might have been lost. User response: Contact your IBM service representative. JVMDG219Dump Handler Caught Internal Exception %d Processing SYSDUMP for Signal %i. Explanation: An exception (specified) was found during an attempt to generate a SYSDUMP for the original signal (specified). A SYSDUMP varies in nature from platform to platform; for example, a minidump on windows, a core dump on AIX®. System action: The SYSDUMP might have been lost. User response: Contact your IBM service representative. JVMDG220Dump Handler Caught Internal Exception %d Processing CEEDUMP for Signal %i The JVM may now be in an Unusable State. Explanation: An exception (specified) was found during an attempt to generate a CEEDUMP for the original signal (specified). This should occur only on z/OS. System action: The CEEDUMP might have been lost. User response: Contact your IBM service representative. JVMDG221Dump Handler Caught Internal Exception %d Processing JAVADUMP for Signal %i. Explanation: An exception (specified) was found during an attempt to generate a JAVADUMP for the original signal (specified). System action: The Javadump might have been lost. User response: Contact your IBM service representative. JVMDG222Dump Handler Caught Internal Exception %d Processing jvmpi_dump() for Signal %i. Explanation: An exception (specified) was found during an attempt to generate a JVMPI Heap Dump for the original signal (specified). System action: The JVMPI Heap Dump might have been lost. User response: Contact your IBM service representative. JVMDG223Dump Handler Caught Internal Exception %d processing HEAPDUMP for Signal %i Explanation: A JVMMI heap dump event was been generated (JVMMI_SERVICE_EVENT_HEAPDUMP). During the processing of this event by the attached JVMMI agent, the named operating system signal was received. System action: Dump processing continues. User response: Find the cause of the failure in your JVMMI agent. JVMDG224Invalid character(s) encountered in hex number "%s" Explanation: When a tpid clause in the system property -Dibm.dg.trc.trigger was being processed, a hexadecimal tracepoint id (tpid) was expected, but the JVM found a nonhexadecimal character. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...) clauses. It must be of the form tpid(hexnumber) or tpid(hexnumber1-hexnumber2) JVMDG225Hex number too long or too short "%s" Explanation: When a tpid clause in the system property -Dibm.dg.trc.trigger was being processed, a specified tpid was found to be of incorrect length. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...) clauses. It must be of the form tpid(hexnumber) or tpid(hexnumber1-hexnumber2), and the hexadecimal numbers must each be between one and eight digits in length. JVMDG226Signed number not permitted in this context "%s" Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, a negative delay count was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. If a delaycount is specified, it must be a positive number. JVMDG227Invalid character(s) encountered in decimal number "%s" Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, a non-numeric character was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. If a delaycount is specified, it must contain only the characters 0 through 9. JVMDG228Number too long or too short "%s" Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, a bad delay count was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. If a delaycount is specified, it must be between one and eight digits long. JVMDG229Invalid trigger action "%s" selected Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, an unrecognized action was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. Where an action is specified, it must be one of the following: suspend, resume, suspendthis, resumethis, javadump, coredump, heapdump, or snap. JVMDG230Invalid tpid clause, usage: tpid(tpid|tpidrange,action[,delaycount]) \n clause is: tpid(%s) Explanation: When a tpid clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to have too many parameters. System action: The JVM fails to initialize. User response: Correct the tpid clause. Its format is displayed in the message. JVMDG231Invalid tpid range - start value cannot be higher than end value Explanation: When a tpid clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to contain an illegal tpid range. System action: The JVM fails to initialize. User response: Correct the tpid clause. For a tpid range, the end of the range cannot be lower than the start. JVMDG232Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not the Java heap) is full. Close down some other running applications to save space. JVMDG233Error occurred while activating tpid %X (rc=%d) Explanation: During an attempt to activate the displayed tpid, an error was received. System action: The JVM fails to initialize. User response: Ensure that the tpid is correct and retry the operation. If the problem remains, check TraceFormat.dat to ensure that the tpid is present in the build. JVMDG234Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not Java the heap) is full. Close down some other running applications to save space. JVMDG235WARNING: This trigger method spec results in 100+ trigger entries.\n. For performance reasons, you may want to narrow the selected scope. Explanation: The method spec that you provided on the method clause of the trigger property is very wide. It will cause much memory to be allocated for control structures. System action: Information only; this message is issued, but no action is taken. User response: You can ignore this warning and continue. However, to save memory, you should refine the trigger method spec to something that is more compact. JVMDG236Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not the Java heap) is full. Close down some other running applications to save space. JVMDG237Failure initializing triggering on methods Explanation: Trigger trace has failed to initialize. System action: The JVM fails to initialize. User response: Check the parameters that you supplied. Note that method trace and trigger trace do not work alongside JVMPI. JVMDG238Too many parameters on trigger property method clause \n usage: method(methodSpec[,entryAction] [,exitAction][,delay]) Explanation: When a method clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to have too many parameters. System action: The JVM fails to initialize. User response: Correct the method clause. Its format is displayed in the message. JVMDG239Method Spec on trigger property (method clause) may not be null Explanation: When the method spec that is in a method clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to be empty. System action: The JVM fails to initialize. User response: Insert the desired method spec, and retry the operation. JVMDG240Method spec for trigger may not include '!', '(' or ')' Explanation: When the method spec that is in a method clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to contain illegal characters. System action: The JVM fails to initialize. User response: Correct the method spec, and retry the operation. JVMDG241You must specify an entry action, an exit action or both. Explanation: When the method clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to contain neither an entry action, nor an exit action. System action: The JVM fails to initialize. User response: Correct the method clause, and retry the operation. You must specify at least one of the two actions. JVMDG242Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not the Java heap) is full. Close down some other running applications to save space. JVMDG243Trigger groups clause has the following usage: \n group(,[,]) Explanation: When the group clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to be in error. System action: The JVM fails to initialize. User response: Change the group clause in line with the usage text that is in the message. Then retry the operation. JVMDG244Delay counts must be integer values from -99999 to +99999: \n group(%s,%s,%s) Explanation: A delay count can be -99999 through +99999. You supplied one that was not in this range. System action: The JVM fails to initialize. User response: Correct the group clause in your trigger property, then retry the operation. JVMDG245Undefined Group "%s" specified in trigger property Explanation: When the group clause in the system property -Dibm.dg.trc.trigger was being processed, the clause was found to reference a group that not exist. System action: The JVM fails to initialize. User response: Correct the group clause, then retry the operation. JVMDG246Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not the Java heap) is full. Close down some other running applications to save space. JVMDG247Error occurred while activating trigger Group "%s" Explanation: When the group clause in the system property -Dibm.dg.trc.trigger was being processed, the specified trigger group could not be processed. System action: The JVM fails to initialize. User response: Ensure that the group clause is correct, then retry the operation. JVMDG248Zero length clause in trigger statement Explanation: One of the clauses of the trigger property was null. System action: The JVM fails to initialize. User response: Check your input, then retry the operation. JVMDG249Malformed clause, requires ')' at the end: \n "s" Explanation: Internal error. The system should never reach this point. System action: The JVM fails to initialize. User response: Contact your IBM service representative. JVMDG250Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not the Java heap) is full. Close down some other running applications to save space. JVMDG251Internal Error Explanation: None. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG252Empty trigger clause "%s" not permitted Explanation: The quoted command-line fragment is in error. A clause of the trigger property is null. System action: The JVM fails to initialize. User response: Correct the trigger property, then retry the operation. JVMDG253Missing closing bracket(s) in trigger property Explanation: The trigger property did not end in a closing bracket. System action: The JVM fails to initialize. User response: Correct the brackets on the trigger property, then retry the operation. JVMDG254Out of memory processing trigger property Explanation: During an attempt to process a trace option, a malloc failed. System action: The JVM fails to initialize. User response: System memory (not the Java heap) is full. Close down some other running applications to save space. JVMDG255Usage error: trigger=([method(args)],[tpid(args)], [group(args)],...) Explanation: A null trigger property was found. System action: The JVM fails to initialize. User response: Correct the trigger property in line with the usage text that is in the message, then retry the operation. JVMDG256Empty clauses not allowed in trigger property Explanation: A null clause was found in a trigger property. System action: The JVM fails to initialize. User response: Correct the trigger property, then retry the operation. This error probably occurred because you entered something like trigger=method,,tpid (that is, you entered too many commas). JVMDG257Trigger clauses can be tpid, method or group. This is invalid: \n "%s" Explanation: Clauses in the trigger property can begin with "method(", "tpid(", or "group(". Anything else is rejected. System action: The JVM fails to initialize. User response: Correct the trigger clauses, then retry the operation. JVMDG258resumecount takes a (single) integer value from -99999 to +99999 Explanation: The ibm.dg.trc.resumecount property is an integer value -99999 through +99999. The value that you specified was not in this range. System action: The JVM fails to initialize. User response: Correct the resumecount property, then retry the operation. JVMDG259suspendcount takes a (single) integer value from -99999 to +99999 Explanation: The ibm.dg.trc.suspendcount property is an integer value -99999 through +99999. The value that you specified was not in this range. System action: The JVM fails to initialize. User response: Correct the suspendcount property, then retry the operation. JVMDG260resumecount and suspendcount may not both be set Explanation: You attempted to set the resumecount and suspendcount properties at the same time. This is not allowed. System action: The JVM fails to initialize. User response: Decide which property you want to use, then remove the other JVMDG261Trace Buffer snap requested by triggered trace action Explanation: Trigger trace has requested that the internal trace buffers be flushed to a Snap file. System action: The JVM fails to initialize. User response: Check whether a file with a name that starts with "Snap" (commonly "Snap0001......") is present. This file contains the most up-to-date JVM trace information. JVMDG262Internal Error Explanation: None. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG263Internal Error Explanation: None. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG264Internal Error Explanation: None. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG265Unknown trigger action encountered (action=%d) Explanation: When an attempt is made to perform a trigger action, the stored trigger type is an unrecognized value. System action: The JVM fails to initialize. User response: This error should not occur. If it does, and occurs repeatedly, contact your IBM service representative. JVMDG266Cannot allocate memory in dgRegisterDumpRoutine Explanation: During dump routine initialization, a block of memory is required, but the malloc has failed. System action: The JVM terminates. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. JVMDG267Cannot suspend tracing from unidentified thread Explanation: A call was made to suspend the tracing for a thread, but the thread id was null. System action: The JVM fails to initialize. User response: This error should not occur. If it does, and occurs repeatedly, contact your IBM service representative. JVMDG268Cannot resume tracing from unidentified thread Explanation: A call was made to resume the tracing for a thread, but the thread id was null. System action: The JVM fails to initialize. User response: This error should not occur. If it does, and occurs repeatedly, contact your IBM service representative. JVMDG269Unknown JVMRAS interface version or modification level Explanation: When the JVMRAS interface (JVMRI) was being initialized, a problem occurred. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG270Unknown JVMRAS interface version or modification level Explanation: When the JVMRAS interface (JVMRI) was being initialized through JNI, a problem occurred. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG271Unknown JVMRAS interface version or modification level Explanation: When the JVMRAS interface (JVMRI) was being initialized from the HPI, a problem occurred. System action: The JVM fails to initialize. User response: If the problem remains, contact your IBM service representative. JVMDG272No Heapdump, JVM is not initialized rasGenerateHeapdump Explanation: A JVMRI request to take a heapdump has been refused because the JVM is not yet initialized. Taking a heapdump before there is a heap, for example, would not make sense. System action: No heapdump is produced, but, in other respects, operation continues as before. User response: If the request came from your agent code, do not issue a heapdump request before you are sure that the JVM is initialized. You can determine that the JVM is initialized, for example, by registering a callback on the JVMMI event, JVMMI_EVENT_INIT_DONE. JVMDG273Heapdump invoked by dgDumpHandler Explanation: A heap dump is being taken as part of the signal handling process. System action: A heapdump is taken. User response: For information only. JVMDG274Dump Handler has Processed OutOfMemory Explanation: The Dump Handler has successfully handled an out-of-memory condition. The selected dumps have been produced. System action: For information only. User response: Investigate why your application might have run out of memory. For example, the specified heap size might be too small or references to unrequired objects are being retained, preventing them from being garbage collected. JVMDG275Heapdump invoked by rasJniHeapDump Explanation: rasJniHeapDump calls a user agent to take a heapdump. System action: This message is passed to JVMMI for inclusion in the JVMMI_EVENT_HEAP_DUMP detail information, to tell you why your agent has been requested to take a heap dump. User response: For information only. JVMDG276Heapdump invoked by rasGenerateHeapdump Explanation: rasGenerateHeapdump calls a user agent to take a heapdump. System action: This message is passed to JVMMI for inclusion in the JVMMI_EVENT_HEAP_DUMP detail information, telling you why your agent has been requested to take a heap dump. User response: For information only. JVMDG277Match counts must be integer values from -99999 to +99999: group(%s,%s,%s,%s) Explanation: On the -Dibm.dg.trc.trigger=group(...) property, the matchcount parameter (the fourth one) is out of range. System action: The JVM terminates. User response: Retry, specifying a different value for matchcount JVMDG278Too many parameters on trigger property threshold clause usage: threshold(thresholdType,thresholdValue [,entryAction][,exitAction][,delay] [,matchcount]) Explanation: There are too many parameters on the -Dibm.dg.trc.trigger=threshold(...) property. System action: The JVM terminates. User response: Correct the command and retry. JVMDG279Threshold Type on trigger property (threshold clause) may not be null Explanation: You must specify a threshold type on the -Dibm.dg.trc.trigger=threshold(...) property. System action: The JVM terminates. User response: Correct the command and retry. JVMDG280Threshold Value on trigger property (threshold clause) may not be null Explanation: You must specify a threshold value on the -Dibm.dg.trc.trigger=threshold(...) property. System action: The JVM terminates. User response: Correct the command and retry. JVMDG281ThresholdType for trigger may not include '!', '(' or ')' Explanation: On the -Dibm.dg.trc.trigger=threshold(...) property, the threshold type must not include the listed characters. System action: The JVM terminates. User response: Correct the command and retry. JVMDG282ThresholdValue for trigger may not include '!', '(' or ')' Explanation: On the -Dibm.dg.trc.trigger=threshold(...) property, the threshold value must not include the listed characters. System action: The JVM terminates. User response: Correct the command and retry. JVMDG283You must specify an entry action, an exit action or both Explanation: No entry or exit action was specified on the -Dibm.dg.trc.trigger=threshold(...) property. System action: The JVM terminates. User response: Correct the command, adding an entry action, an exit action, or both. JVMDG284Out of memory processing trigger property Explanation: While trying to store information about a trigger property, a malloc failed. System action: The JVM terminates. User response: This message indicates that native memory was exhausted. Increase the available memory or remove any extraneous memory usage. JVMDG285Threshold direction undefined Explanation: This message should never be issued. System action: The JVM terminates. User response: Contact your IBM support representative. JVMDG286Threshold direction undefined Explanation: This message should never be issued. System action: The JVM terminates. User response: Contact your IBM support representative. JVMDG287Internal error. Explanation: This message should never be issued. System action: Undefined. User response: Contact your IBM support representative. JVMDG288Cannot create semaphore in initDgData Explanation: DG initialization attempted to create a semaphore, but the operation failed. System action: The JVM terminates. User response: Investigate whether you have reached a system limit on semaphores. JVMDG289Unknown Universal Trace Client interface version or modification. Explanation: Internal error. System action: The JVM terminates. User response: Contact your IBM support representative. JVMDG290Syntax error in early trace options environment variable Explanation: System action: The JVM terminates. User response: Correct the command and retry. JVMDG291Syntax error in early trace options environment variable Explanation: The early trace environment variable is incorrectly specified. System action: The JVM terminates. User response: Correct the environment variable and retry. JVMDG292Unsupported trace option in early trace options environment variable Explanation: The early trace environment variable is incorrectly specified. System action: The JVM terminates. User response: Correct the environment variable and retry. JVMDG293Dump Handler Caught Internal Exception %d Processing HEAPDUMP for Signal %i. Explanation: During the creation of a heapdump an operating system signal occurred. System action: The heapdump might be truncated. User response: Be aware that the heapdump might not be useful or usable. JVMDG294Error writing Java core buffer to file Explanation: Javacore processing was Unable to obtain the name to use for the Javacore file. System action: The Javacore is written to stderr instead of to file. User response: None. JVMDG303JVM Requesting Java core file Explanation: The JVM has started to generate a Javadump. System action: For information only. User response: None. JVMDG304Java core file written to %s Explanation: The JVM has finished generating a Javadump. System action: For information only. User response: The Javadump is now available. Its name is specified in the message. JVMDG305Java core not written, Unable to allocate memory for print buffer. Explanation: Javadump processing needs a large buffer to create the Javadump. If this memory is not available, a Javadump is not produced. System action: Javadump processing is skipped. User response: This message is for information. It is not an error. JVMDG306Exception %d received during dump routine processing, section truncated. Explanation: During the creation of the Javadump, each subcomponent is asked to provide its own dump information. In one of the components, a severe error has occurred and the production of its section of the Javadump has been terminated. System action: The dump information is written to the Javadump file, but the contents of the current section ends prematurely. This message is written at that point in the Javadump and the next section continues as normal. User response: Review the contents of the Javadump file and, if the truncation of the section prevents you using the Javadump for its intended purpose, contact your IBM service representative. JVMDG307Exception %d received during dump routine processing, dump truncated. Explanation: During creation of the Javadump, a severe error has occurred and the production of the Javadump has been terminated. System action: The dump information that has been generated so far is written to the Javadump file. Following that, this message is written into the file and the file ends prematurely. User response: Contact your IBM service representative. JVMDG308Error writing Java core buffer to file Explanation: Writing the Javadump to the expected file has failed for unspecified reasons. System action: The Javadump file is written to stderr instead. User response: If this problem remains, contact your IBM service representative. JVMDG310Javacore cannot be taken by a system thread because of possible deadlocks Explanation: An internal system thread has attempted to generate a Javacore (Javadump) file, but it cannot. Before the JVM can generate a Javadump, it needs to quiesce all running threads to collect coherent data. It does this by obtaining system monitors and suspending all threads except the current one and some special threads such as Garbage Collector helper threads. The Garbage Collector does a similar action when a garbage collection is done. A problem occurs when these two events coincide. Typically this can happen if a Garbage Collector helper thread finds a problem while a garbage collection is in progress. If one of these threads attempts to generate a Javacore during a garbage collection, a deadlock almost certainly occurs. This deadlock is a design restriction. System action: The Javadump file is not produced and processing continues. If the reason for the failed Javadump is a fatal error, the JVM terminates. User response: If this problem remains, see JVM dump initiation. JVMDG311Set JAVA_DUMP_OPTS to request a SYSDUMP if diagnostic information is required Explanation: This is an informational message that always accompanies JVMDG310. System action: None. User response: See JVM dump initiation. JVMDG312Dump handler forcing garbage collection for Heapdump Explanation: This is an informational message that shows that a garbage collection cycle is being performed before a Heapdump is generated. System action: A garbage collection cycle is performed. User response: None. JVMDG313Heapdump cannot be taken by a system thread because of possible deadlocks Explanation: An internal system thread has attempted to generate a Heapdump file, but it cannot. Before the JVM can generate a Heapdump, it needs to quiesce all running threads to collect coherent data. It does this by obtaining system monitors and suspending all threads except the current one and some special threads such as Garbage Collector helper threads. The Garbage Collector does a similar action when a garbage collection is done. A problem occurs when these two events coincide. Typically this can happen if a Garbage Collector helper thread finds a problem while a garbage collection is in progress. If one of these threads attempts to generate a Heapdump during a garbage collection, a deadlock almost certainly occurs. This deadlock is a design restriction. System action: The Javadump file is not produced and processing continues. If the reason for the failed Javadump is a fatal error, the JVM terminates. User response: If this problem remains, see JVM dump initiation. JVMDG314Set JAVA_DUMP_OPTS to request a SYSDUMP if diagnostic information is required Explanation: This is an informational message that always accompanies JVMDG310. System action: None. User response: See JVM dump initiation. JVMDG315JVM Requesting Heapdump file Explanation: The JVM has started to generate a Heapdump. System action: For information only. User response: None. JVMDG316 Unable to write Heapdump - Unable to create file %s Explanation: The JVM cannot open the file. System action: The Heapdump is not generated, and processing continues. User response: Check whether the JVM has the correct permission to write to the output file. JVMDG317Error % writing Heapdump to file Explanation: The write operation failed while it was writing the Heapdump. System action: The Heapdump write operation is stopped, and processing continues. User response: Determine why the Heapdump write operation failed. JVMDG318Heapdump file written to %s Explanation: The JVM has finished generating a Heapdump. System action: For information only. User response: The Heapdump is now available. Its name is specified in the message. JVM error messages for JVMHP JVMHP002JVM requesting Transaction Dump Explanation: During handling of a fatal signal, the JVM requests that the system produces a call BCP service IEATDUMP to produce a transaction dump. System action: The JVM calls BCP service IEATDUMP to produce a transaction dump. User response: See the text of system message IEA820I on the system log to determine the name of the dynamically allocated dataset. The service allocates the dataset into the normal MVS™ filesystem, not into the z/OS® UNIX® HFS. If you do not want transaction dumps to be created, set code environment variable IBM_JAVA_ZOS_TDUMP=NO. JVMHP004Transaction dump service IEATDUMP failed with rc=0x%x (%d), reason code=0x%x (%d) Explanation: The IEATDUMP service that is called by the JVM has failed. If the rc is 4, a partial dump has been taken. If the rc is higher, the dump service completely failed. System action: The JVM takes other actions that are suitable for this signal. User response: Console messages that have prefix IEA have been written to the system log with more information about the failure. Look up the return code and reason code in z/OS MVS Auth Assm Services Reference ENF-IXG, SA22-7610. JVMHP006JVM requesting CEEDUMP Explanation: The JVM calls the LE Service CEE3DMP to request a formatted application level dump. System action: The JVM takes other actions that are suitable for this signal. User response: None. JVMHP008CEE3DMP failed with msgno 0x%x (%d) Explanation: The LE service CE3DMP failed. The message prints the hex and decimal value of the fc.tok_msgno returned. User response: No CEEDUMP was created. Look up the meaning of the msgno in the appropriate LE documentation. JVMHP009Complete CEEDUMP was written to process ID %i Explanation: A complete CEEDUMP was written into the z/OS UNIX HFS. The message indicates the complete writing of the CEEDUMP. User response: None JVMHP010No TDUMP requested, request threshold of %d reached Explanation: The user-specified or default limit for the number of transaction dumps has been reached. System action: The JVM takes no further transaction dumps. User response: If a Transaction Dump is required for diagnosis of a later program check, increase the limit by using the environment variable IBM_JAVA_ZOS_TDUMP_COUNT. JVMHP012System Transaction Dump written to %s Explanation: The JVM called the IEATDUMP macro to write a dump a dataset. System action: The JVM can gather other documentation in the form of CEEDUMPs, core dumps, JAVADUMPs, or all of these. User response: Examine dumps to determine cause of failure. JVMHP013JVM requesting USERABEND Explanation: The JVM call the LE Service CEE3ABD for the JAVA_DUMP_OPTS USERABEND option. System action: The JVM takes a CEEDUMP. User response: This message verifies that a dump was taken in response to a user request. Examine the dump to find the cause of the failure. JVMHP014JVM requesting user dump tool [ %s ] Explanation: A system dump has been requested and the dump tool that the user has specified is being run. The user specified this tool by using the environment setting JAVA_DUMP_TOOL= System action: The JVM is requesting a system dump through the user-specified dump tool. User response: This message verifies that a dump was taken in response to a user request. Examine the dump to find the cause of the failure. JVMHP015JVM passing exception to Operating System Explanation: The JVM is passing an exception to Operating System. System action: None User response: None; this message is for information only. JVMHP016JVM requesting System Dump Explanation: The JVM is taking a dump either as a response to a user signal, or as the result of an exception. System action: The system attempts to produce a core file. User response: None; this message is for information only. JVMHP017System Dump written to Explanation: This message follows JVMHP016, and contains the filename of the core file that was produced. The message indicates that the core file was successfully produced. System action: None User response: None; this message is for information only. JVMHP018Coredump() failed with errno: Explanation: This message is the alternative message to JVMHP017. It indicates that the core file was not successfully produced. The coredump system call failed and the errno returned is contained in the message along with the filename of the core file. A file might or might not be produced, depending on the error that was found. System action: None User response: Determine which errno was returned, and correct the error. JVMHP020 Unable to find entry point MiniDumpWriteDump Explanation: A system dump has been requested, and the JVM is trying to generate a minidump. The dll dbghelp.dll that generates the minidump has been loaded, but the function that is needed to generate the dump MiniDumpWriteDump does not exist. System action: The system cannot find the function MiniDumpWriteDump in dbghelp.dll that it needs to generate the minidump. User response: Check whether the dbghelp.dll that was supplied with the JVM is the first one that is found on the system path. If it is and the error still occurs, it might have been corrupted. Reload the dbghelp.dll onto the system. JVMHP021 Unable to load DbgHelp.dll for system dump Explanation: A system dump has requested, but the JVM cannot load the dll dbghelp, which is used to generate a minidump. System action: The Microsoft® debug dll dbghelp cannot be loaded. User response: Ensure that dbghelp.dll is available on the path. It should have been installed with the JVM into the \jre\bin directory. JVMHP022Error creating system dump file: %s, GetlastError = %d Explanation: The dump file that is to contain the minidump information could not be created. System action: The system call to create the dump file has failed. User response: Ensure that the drive has enough disk space for the dump file. (For some applications, the dump file can be large.) If disk space does not seem to be the cause of problem, make a note of the error number, and contact your IBM® Service representative. JVMHP023Creating system dump file: %s Explanation: The dump file that contains the minidump information is being written to the named file. System action: The dump file is about to be written. User response: None; this message is for information only. JVMHP024Dump to %s successful Explanation: The minidump information has been written to the named file successfully System action: The system call to write the minidump information to the named file has completed successfully. User response: None; this message is for information only. JVMHP025Dump to %s failed, GetLastError = %d Explanation: The writing of the minidump information to the named file has failed. System action: The system call to write the minidump information to the named file has failed. User response: Ensure that the drive has enough disk space for the dump file. (For some applications, the dump file can be large.) Also ensure that the version of dbghelp.dll that is shipped with the JDK is the first one that is found on the path. If neither disk space nor dbghelp.dll seem to be the cause of problem, make a note of the error number, and contact your IBM Service representative. JVMHP026Unique dump file not created Explanation: A unique dump file name could not be created. System action: The system was trying to create a unique name and a path for the dump file into which the minidump information is to be written, but the length of the combined name and path exceeds the maximum filename/path length that is allowed. User response: You cannot control the filename, but you can change the path/directory name. If the directory from which the application is being run has a very long path, that path is causing the problem. By setting the environment string IBM_JAVACOREDIR, you can set to an alternative directory the location to which the dump file will be written. JVMHP027Path and filename too long Explanation: The path and filename that were generated for the minidump file exceed the maximum length allowed. The message JVMHP026 is displayed immediately before this message. System action: The system was trying to create a unique name and a path for the dump file into which the minidump information is to be written, but the length of the combined name and path exceeds the maximum filename/path length that is allowed. User response: You cannot control the filename, but you can change the path/directory name. If the directory from which the application is being run has a very long path, that path is causing the problem. By setting the environment string IBM_JAVACOREDIR, you can set to an alternative directory the location to which the dump file will be written. JVMHP028Error switching to IFA processor rc: %08x Explanation: The JVM attempted unsuccessfully to switch to an IFA (Integrated Facility for Applications) processor. This is caused by an error condition indicated by the return code shown. System action: The JVM disables further attempts to switch between IFA and standard processors and continues normally. User response: Contact you IBM Service representative for further information. JVMHP029Error switching from IFA processor rc: %08x Explanation: The JVM attempted unsuccessfully to switch from an IFA (Integrated Facility for Applications) processor back to a standard processor. This is caused by an error condition indicated by the return code shown. System action: The JVM disables further attempts to switch between IFA and standard processors and continues normally. User response: Contact you IBM Service representative for further information. JVMHP030 Unable to switch to IFA processor - libhpi.so needs extattr +a Explanation: The JVM attempted unsuccessfully to switch to an IFA (Integrated Facility for Applications) processor. This is because the JVM library file libhpi.so requires APF-authorisation. System action: The JVM disables further attempts to switch between IFA and standard processors and continues normally. User response: Ensure that file libhpi.so has extended attributes set using command "extattr +a". JVMHP031Malloc for bytes failed Explanation: The JVM failed to allocate the native storage required to hold details about the Java™ Threads. System action: The JVM was about to suspend all the Java threads ahead of Garbage Collection. The thread details would be passed to the C runtime call pthread_quiesce_and_get_np(), which would perform the thread suspension. User response: Increase the size of available storage. JVMHP032 Unable to UNFREEZE suspended threads, rc: errno: errno2: Explanation: The JVM was Unable to unfreeze all the Java threads . System action: The JVM is trying to suspend all the Java threads ahead of Garbage Collection. A call to pthread_quiesce_and_get_np() to suspend the threads has been unsuccessful; a further call to pthread_quiesce_and_get_np() to unsuspend (unfreeze) the threads before another attempt to suspend has also been unsuccessful. The JVM exits at this point. User response: Check that all LE maintenance has been installed by checking symptoms against the APAR database. JVMHP033 Unable to suspend threads, rc: errno: errno2: Explanation: The JVM was Unable to suspend all the Java threads. System action: The JVM is trying to suspend all the Java threads ahead of Garbage Collection. A call to pthread_quiesce_and_get_np() to suspend the threads has been unsuccessful. The JVM exits at this point. User response: Check that all LE maintenance has been installed by checking symptoms against the APAR database. JVMHP034KeyFromName.file open failure. Errno=%d Explanation: There is an error when the /tmp/IBM_JVM_GLOBAL_MONITOR_nnn file for semaphores is opened. System action: The JVM fails in the initialization stage. User response: Remove the /tmp/IBM_JVM_GLOBAL_MONITOR_nnn file and restart the JVM. JVMHP035KeyFromName.remove failed: errno=%d, filename=%s Explanation: The JVM failed to remove the existing semaphone file /tmp/IBM_JVM_GLOBAL_MONITOR_nnn. System action: The JVM fails in the initialization stage. User response: Remove the /tmp/IBM_JVM_GLOBAL_MONITOR_nnn file and restart the JVM. JVMHP036KeyFromName.semctl failed: errno=%d SemSetID=%d Explanation: The JVM failed to remove the existing semaphone set %d. System action: The JVM fails in the initialization stage. User response: Remove the semaphore set and restart the JVM. JVMHP037 Unable to modify file permissions: filename='%s' Explanation: The JVM failed to chmod the global monitor file /tmp/IBM_JVM_GLOBAL_MONITOR_nnn System action: The JVM fails in the initialization stage. User response: Remove the /tmp/IBM_JVM_GLOBAL_MONITOR_nnn file and restart the JVM. Contact your IBM service representative if the problem persists. JVMHP038ftok failed: errno=%d filename=%s Explanation: The JVM failed to generate the IPC key. System action: The JVM fails in the initialization stage. User response: Remove the /tmp/IBM_JVM_GLOBAL_MONITOR_nnn file and restart the JVM. Contact your IBM service representative if the problem persists. JVMHP039semaphore ID %d is larger than MAX_SEMAPHORES (%d) Explanation: The JVM failed when trying to allocate a semaphore id that was invalid. System action: The JVM fails. User response: Contact your IBM service representative. JVMHP040semctl failed to remove set: errno=%d, rc=%d, key=%x Explanation: The JVM failed to remove the existing semaphore set %d. System action: The JVM fails in the initialization stage. User response: Remove the semaphore set and restart the JVM. JVMHP041semget2 Failed: errno=%d, key=%x Explanation: The JVM failed to get the semaphore set id. System action: The JVM fails in the initialization stage. User response: Remove the semaphore set and restart the JVM. JVMHP042semget Failed: key = %d Explanation: The JVM failed to get the semaphore set id. System action: The JVM fails in the initialization stage. User response: Remove the semaphore set and restart the JVM. JVMHP043SemDestroy semaphore id mismatch Explanation: The JVM failed to identify the semaphore id to remove. System action: The semaphore set persists after the JVM has shutdown. User response: Contact your IBM service representative. JVMHP044SemDestroy remove failed filename=%s, errno=%d Explanation: The JVM failed to remove the semaphore file /tmp/IBM_JVM_GLOBAL_MONITOR_nnn. System action: The semaphore file persists after the JVM has shutdown. User response: Remove the /tmp/IBM_JVM_GLOBAL_MONITOR_nnn file. JVMHP045syscorepath has been set. The core file will be generated in the directory %s Explanation: The JVM is taking a system dump, which will be generated in the named directory. System action: The system attempts to produce a core dump in the directory specified by syscorepath. User response: None. This message is for information only. JVMHP046 Unable to allocate memory for stack segments for thread %p (errno: %d) Explanation: A system memory allocation call has failed while the JVM was preparing to scan a thread stack for garbage collection. System action: Garbage collection might miss object references and subsequently cause the JVM to fail. User response: Increase the available runtime (heap) memory in the process that is running the JVM. JVMHP047 Unable to scan stacks for thread %p due to quiesce failure Explanation: For garbage collection, an attempt was made to scan a stack for a thread that was not quiesced. System action: Garbage collection might miss object references and subsequently cause the JVM to fail. User response: Contact your IBM service representative. JVMHP048__stack_info failed for thread %p with errno: %d Explanation: For garbage collection thread stack scanning, a call to __stack_info LE service has failed. System action: Garbage collection might miss object references and subsequently cause the JVM to fail. User response: Contact your IBM service representative. JVMHP049tid %p - start and end addresses for segment %d are the same (both %p) (nsegs: %d) Explanation: A call to the operating system to return a thread's upper and lower bounds has returned values that are equal. System action: This message is a warning. User response: A JVM failure due to (probably) heap corruption might follow this warning. If this failure occurs, contact your IBM Service representative. JVM error messages for JVMLH JVMLH001Invalid thread state xxxxx Explanation: While waiting for a mutex the thread is in the invalid state xxxxx. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM® service representative. JVMLH002Invalid thread state xxxxx Explanation: After waking from a wait state the thread is in the invalid state xxxxx. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH003Cannot open /proc//stat Explanation: The JVM cannot open the process stat file at the specified location. The file might not have the correct permission for you to open it or the process might not exist in memory. System action: The JVM is terminated. User response: If the file is present at this location check the permission. If the file is not present, contact your IBM service representative. JVMLH004Cannot parse stack base from /proc//stat Explanation: The stat file at the specified location cannot be parsed. The operating system might have changed the file format. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH005Invalid thread sr_state xxxxx Explanation: Due to an internal error condition the thread is in the invalid state xxxxx. System action: None. User response: Contact your IBM service representative. JVMLH006Invalid thread sr_state xxxxx Explanation: This warning message is displayed when the thread enters the invalid state xxxxx. System action: None. User response: Contact your IBM service representative. JVMLH007Invalid thread sr_state xxxxx Explanation: This warning message is displayed when the thread enters the invalid state xxxxx. System action: None. User response: Contact your IBM service representative. JVMLH008Unexpected error (xxxxx) from pthread_mutex_trylock() Explanation: pthread_mutex_trylock() returned the error xxxxx when it tried to acquire the monitor. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH009Unexpected error (xxxxx) from pthread_mutex_trylock() Explanation: pthread_mutex_trylock() returned the error xxxxx when it entered the monitor. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH010Invalid in_use_count Explanation: The count of the monitors is incorrect due to a JVM internal problem. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH011Unexpected error(%d) from pthread_mutex_lock Explanation: A problem occurred in a pthread_mutex_lock() call. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH012Cannot get minimum stack for primordial thread Explanation: There is insufficient space on the stack. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH013Unexpected suspend type xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH014Invalid thread sr_state xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH015Invalid thread sr_state xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH016Bad suspend count xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH017Unexpected suspend type xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH018Invalid suspend count (xxxxx) for type yyyyy Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH019Invalid thread sr_state xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH020Error resetting thread sr_state Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH021Unexpected error (xxxxx) from kill Explanation: An internal error occurred on the system call. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH022Unexpected error (xxxxx) from kill Explanation: An internal error occurred on the system call. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH023Error resetting thread sr_state Explanation: An internal error occurred on the system call. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH024Unexpected suspend type xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH025Invalid suspend count (xxxxx) for type yyyyy Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH026Invalid thread sr_state xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH027Unexpected error (xxxxx) from kill Explanation: An internal error occurred on the system call. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH028Error registering requestor Explanation: None. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH029Suspend context has not been saved Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH030Threads are disappearing when trying to suspend all threads Explanation: This is a JVM or an Operating System internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH031Error unregistering requestor Explanation: None. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH032Cannot open /proc//maps Explanation: The JVM cannot open the process maps file at the specified location. The file might not have the correct permission for you to open it or the process might not exist in memory. System action: The JVM is terminated. User response: If the file is present at this location check the permission. If the file is not present, contact your IBM service representative. JVMLH033Cannot parse stack top from /proc//maps Explanation: The stat file at the specified location cannot be parsed. The operating system might have changed the file format. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH034 Unable to determine stack layout - pthread_getattr_np() unavailable Explanation: None. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH035Invalid thread sr_state xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH036Thread sr_state unexpectedly changed Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH037Invalid thread sr_state xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH038Registration of suspend/resume signal xxxx handling failed. Explanation: The registration of signal handling for the suspend/resume signal failed. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH040Unexpected hpi lock value xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH041Unexpected hpi lock value xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH042Hpi lock owner [xxxxx] doesn't match caller [yyyyy] Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH043Unexpected hpi lock value xxxxx Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH044Signal handler for registered signal 'xxxxx' not found Explanation: This is a JVM internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH045Registration of interrupt signal xxxxx handling failed Explanation: The registration of signal handling for the interrupt signal failed. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH047Override value for JVM interrupt signal xxxxx is not valid or is otherwise unavailable. Explanation: This is a JVM internal error. System action: A warning message is displayed and processing continues. User response: Contact your IBM service representative. JVMLH048Override value for JVM suspend/resume signal xxxxx is not valid or is otherwise unavailable. Explanation: This is a JVM internal error. System action: A warning message is displayed and processing continues. User response: Contact your IBM service representative. JVMLH049Guard page creation failed (errno=xxxxx). Explanation: This is a JVM or an Operating System internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH050Signal stack reqistration failed (errno=xxxxx). Explanation: This is a JVM or an Operating System internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH051Signal stack resetting failed (errno=xxxxx). Explanation: This is a JVM or an Operating System internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH052Guard page resetting failed (errno=xxxxx). Explanation: This is a JVM or an Operating System internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH053Heap-Stack collision detected [max heap xxxxx > yyyyy] Explanation: This is a JVM or an Operating System internal error. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH054_hpiForceStackCommit is not implemented Explanation: The _hpiForceStackCommit function is not implemented for Linux PPC 32-bit and 64-bit architectures. System action: The JVM is terminated. User response: Collect the mustgather data and contact your IBM service representative. JVMLH055 Unable to open /proc/meminfo Explanation: The JVM is not able to open or read the /proc/meminfo file. You might not have the correct permission to access this file. System action: None. User response: Change the file permission. If the problem recurs, contact your IBM service representative. JVMLH056Failed to clean up shared memory. Please free shm id xxxxx manually Explanation: This is an Operating System internal error. System action: None. User response: A warning message is displayed and processing continues. JVMLH057detectNPTL cannot create thread. Explanation: The Native Posix Thread Library (NPTL) is Unable to create the thread. The detectNPTL function detects whether NPTL or the Linux Thread Library is used. System action: The JVM is terminated User response: Collect the mustgather data and contact your IBM service representative. JVMLH060could not allocate network interface IPAddressBufferer Explanation: The JVM cannot allocate memory for the IPAddressBuffer buffer to hold the network interfaces information, because a malloc call failed. System action: The message is written to stderr and processing continues. User response: The C-runtime heap of the process (not the Java™ object heap) is full. Ignore this message if you have disabled networking on your system, otherwise, increase the heap, if that is possible in your environment, or contact your IBM service representative. JVMLH061could not reallocate network interface IPAddressBufferer Explanation: The JVM cannot reallocate space for the IPAddressBuffer buffer to hold the network interfaces information, because a realloc call failed. System action: The message is written to stderr and processing continues. User response: The C-runtime heap of the process (not the Java object heap) is full. Ignore this message if you have disabled networking on your system, otherwise, increase the heap, if that is possible in your environment, or contact your IBM service representative. JVMLH062could not allocate network interface Explanation: The JVM cannot allocate space for the IPAddressBuffer buffer to hold the network interfaces information, because a malloc call failed. System action: The message is written to stderr and processing continues. User response: The C-runtime heap of the process (not the Java object heap) is full. Ignore this message if you have disabled networking on your system, otherwise, increase the heap, if that is possible in your environment, or contact your IBM service representative. JVMLH063Socket creation failed Explanation: An attempt to create a socket has failed in IPv4 because support for IPv4 is not present. System action: The message is written to stderr and processing continues. User response: Ignore this message if you have disabled networking on your system, otherwise check your network setting for IPv4. JVMLH064heap allocation failed Explanation: The JVM cannot allocate heap space for a variable because a malloc call failed. System action: The message is written to stderr and processing continues. User response: The C-runtime heap of the process (not the Java object heap) is full. Ignore this message if you have disabled networking on your system, otherwise, increase the heap, if that is possible in your environment, or contact your IBM service representative. JVMLH065SocketException ioctl SIOCGIFCONF failed Explanation: An exception was thrown when an ioctl [SIOCGIFCONF] function attempted to obtain information about the network interface. System action: The message is written to stderr and processing continues. User response: Ignore this message if you have disabled networking on your system, otherwise contact your IBM service representative. JVMLH066Socket creation failed Explanation: An attempt to create a datagram socket has failed and the error code returned by the operating system is not EPROTONOSUPPORT. Note that an error code of EPRONOTOSUPPORT is returned if the system does not have IPv4 support. System action: The error message is written to the stderr log and an error code of -1 is returned to the caller. User response: Ignore this message if you have disabled networking on your system and your application does not use network sockets. Otherwise, contact your IBM service representative. JVMLH067Heap allocation failed Explanation: The JVM cannot allocate memory for a buffer to hold the network interfaces information when using IPv4. System action: The error messages are written to the stderr log and the socket is closed. User response: Contact your IBM service representative. JVMLH068Heap allocation failed Explanation: The JVM cannot allocate memory for a buffer to hold the network interfaces information when using IPv6. System action: The error messages are written to the stderr log and the socket is closed. User response: Contact your IBM service representative. JVMLH069ioctl call failed (errno=%d) Explanation: An unexpected error occurred in ioctl() and the error is not ERANGE or EINVAL. System action: The error messages are written to the stderr log and the socket is closed. User response: Contact your IBM service representative. JVM error messages for JVMLK JVMLK001Current thread not owner Explanation: A thread has attempted to exit an inflated monitor when it does not own that monitor. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Contact your IBM® service representative. JVMLK002Current thread not owner Explanation: A thread has attempted to exit a flat monitor when it does not own that monitor. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Contact your IBM service representative. JVMLK003Current thread not owner Explanation: A thread has attempted to call a notify() method on an object when it does not own the flat lock on that object. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Correct the Java™ application code. Use a synchronized block or method so that the thread owns the lock on the object before it calls the notify() method. JVMLK004Current thread not owner Explanation: A thread has attempted to call a notify() method on an object when it does not own the inflated lock on that object System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Correct the Java application code. Use a synchronized block or method so that the thread owns the lock on the object before it calls the notify() method. JVMLK005Current thread not owner Explanation: A thread has attempted to call a notifyAll() method on an object when it does not own the flat lock on that object. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Correct the Java application code. Use a synchronized block or method so that the thread owns the lock on the object before it calls the notifyAll() method. JVMLK006Current thread not owner Explanation: A thread has attempted to call a notifyAll() method on an object when it does not own the inflated lock on that object. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Correct the Java application code. Use a synchronized block or method so that the thread owns the lock on the object before it calls the notifyAll() method. JVMLK007Operation interrupted Explanation: A thread has been interrupted during a wait() method by another thread that was calling the interrupt() method on the thread class. System action: The JVM throws a java.lang.InterruptedException. User response: Correct the Java application code so that it handles the InterruptedException. JVMLK008Current thread not owner Explanation: A thread has attempted to call a wait() method on an object when it does not own the lock on that object. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Correct the Java application code. Use a synchronized block or method, so that the thread owns the lock on the object before it calls the wait() method. JVMLK010Current thread not owner Explanation: A thread has attempted to call a wait() method on an object when it does not own the flat lock on that object. System action: The JVM throws a java.lang.IllegalMonitorStateException. User response: Correct the Java application code. Use a synchronized block or method, so that the thread owns the lock on the object before it calls the notifyAll() method. JVMLK011Totally out of thread IDs Explanation: The maximum number of threads that are allowed in the JVM has been exceeded. System action: The JVM is terminated. User response: Reduce the number of threads that have started by the Java application. JVMLK012Expanding monitor pool by monitors to Explanation: The number of inflated monitors (locks) that are required by the Java application has exceeded the number that are available in the monitor pool. The size of the pool has been increased as indicated in the message. This message is issued only if verbose monitor garbage collection mode (command line option -Xverbosemongc) is specified. System action: The number of monitors that are in the pool is increased. User response: This message is for information only and can be ignored. JVMLK013Expanding monitor pool by monitors to Explanation: The number of inflated monitors (locks) that are available in the JVM has been increased. The hash table that is used to index the monitor pool is about to be expanded as indicated in the message. This message is issued only if verbose monitor garbage collection mode (command line option -Xverbosemongc) is specified. System action: The size of the monitor pool hash table is increased as indicated. User response: This message is for information only and can be ignored. JVMLK014Monitor cache GC freed of monitors in ms ( total free) Explanation: During garbage collection, a scan of the monitor cache in the JVM has found the indicated number of unused inflated monitors. This message is issued only if verbose monitor garbage collection mode (command line option -Xverbosemongc) is specified. System action: The indicated number of inflated monitors are freed. User response: This message is for information only and can be ignored. JVMLK015Unlocking - Flat locked when Thread exited Explanation: A thread has terminated while still holding the flat lock on the object indicated. This message is issued only by the PD build. System action: The flat lock on the object is released and thread termination continues. User response: Contact your IBM service representative. JVMLK016Unlocking - Locked when Thread exited Explanation: A thread has terminated while still holding the inflated lock on the object indicated. This message is issued only by the PD build. System action: The inflated lock on the object is released and thread termination continues. User response: Contact your IBM service representative. JVMLK017obj mid monIndex(mid) monIndexToMonitor(monIndex(mid)) Explanation: A thread has terminated while still holding the inflated lock on the object indicated. This message is issued only by the PD build. System action: An internal consistency check on object monitor pointers has failed. User response: Contact your IBM service representative. JVMLK018OutOfMemoryError, sysMalloc returned NULL Explanation: A system memory allocation call has failed while the JVM was initializing its internal monitors. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVMLK019OutOfMemoryError, sysMalloc returned NULL Explanation: A system memory allocation call has failed while the JVM was initializing its internal monitors. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVMLK020Cannot allocate memory for micb table in monPoolInit Explanation: A system memory allocation call has failed while the JVM was initializing its monitor pool. System action: The JVM is terminated. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVMLK021Cannot allocate memory for monitor buffer monPoolExpand Explanation: A system memory allocation call has failed while the JVM was expanding its monitor pool. System action: The JVM is terminated. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVMLK022Cannot allocate memory for new buffer in monPoolExpand Explanation: A system memory allocation call has failed while the JVM was expanding its monitor pool. System action: The JVM is terminated. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVMLK023Cannot allocate memory in inflMonitorInit Explanation: A system memory allocation call has failed while the JVM was initializing an inflated monitor. System action: The JVM is terminated. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVMLK024Failed to obtain local monitor Explanation: Internal error. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMLK025Failed to obtain global monitor Explanation: Internal error. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMLK026Failed to release global monitor Explanation: Internal error. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMLK027Failed to release local monitor Explanation: Internal error. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMLK028Failed to obtain local monitor Explanation: Internal error. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMLK029Failed to release local monitor Explanation: Internal error. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMLK030Cannot allocate memory in lkGetLocalProxy() Explanation: An out-of-memory condition occurred while memory was being allocated for shared JVM locks. System action: The JVM is terminated. User response: Increase the runtime (heap) memory that is available in the process that is running the JVM. JVM error messages for JVMST JVMST001Cannot allocate memory in initWorkPackets Explanation: Not enough virtual storage was available to allocate the concurrent data structures. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM® service representative. JVMST010Cannot allocate memory for ACS area Explanation: Not enough virtual storage was available to allocate the ACS heap. The call to sharedMemoryAlloc() failed. This can happen during the initialization or expansion of the ACS heap. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST011JVMST011 Explanation: Not enough virtual storage was available to allocate the mirrored card table. The call to sysMapMem() failed. This can happen only in the debug build during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST012Cannot allocate memory in concurrentInit() Explanation: Not enough virtual storage was available to allocate the stop_the_world_mon monitor. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST013Cannot allocate memory in initGcHelpers(2) Explanation: Not enough virtual storage was available to allocate the ack_mon monitor. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST014Cannot allocate memory in initConBKHelpers(3) Explanation: Not enough virtual storage was available to start a concurrent background thread. The call to xmCreateSystemThread() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST015Cannot commit memory in initConcurrentRAS Explanation: An error occurred during an attempt to commit memory for the mirrored card table. The call to sysCommitMem() failed. This only happen only in the debug build during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST016Cannot allocate memory for initial Java heap Explanation: Not enough virtual storage was available to allocate the Java™ heap. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative JVMST017Cannot allocate memory in initializeMarkAndAllocBits(markbits1) Explanation: Not enough virtual storage was available to allocate the markbits vector. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST018Cannot allocate memory for initializeMarkAndAllocBits(allocbits1) Explanation: Not enough virtual storage was available to allocate the allocbits vector. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST019Cannot allocate memory in allocateToMiddlewareHeap Explanation: An error occurred during an attempt to commit memory for the Java heap. The call to sysCommitMem() failed. This can happen during initialization or during expansion of the heap. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST020Cannot allocate memory in allocateToTransientHeap Explanation: An error occurred during an attempt to commit memory for the transient heap. The call to sysCommitMem() failed. This can happen during initialization or during expansion of the transient heap. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST021Cannot allocate memory in initParallelMark(stackEnd Explanation: Not enough storage was available in the Java heap to allocate the stackEnd object. The call to allocMiddlewareArray() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more Java heap storage by increasing the -Xmx value. If the problem remains, contact your IBM service representative. JVMST022Cannot allocate memory in initParallelMark(pseudoClass Explanation: Not enough storage was available in the Java heap to allocate the pseudoClass object. The call to allocMiddlewareObject() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more Java heap storage by increasing the -Xmx value. If the problem remains, contact your IBM service representative. JVMST023Cannot allocate memory in initializeGCFacade Explanation: Not enough virtual storage was available to allocate the verbosegc buffer. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST024Cannot allocate memory in concurrentInit(base-Malloc) Explanation: Not enough virtual storage was available to allocate the concurrent data structures. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative JVMST025Cannot allocate memory in icDoseThread Explanation: Not enough virtual storage was available to allocate a sys_thread_stack_segment. The call to sysCalloc() failed. This can happen only during garbage collection. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST026Cannot allocate memory in initializeMiddlewareHeap (not enough memory) Explanation: An error occurred during an attempt to allocate storage to the middleware heap. The call to allocateToMiddlewareHeap() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST027Cannot allocate memory for System Heap area in allocateSystemHeapMemory Explanation: Not enough virtual storage was available to allocate storage for the system heap. The call to sharedMemoryAlloc() failed. This can happen during initialization or during expansion of the system heap. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST028Cannot commit memory in RASinitShadowHeap Explanation: An error occurred during an attempt to commit memory for the shadow heap. The call to sysCommitMem() failed. This can happen only during initialization when the trace option -Dibm.dg.trc.print=st_concurrent_shadow_heap is used. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST029Cannot allocate memory in jvmpi_scan_thread_roots Explanation: Not enough virtual storage was available to allocate a sys_thread_stack_segment. The call to sysCalloc() failed. This can happen only during garbage collection when JVMPI is running. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST030Cannot allocate memory in initializeCardTable Explanation: Not enough virtual storage was available to allocate the card table. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST031Cannot commit memory in initializeCardTable Explanation: An error occurred during an attempt to commit memory for the card table. The call to sysCommitMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST032Cannot allocate memory in initializeTransientHeap Explanation: An error occurred during an attempt to allocate storage to the transient heap. The call to allocateToTransientHeap() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST033Cannot allocate memory in initializeMarkAndAllocBits(markbits2) Explanation: An error occurred during an attempt to commit memory for the markbits vector. The call to sysCommitMem() failed. This can happen only during initialization when -Xresettable is running. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST034Cannot allocate memory in initializeMarkAndAllocBits(allocbits2) Explanation: An error occurred during an attempt to commit memory for the allocbits vector. The call to sysCommitMem() failed. This can happen only during initialization when -Xresettable is running. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST035Cannot allocate memory in initializeMiddlewareHeap (markbits) Explanation: An error occurred during an attempt to commit memory for the markbits vector. The call to sysCommitMem() failed. This can happen only during initialization when -Xresettable is not running. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST036Cannot allocate memory in initializeMiddlewareHeap (allocbits) Explanation: An error occurred during an attempt to commit memory for the allocbits vector. The call to sysCommitMem() failed. This can happen only during initialization when -Xresettable is not running. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST039Cannot allocate Shared Memory segment in initializeSharedMemory Explanation: An error occurred during an attempt to create shared memory. The call to xhpiSharedMemoryCreate() failed. This can happen only during initialization when -Xjvmset is running. System action: A return code of JNI_ENOMEM is passed back to the JNI_CreateJavaVM call. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST040Cannot initialize Java heap in allocateToMiddlewareHeap Explanation: An error occurred during an attempt to commit memory for the Java heap. The call to sysCommitMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST042Cannot allocate memory in initParallelMark(base-Malloc) Explanation: Not enough virtual storage was available to allocate the parallel mark data structures. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST043Cannot allocate memory in concurrentScanThread Explanation: Not enough virtual storage was available to allocate a sys_thread_stack_segment. The call to sysCalloc() failed. This can happen only during concurrent marking. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST044Cannot allocate memory in concurrentInitLogCleaning Explanation: Not enough virtual storage was available to allocate the cleanedbits vector. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST045Cannot commit memory in concurrentInitLogCleaning Explanation: An error occurred during an attempt to commit memory for the cleanedbits. The call to sysCommitMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST046Cannot allocate storage for standalone jab in initializeSharedMemory Explanation: Not enough virtual storage was available to allocate the JAB. The call to sysCalloc() failed. This can happen only during initialization when -Xjvmset is not running. System action: A return code of JNI_ENOMEM is be passed back to the JNI_CreateJavaVM call. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST047Cannot allocate memory in initParallelSweep Explanation: Not enough virtual storage was available to allocate the parallel sweep data structure PBS_ThreadStat. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST048:Could not establish access to shared storage in openSharedMemory Explanation: An error occurred during an attempt to access shared memory. The call to xhpiSharedMemoryOpen() failed. This can happen only during initialization when -Xjvmset is running. System action: A return code of JNI_ENOMEM is passed back to the JNI_CreateJavaVM call. User response: Check that the correct token is being passed in the JavaVMOption. If the problem remains, contact your IBM service representative. JVMST049Worker and Master JVM versions differ Worker JVM version is build type is Master JVM version is build type is Where version is the JVM version (for example 1.3) and build is the build type (DEV, COL, or INT). Explanation: A mismatch has occurred between the Master JVM and a Worker JVM. This can happen only during initialization when -Xjvmse is running. System action: A return code of JNI_ERR is passed back to the JNI_CreateJavaVM call. User response: Ensure that the Master and all Worker JVMs are at the same version level, and all are of the same build type. If the problem remains, contact your IBM service representative. JVMST050Cannot allocate memory for initial Java heap Explanation: An error occurred during an attempt to query memory availability. The call to DosQuerySysInfo() failed. This can happen only during initialization on OS/2®. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST051Cannot allocate memory for initial Java heap Explanation: Not enough virtual storage was available to allocate the Java heap. The call to sysMapMem() failed. This can happen only during initialization on OS/2. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST052Cannot allocate memory for initial Java heap Explanation: Not enough virtual storage was available to allocate the Java heap. The call to sysMapMem() failed. This can happen only during initialization on OS/2 and when JAVA_HIGH_MEMORY has been specified. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST055Cannot allocate memory in initParallelSweep Explanation: Not enough virtual storage was available to allocate the parallel sweep data structure pbs_scoreboard. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST056Cannot allocate memory in initConBKHelpers(1) Explanation: Not enough virtual storage available to allocate the bk_activation_mon monitor. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST057Cannot allocate memory in initGcHelpers(1) Explanation: Not enough virtual storage was available to allocate the request_mon monitor. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST058Cannot allocate memory in initGcHelpers(3) Explanation: Not enough virtual storage available to start a gcHelper thread. The call to xmCreateSpecialSystemThread() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST059Cannot allocate memory in scanThread Explanation: Not enough virtual storage was available to allocate a sys_thread_stack_segment. The call to sysCalloc() failed. This can happen only during garbage collection. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST060Cannot allocate memory in concurrentInit() - bk_threads-sysCalloc Explanation: Not enough virtual storage was available to allocate concurrent background thread(s). The call to sysCalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST061Cannot allocate memory in concurrentInit Explanation: Not enough virtual storage was available to allocate the concurrent tracer_mon monitor. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST062Cannot allocate memory in initializeFRBits Explanation: Not enough virtual storage was available to allocate the FRBits. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST063Cannot allocate memory in initializeFRBits Explanation: Not enough virtual storage was available to commit the FRBits in resettable code. The call to sysCommitMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST064Cannot allocate memory in initializeMiddlewareHeap Explanation: Not enough virtual storage was available to commit the FRBits in resettable code. The call to sysCommitMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST065Cannot allocate memory for break tables in initializeIncrementalCompaction Explanation: Not enough virtual storage was available to create the break tables for incremental compaction. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST066Exception (sysGetExceptionCode()) received during openSharedMemory with token(token) Explanation: Cannot access shared storage that is defined by the token that xhpiSharedMemoryOpen returns. This can happen only during initialization. System action: The JVM is terminated. User response: Check whether the token that is being passed by -Xjvmset is valid. If the problem remains, contact your IBM service representative. JVMST067Invalid method_type detected in heap allocation(allocObject) Explanation: A class type that was detected during object allocation was not Middleware, Primordial, or Application. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST068Invalid method_type detected in heap allocation (allocArray) Explanation: A class type that was detected during array allocation was not Middleware or Application. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST069Invalid method_type detected in heap allocation (allocConextArray) Explanation: A class type that was detected during context array allocation was not Middleware or Application. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST070Invalid method_type detected in heap allocation (allocConextObject) Explanation: A class type that was detected during context object allocation was not Middleware or Application. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST080-verbose:gc flag is set Explanation: The JVM was started with switch -verbose:gc System action: During garbage collection cycles, informational messages are written to stderr (or to a file that you specify). User response: None. JVMST081File open failed for verbose:gc output file %s Explanation: An error occurred during the opening of the file for verbose:gc output. System action: The JVM directs verbose garbage collection messages to stderr instead. JVM initialization continues. User response: Review stderr for verbose:gc messages. Ensure that environment variable IBM_JVM_ST_VERBOSEGC_LOG specifies a valid filename. JVMST082-verbose:gc output will be written to %s Explanation: verbose:gc output will be written to the names HFS file. System action: The JVM sends verbose:gc messages to the names file. JVM initialization continues. User response: Review stderr for verbose:gc messages. JVMST083Exception occurred while calculating freeList size for JVMMI Explanation: An exception occurred while the jvmmiOutOfMemoryEvent was being set up. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST084Cannot allocate memory in stInit for segment_info Explanation: Not enough virtual storage was available to create the sys_thread_stack_segment. The call to sysCalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST085Cannot suspend threads in gc0 Explanation: An attempt by xmSuspendAllThreads to lock all threads before garbage collection was not successful. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST086verifyHeap() not supported in single thread mode Explanation: ST facade function for heap verification called during GC. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST088Cannot allocate memory in "initializeSCCardTable" Explanation: Not enough virtual storage was available to allocate the shared class card table. The call to sysMapMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST089Cannot commit memory in "initializeSCCardTable" Explanation: An error occurred during an attempt to commit memory for the shared class card table. The call to sysCommitMem() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Contact your IBM service representative. JVMST090Incorrect usage of -Xverbosegclog Explanation: The parameters that were passed with -Xverbosegclog are not correct. System action: The JVM is terminated. User response: Refer to the information about -Xverbosegclog (see Appendix G. Command-line parameters). If the problem remains, contact your IBM service representative. JVMST092Cannot allocate memory in initializeGCFacade Explanation: Not enough virtual storage was available to allocate the verbosegc trace buffer. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST093file open failed for verbose:gc output file Explanation: Cannot open the verbosegc log file. System action: Verbosegc log output is written to the stderr log. User response: Check whether the entered file name is valid and whether open is a valid operation on this file. JVMST094file open failed for verbose:gc output file Explanation: Cannot open the verbosegc log file. System action: Verbosegc log output is written to the stderr log. User response: Check whether the entered file name is valid and whether open is a valid operation on this file. JVMST095Incorrect usage of -Xverbosegclog Explanation: The parameters that were passed with -Xverbosegclog are not correct. System action: The JVM is terminated. User response: Refer to the information about -Xverbosegclog (see Appendix G. Command-line parameters). If the problem remains, contact your IBM service representative. JVMST096Out of memory in setVerbosegcRedirectionFormatScreen Explanation: Not enough virtual storage was available to allocate the verbosegc buffer. The call to sysMalloc() failed. This can happen only during initialization. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMST097Concurrent GC is disabled Explanation: An attempt has been made to turn on concurrent verbosegc by using the dynamic switching interface when concurrent gc is not enabled. System action: The JVM is terminated. User response: Review the dynamic switching interface. JVMST099Live Memory count inaccuracy, traced %d bytes, STW %d bytes Explanation: The counter that tracks total number of bytes consumed by live objects contains inaccurate value. This inaccurate value can affect the heuristics used in some GC algorithms. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. JVMST100 Unable to allocate an array object. Array element exceeds IBM JDK limit of 268435455 elements Explanation: The array could not be allocated in the requested heap because the size requested for the array exceeds the maximum size that is permitted by the IBM JDK. System action: JVM terminated. User response: Reduce the array size to less than 256 MB. JVMST101 Unable to allocate an array object. Array element exceeds IBM JDK limit of 268435455 elements Explanation: The array could not be allocated in the middleware heap because the size requested for the array exceeds the maximum size that is permitted by the IBM JDK. System action: JVM terminated. User response: Reduce the array size to less than 256 MB. JVMST102 Unable to allocate an array object. Array element exceeds IBM JDK limit of 268435455 elements Explanation: The array could not be pinned and allocated from the pinned cluster because the size requested for the array exceeds the maximum size that is permitted by the IBM JDK. System action: JVM terminated. User response: Reduce the array size to less than 256 MB. JVMST103 Unable to allocate an array object. Array element exceeds IBM JDK limit of 268435455 elements Explanation: The array could not be allocated from the middleware or transient heap because the size requested for the array exceeds the maximum size that is permitted by the IBM JDK. System action: JVM terminated. User response: Reduce the array size to less than 256 MB. JVMST104 Unable to allocate an array object. Array element exceeds IBM JDK limit of 268435455 elements Explanation: The array could not be allocated from the middleware or transient heap according to the current method context because the size requested for the array exceeds the maximum size that is permitted by the IBM JDK. System action: JVM terminated. User response: Reduce the array size to less than 256 MB. JVMST105 Unable to allocate an array object. Array element exceeds IBM JDK limit of 268435455 elements Explanation: The array could not be allocated from the same heap as the object that has been passed as one of the parameters, because the size requested for the array exceeds the maximum size that is permitted by the IBM JDK. System action: JVM terminated. User response: Reduce the array size to less than 256 MB. JVMST106 Unable to allocate an object. Object size is bigger than 1073741824 bytes Explanation: Cannot allocate a chunk of storage to use as an object, array, or one of a variety of 'special' objects such as pinned object clusters. System action: JVM terminated. User response: Reduce the object size to less than 1 GB. JVMST107 Unable to allocate an object. Object size is bigger than 1073741824 bytes Explanation: Cannot allocate a chunk of storage to use as an object, array, or one of a variety of 'special' objects such as pinned object clusters in the target heap specified. System action: JVM terminated. User response: Reduce the object size to less than 1 GB. JVMST108Insufficient space in Java heap to satisfy allocation request Explanation: Cannot allocate a chunk of storage for use in the Java heap when concurrent is enabled. System action: JVM terminated. User response: Contact your IBM service representative. JVMST109Insufficient space in Java heap to satisfy allocation request Explanation: Cannot allocate a chunk of storage for use in the Java heap when concurrent is disabled. System action: JVM terminated. User response: Contact your IBM service representative. JVMST110Insufficient space in transient Java heap to satisfy allocation request Explanation: Cannot allocate a chunk of storage for use in the Java heap. System action: JVM terminated. User response: Contact your IBM service representative. JVMST111scanThread failed for execenv %p Explanation: scanThread is a JVM function that identifies reachable Java objects on the JVM's Java heap by scanning the threads' stacks during garbage collection. If this function fails, a reachable object might be either collected or moved. This failure is likely to cause an unrecoverable error when a reference is later made to the object that has been moved or had its storage reused. System action: none. User response: The message is for information only. If a failure occurs after this message, contact your IBM service representative and include the stderr log in the document set that you send. JVM error messages for JVMXE JVMXE001OutOfMemoryError, stAllocObject failed Explanation: The JVM cannot create a new java (class) object. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the memory that the application requires. JVMXE002OutOfMemoryError, xeCreateStack failed Explanation: The JVM cannot create a new stack to expand an existing Java™ stack. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the Java stack size that is specified for the application. Increase the Java stack size through the -Xss parameter if required. JVMXE003OutOfMemoryError, stAllocObject for executeJava failed Explanation: The JVM cannot create a new Java (class) object. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the memory that the application requires. JVMXE004OutOfMemoryError, stAllocArray for executeJava failed Explanation: The JVM cannot create a new Java (newArray_quick) object. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the memory that the application requires. JVMXE005OutOfMemoryError, multiArrayAlloc for executeJava failed. Unable to create the Java (multiArray) object due to Out_Of_Memory condition (inside interpreter) Explanation: The JVM cannot create a new Java (multiArray) object. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the memory that the application requires. JVMXE006OutOfMemoryError, stAllocArray for executeJava failed Explanation: The JVM cannot create a new Java (newArray) object. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the memory that the application requires. JVMXE007OutOfMemoryError, multiArrayAlloc failed for x86_multianewarray_quick Explanation: The JVM cannot create a new Java (newMultiArray) object. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the memory that the application requires. JVMXE008Cannot allocate memory for temporary array in remapLocals Explanation: The JVM cannot allocate a temporary array for remapping of Locals. System action: The JVM issues an "Out of memory, aborting" message, and is terminated. User response: Review the memory that the application requires. JVMXE015Cannot allocate memory for XeData in getXeDataAddress Explanation: The JVM cannot allocate memory for a Xedata area in a multi-JVM environment. System action: The JVM issues an "Out of memory, aborting" message, and is terminated. User response: Review the memory that the application requires. JVMXE016Invalid JIT setting for Worker JVM Explanation: A Worker JVM has been started with a -Djava.compiler value that is different from the one that is specified for the Master JVM in a multi-JVM environment. System action: The JVM issues the message and continues processing. User response: Review and correct the start up parameter -Djava.compiler for the Worker JVM. JVMXE017JVM will terminate at user request, Exception match Explanation: The JVM has received a signal to terminate for an exception. System action: The JVM issues the message and is terminated. User response: Review the exception request from the application, and correct the detected error. JVMXE018StackOverflowError, expandJavaStack failed due to Insufficient Java stack size Explanation: Java Stack usage exceeded the limit or size of the Java stack. System action: The JVM throws java.lang.StackOverflowError. User response: Check for any Recursions, unreleased JNI references. JVM error messages for JVMXM JVMXM001OutOfMemoryError, can't create new thread Explanation: This message is issued if the JVM cannot create a new system thread. System action: The JVM throws a java.lang.OutOfMemoryError. User response: Review the number of threads and memory that the application requires. JVMXM002Cannot set resettable mode in a Worker JVM Explanation: This message is issued if a Worker JVM is started with the -Xresettable option. System action: The JVM is terminated. User response: Do not specify the -Xresettable option for a Worker JVM, because it always inherits the resettable option from the Master. JVMXM003Exception %d Caught during Abort Processing Explanation: Here, %d is a JVM exception code. This message is issued during the abort of a failed JVM, if the abort processing itself finds a secondary failure. System action: The JVM is aborted, but the abort processing is incomplete. User response: None. The usual cause of this error is that the original JVM failure was severe enough to cause the abort processing to fail. JVMXM004Error in global locking initialization Explanation: A master or worker JVM has failed to initialize because it cannot create or access the cross-process semaphores that are needed in a shareable JVM environment. Possible reasons for this message are: Not enough system semaphores are available. Each master JVM gets a set of 32 semaphores that its worker JVMs subsequently use. You are running shareable JVMs from different user IDs, and the default file permissions that are used for semaphore files are not correct. System action: The JVM is terminated. User response: Use the ipcs and ipcs -y commands to check the use and availability of system semaphores, as follows: The MNIDS value must be enough for the maximum number of semaphore IDs that are in use at one time. Each master JVM uses a single semaphore ID; other processes might use more. You can change the MNIDS value by using the IPCSEMNIDS parameter that is in the BPXPRM parmlib. The MNSEMS value must be enough for the maximum number of semaphores that are requested in a semaphore set. The master JVM requests a set of 32 semaphores, so the MNSEMS value must be 32 or greater. You can change the MNSEMS value by using the IPCSEMNSEMS parameter that is in the BPXPRM parmlib. For additional information see z/OS® V1R2.0 UNIX® System Services Programming: Assembler Callable Services Reference at http://publibz.boulder.ibm.com/epubs/pdf/bpxzb110.pdf. Check whether the user's umask setting is 011. This sets default permissions of new files to rw-rw-rw-. JVMXM005 Unable to initialize threads Explanation: The JVM could not initialize the main thread. System action: The JVM is terminated. User response: Review system resources and Java™ heap settings. They might be too small. Review the Java installation. JVMXM006 Unable to initialize signal handler, thread create failed Explanation: Cannot create the signal dispatcher thread. System action: The JVM is terminated. User response: Review system resources and the Java installation. JVMXM007Error occurred while initializing System or Runtime class Explanation: The initialization of mirrored system classes has failed. (This error is applicable to shared classes only.) System action: The JVM is terminated. User response: Review system resources and the Java installation. Other system messages that give more specific information might accompany this message. Running with -Xverbose might also be helpful. JVMXM008Error occurred while initializing System Class Explanation: The Java System class initialization method has failed. System action: The JVM is terminated. User response: Review system resources and the Java installation. Other system messages that give more specific information might accompany this message. JVMXM009Error occurred while initializing extra classes Explanation: Additional class initialization for shared classes mode has failed. System action: The JVM is terminated. User response: Review system resources and the Java installation. Other system messages that give more specific information might accompany this message. JVMXM010Cannot allocate memory in eeReserveSlot() Explanation: Internal JVM request for thread data area has failed due to out of memory condition. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM® service representative. JVMXM011Cannot allocate memory in xmPush() Explanation: An internal JVM request has failed because of an out-of-memory condition. System action: The JVM is terminated. User response: Allocate more virtual storage to the JVM region. If the problem remains, contact your IBM service representative. JVMXM012Error occurred in diagnostics initialization(2) Explanation: The JVM RAS trace component initialization has failed. System action: The JVM is terminated. User response: Review system resources and the Java installation. Other system messages that give more specific information might accompany this message. >> Universal Trace Engine error messages U TE001 Error starting trace write thread Explanation: The trace write thread is responsible for writing trace data to disk. It could not be started. System action: The trace data is not written to disk User response: Ensure that you are not running into a system thread limit. If the problem remains, contact your IBM® service representative. UTE002 Cannot open trace control file: %s Explanation: As part of initialization, the Trace Control File is loaded. This time, it cannot be opened. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. UTE003 Cannot obtain size of trace control file: %s Explanation: As part of initialization, when the Trace Control File is loaded, its size is calculated. This time, querying the file size has returned an error. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. UTE004 Trace control file %s is too large Explanation: As part of initialization, the Trace Control File is loaded into memory. However, the file is too large. System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. UTE005 Out of memory condition processing %s Explanation: As part of initialization, the Trace Control File is loaded into memory. However, the attempt to allocate a block of memory to contain the file contents has failed because of a lack of memory. System action: The JVM is terminated. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative. UTE006 Error reading %s Explanation: As part of initialization, the Trace Control File is loaded into memory. However, an error was reported while trying to read the file System action: The JVM is terminated. User response: If the problem remains, contact your IBM service representative. UTE008 Out of memory in rasTraceRegister Explanation: While registering an external trace listener, the JVM attempted to malloc memory to hold the listener's address, but the malloc failed System action: JNI_ENOMEM is returned to the calling program. User response: Try running the JVM with a larger maximum heap size (by using the -Xmx option). If the problem remains, contact your IBM service representative UTE009 Invalid module number (%d) for % Explanation: Internal error in trace initialization. System action: Tracing will not be enabled for this executable. User response: Contact your IBM service representative. UTE010 Name mismatch for module number %d; is %s, should be %s Explanation: Internal error in trace initialization. System action: Tracing will not be enabled for this executable. User response: Contact your IBM service representative. UTE011Active tracepoint array length for %s is %d; should be %d Explanation: Internal error in trace initialization. System action: Tracing will not be enabled for this executable. User response: Contact your IBM service representative. UTE012Trace configuration mismatch for %s Explanation: The CRC for the named executable does not match the previously stored value. System action: Trace is not enabled for this executable. User response: Contact your IBM service representative. UTE013Invalid module number (%d) for %s Explanation: Internal error in trace termination. System action: Tracing will not be terminated for this executable. User response: Contact your IBM service representative. UTE014Name mismatch for module number %d; is %s, should be %s Explanation: Internal error in trace termination. System action: Tracing will not be terminated for this executable. User response: Contact your IBM service representative. UTE016utcMemAlloc failure in utsTraceSet Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java™ heap) is full. Consider reducing the size of the Java heap to save space. UTE017Unable to purge trace buffer for thread %p Explanation: While external trace (trace to a file) was running, trace records were lost. When the buffers were flushed at the point a signal was received, this buffer could not be written. System action: The indicated trace buffer will not be written to disk. User response: Be aware when processing trace files that, because of this error, the files might not be complete. If the problem remains, contact your IBM service representative. UTE018%d trace records lost Explanation: Trace records are lost when the trace buffers option (-Dibm.dg.trc.buffers) is set to nodynamic, both buffers are full, and the first buffer has not yet been written to disk when the second buffer fills up. The JVM wants to switch back to tracing into the first buffer, but because it has not been written to disk, new records are lost. When the first buffer is written, it is reused for new trace records, but this warning tells you how many records were lost before that happened. System action: None. User response: When specifying the buffers property, specify dynamic or remove the specification of nodynamic (for example, -Dibm.dg.trc.buffers=16k,dynamic). UTE019Unable to obtain storage for thread control block Explanation: While processing the startup of a new thread, no storage was available to allocate a trace thread control block. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE020Unable to obtain storage for excluded command list Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE021Unable to obtain storage for excluded command Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE022Initialization of traceLock failed Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE023Initialization of writeEvent failed Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE024Initialization of traceTerminated semaphore failed Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE025Initialization of writeInititialized semaphore failed Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE026Unable to obtain storage for global control block Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE027Error processing early options Explanation: An invalid trace option was detected during trace initialization. System action: JVM initialization may fail due to this error. User response: Check the syntax of any trace options specified in the JVM startup options and system properties. If the options are correct, contact your IBM service representative. UTE028Error processing control file Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE029Error initializing module blocks Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE030Error processing options Explanation: An invalid trace option was detected during trace initialization. System action: JVM initialization may fail due to this error. User response: Check the syntax of any trace options specified in the JVM startup options and system properties. If the options are correct, contact your IBM service representative. UTE031AddComponent failed to allocate memory for %d applids Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE032AddComponent failed to allocate memory for applid Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE033Out of memory handling applids Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE101RC %d from utcEventWait in waitEvent Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE102RC %d from utcEventPost in postEvent Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE103Out of memory in initTraceHeader Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE104Error opening tracefile: %s Explanation: The JVM tried to open a trace output file (name supplied in message), but the open failed. System action: Various. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE105Error writing header to tracefile: %s Explanation: The JVM attempted to write the trace file header to disk but the operation was unsuccessful or only partially successful. System action: Various. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE106Error from utcFileSetLength for tracefile: %s Explanation: The JVM attempted to write a trace buffer to disk, but the operation was unsuccessful or only partially successful. System action: None. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE107Error writing to tracefile: %s Explanation: The JVM attempted to write a trace buffer to disk, but the operation was unsuccessful or only partially successful. System action: None. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE108Error opening next generation: %s Explanation: The trace is moving on to the next generation file and so needs to open the file that is suffixed for this new generation. Unfortunately it cannot open the new file. System action: When running with the PD build, the JVM terminates with an assertion failure. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE109Error performing seek in tracefile: %s Explanation: The JVM has attempted to skip past the header of a trace file so that it can write more trace data into it. Unfortunately, this failed. System action: When running with the PD build, the JVM terminates with an assertion failure. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE110Error performing seek in tracefile: %s Explanation: The JVM has attempted to skip past the header of a trace file so that it can write more trace data into it. Unfortunately, this failed. System action: When running with the PD build, the JVM terminates with an assertion failure. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE111Error opening next state file: %s Explanation: When filling one state trace file and switching to the other, an error occurred while the new (named) file was being opened. System action: When running with the PD build, the JVM terminates with an assertion failure. User response: Consider enabling fewer state trace tracepoints. If the problem remains, contact your IBM service representative. UTE112Error performing seek in tracefile: %s Explanation: The JVM has attempted to skip past the header of a trace file so that it can write more trace data into it. Unfortunately, this failed. System action: When running with the PD build, the JVM terminates with an assertion failure. User response: Check whether your problem with opening the file is caused by, for example, disk space or security settings. If the problem remains, contact your IBM service representative. UTE113RC %d from utsThreadStop in traceWrite Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE114RC %d from utsThreadStop in traceWrite Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE115At least one trace record lost Explanation: Trace Buffers are set to nodynamic and both buffers are full. Before the first buffer could be written to disk, the second one has filled up and the system now wants to write trace records to the first buffer again. However, it cannot do this without overwriting trace data that is already present. System action: All new trace data is discarded until the first buffer can be written to disk. User response: Specify the keyword dynamic on the buffers option (for example, -Dibm.dg.trc.buffers=16k,dynamic), or remove the nodynamic keyword that is there. UTE116Out of memory obtaining trace buffer Explanation: An attempt to obtain an additional trace buffer failed; no storage was available. System action: Trace data will be lost for the thread that encountered this error. If possible, the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. Also, consider reducing the volume of data being traced, or moving the output file to a faster medium, or both. UTE117Counter wrap for tracepoint %6.6X Explanation: When you were using the trace count option (-Dibm.dg.trc.count), a tracepoint was incremented so many times that the count has wrapped back to zero. System action: The counter for the specified tracepoint has wrapped to zero and will count upwards again from there. User response: Determine the action to take. UTE201utcMemAlloc failure in addTraceCmd Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE202Invalid multiplier specified for buffer size Explanation: Buffer size can be specified in multiples of KB or MB. For example, buffers=16k. Note that only lowercase k or m is used. All other letters in this position are not valid. System action: The JVM is terminated. User response: Try again, this time specifying k or m. UTE203Length of buffer size parameter invalid Explanation: A buffer size must be between two and five characters in length including the k or m. The one that you specified was too short or too long. System action: The JVM is terminated. User response: Try again, this time specifying a value between two and five characters in length for the buffer size (for example -Dibm.dg.trc.buffers=1234k). UTE204Buffer size not specified Explanation: The buffers system property expects a buffer size to be specified. You did not provide one. System action: The JVM is terminated. User response: Try again, this time specifying a size for the buffer (for example, -Dibm.dg.trc.buffers=8k). UTE205Dynamic or Nodynamic keyword expected Explanation: The buffers system property takes an optional second argument (after the size). The only allowed values for this are dynamic or nodynamic. System action: The JVM is terminated. User response: Try again, this time specifying a second argument of dynamic or nodynamic on the buffers property (for example, -Dibm.dg.trc.buffers=16k,nodynamic) or by omitting the argument entirely. UTE206Unrecognized keyword in buffer specification Explanation: The buffers system property contains an unrecognized keyword. System action: The JVM is terminated. User response: Correct the syntax and try again. UTE207Too many keywords in buffer specification Explanation: The buffers system property contains too many keywords. System action: The JVM is terminated. User response: Correct the syntax and try again UTE208Usage: buffers=nnnn{k|m} [,dynamic|nodynamic] Explanation: This explanatory message describes the syntax for the buffers system property. System action: The JVM is terminated. User response: Correct the syntax and try again UTE209Out of memory handling exception property Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible, the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE210Filename not supplied in exception specification Explanation: When specifying the exception output file (-Dibm.dg.trc.exception.output), you did not provide a file name. System action: The JVM is terminated. User response: Try again, specifying a file name for the exception.output property (for example,- Dibm.dg.trc.exception.output=fred.trc). UTE211Invalid multiplier for exception wrap limit Explanation: Wrap limit can be specified in multiples of KB (k) or MB (m); for example, -Dibm.dg.trc.exception.output=except,2m. System action: The JVM is terminated. User response: Try again, this time specifying k or m. UTE212Length of wrap limit parameter invalid Explanation: A wrap limit must be between two and five characters in length including the k or m. The one that you specified was too short or too long. System action: The JVM is terminated. User response: Try again, this time specifying a value two through five characters long for the buffer size (for example, -Dibm.dg.trc.exception.output=fred.trc,1234k). UTE213Too many keywords in exception specification Explanation: Only two allowable parameters can follow the exception.output parameter. They are filename and wrap limit. Because you tried to put more options there, this is an error. System action: The JVM is terminated. User response: Remove the third (and later) keywords that are following on the exception.output specification, then retry. UTE214Usage: exception.output=filename[,nnnn{k|m}] Explanation: The way in which you have attempted to specify exception.output does not match the displayed usage. System action: The JVM is terminated. User response: Correct your specification of exception.output and retry. UTE215Out of memory handling state.output property Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible, the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE216Filename not supplied in state.output specification Explanation: State trace output requires a filename, but none was supplied. System action: The JVM terminates. User response: When you specify the state trace output, ensure that you provide a filename (for example, -Dibm.dg.trc.state.output=fred.trc). UTE217Invalid multiplier for state wrap limit Explanation: State trace output file wrap size can be specified in multiples of KB (k) or MB (m) only. System action: The JVM terminates. User response: Retry, specifying state trace output file wrap size in multiples of KB (k) or MB (m); for example, state.output=filename.trc,2m. UTE218Length of wrap limit parameter invalid Explanation: The length of the state trace wrap limit must be two through five characters (including the multiplier k or m, if specified). This rule was broken. System action: The JVM terminates. User response: Retry, specifying state trace output file wrap size in two through five characters including the multiplier (for example, -Dibm.dg.trc.state.output=filename.trc,1234k). UTE219Too many keywords in state.output specification Explanation: State.output is followed by a maximum of two parameters: the file name and the file wrap size. A third parameter is not valid. System action: The JVM terminates. User response: Remove the invalid third (and later) parameters on the state.output specification, and retry. UTE220Usage: state.output=filename[,nnnn{k|m}] Explanation: The usage for a state.output parameter is as shown. System action: The JVM terminates. User response: Correct your input to match the usage displayed and retry. UTE221Out of memory handling output property Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE222Filename not supplied in output specification Explanation: State trace output requires a filename, but none was supplied. System action: The JVM terminates. User response: When you specify the state trace output, ensure that you provide a filename (for example, -Dibm.dg.trc.state.output=fred.trc). UTE223Invalid multiplier for trace wrap limit Explanation: Output file wrap size can be specified in multiples of KB or MB; for example, output=filename.trc,2m. Note that only lowercase k or m is used. All other letters in this position are not valid. System action: The JVM is terminated. User response: Try again, this time specifying k or m. UTE224Length of wrap limit parameter invalid Explanation: A wrap limit must be between two and five characters in length including the k or m. The one that you specified was too short or too long. System action: The JVM is terminated. User response: Try again, this time specifying a value two through five characters long for the buffer size (for example, -Dibm.dg.trc.exception.output=fred.trc,1234k). UTE225Invalid number of trace generations Explanation: When specified, the number trace generations must be 2 through 36. The number that you specified falls outside these limits. System action: The JVM is terminated. User response: Try again, this time specifying a value 2 through 36 for the number of trace generations (for example, -Dibm.dg.trc.output=trace.out,2m,10). UTE226Invalid filename for generation mode Explanation: When trace generations are specified, the trace output file name must contain a # character. This is replaced with the generation character in each trace generation file. The name that you specified does not contain a #. System action: The JVM is terminated. User response: Try again, this time specifying a filename that contains a # (for example, -Dibm.dg.trc.output=trace#.out,2m,10). UTE227Length of generation parameter invalid Explanation: Because the number of trace generations must be 2 through 36, it makes no sense for the length of the trace generations parameter to be anything other than 1 or 2 characters long. The argument that you supplied was less than 1, or greater than 2 characters long. System action: The JVM is terminated. User response: Try again, this time specifying a value 2 through 36 for the number of trace generations (for example, -Dibm.dg.trc.output=trace.out,2m,10). UTE228Too many keywords in output specification Explanation: The output specification supplies an output filename, (optionally) an output file wrap size, and (optionally) several generations. Further arguments are meaningless and should not be specified. System action: The JVM is terminated. User response: Try again, this time omitting the fourth (and following) meaningless arguments. UTE229Usage: output=filename[,nnnn{k|m}[,n]] Explanation: The output specification that you supplied does not meet the described usage. System action: The JVM is terminated. User response: Correct the output specification so that it meets the described usage, and try again. UTE230Empty clauses not allowed in trigger property. Explanation: A null clause was found in a trigger property. System action: The JVM fails to initialize. User response: Correct the trigger property, then retry the operation. This error probably occurred because you entered something like trigger=method,,tpid (that is, you entered too many commas). UTE231utcMemAlloc failure for FormatSpecPath Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE232utcMemAlloc failure for Suffix Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE233utcMemAlloc failure for traceControlPath Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE234Trace control already loaded Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE235Incorrect TRACECONTROL value Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE236LIBPATH and TRACECONTROL options are mutually exclusive Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE237resumecount takes a single integer value from -99999 to +99999 Explanation: The ibm.dg.trc.resumecount property is an integer value -99999 through +99999. The value that you specified was not in this range. System action: The JVM fails to initialize. User response: Correct the resumecount property, then retry the operation. UTE238suspendcount takes a single integer value from -99999 to +99999 Explanation: The ibm.dg.trc.suspendcount property is an integer value -99999 through +99999. The value that you specified was not in this range. System action: The JVM fails to initialize. User response: Correct the suspendcount property, then retry the operation. UTE239resumecount and suspendcount may not both be set. Explanation: You attempted to set the resumecount and suspendcount properties at the same time. This is not allowed. System action: The JVM fails to initialize. User response: Decide which property you want to use, then remove the other UTE240Out of memory while processing properties file Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE241Unable to open properties file %s Explanation: The JVM was unable to open the properties file that was listed in the message. System action: The JVM is terminated. User response: Ensure that the properties file that you have specified really exists. If the problem remains, contact your IBM service representative. UTE242Unable to determine size of properties file %s Explanation: Having opened the trace properties file mentioned in the message, the JVM was unable to determine its size. System action: The JVM is terminated. User response: Ensure that the file that you specified is a valid properties file, and that it is readable. If the problem remains, contact your IBM service representative. UTE243Cannot obtain memory to process %s Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE245Error reading properties file %s Explanation: To process the trace properties file, it is read into memory. Unfortunately, the call to read it into memory has failed. System action: The JVM is terminated. User response: Contact your IBM service representative. UTE246utcMemAlloc failure for FormatSpec Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE247Unrecognized line in %s: "%s" Explanation: While reading the trace properties file, a line has been found that contains a keyword that is not recognized. The properties file name and the offending line are included in the text of the message. System action: The JVM is terminated. User response: Correct the line in error and try again. UTE248Unrecognized option : "%s" Explanation: While processing the trace options, an unrecognized keyword has been encountered. System action: The JVM is terminated. User response: Correct or remove the option in error and try again. UTE249utcMemAlloc failure for UtSpecial Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE250utcMemAlloc failure for UtSpecial Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE251utcMemAlloc failure for UtItem Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE252utcMemAlloc for trace array for %s failed Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE253Invalid range: %6.6X-%6.6X Explanation: You can specify ranges of tracepoints; for example, tpid(c001-c01f). However if you do, the second number must be bigger than the first. System action: The JVM is terminated. User response: Correct the tpid range and retry. UTE254Tracepoint id is not a valid hex string Explanation: Tpids (trace point ids) are expressed as a hex number 1 through 6 characters long and including only the characters 0 through 9 and a through f (also A through F). The tpid that you specified does not meet these criteria. System action: The JVM is terminated. User response: Correct the tpid and try again. UTE255Invalid range: %6.6X-%6.6X Explanation: Tpids (trace point ids) are expressed as a hex number 1 through 6 characters long and including only the characters 0 through 9 and a through f (also A through F). The tpid that you specified does not meet these criteria. System action: The JVM is terminated. User response: Correct the tpid and try again. UTE256Invalid tracepoint id: %6.6X Explanation: The specified tracepoint does not exist in this build. System action: The JVM may terminate. User response: Modify the trace properties, removing or correcting the reference to this tpid. UTE257Tracepoint %6.6X is not included in this build Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE258Tracepoint id is not a valid hex string Explanation: You used an invalid hex number when specifying tracepoint ids for application trace System action: The JVM terminates. User response: Correct the specification and retry. UTE259utcMemAlloc failure in setTraceState Explanation: While trying to process a trace option, a malloc failed. System action: The JVM may fail as a result of this error. User response: System memory (not Java heap) is full. Consider reducing the size of the Java heap to save space. UTE260Trace selection specification incomplete:\n%s Explanation: The input line shown above ends at an unexpected point. System action: The JVM is terminated. User response: Correct the line that is indicated in the message and try again. UTE261Syntax error encountered at offset %d in:\n%s Explanation: A syntax error is at the indicated position in the line displayed. System action: The JVM is terminated. User response: Correct the line that is indicated in the message, and try again. UTE262Error processing options Explanation: An invalid trace option was detected during trace initialization. System action: JVM initialization may fail due to this error. User response: Check the syntax of any trace options specified in the JVM start-up options and system properties. If the options are correct, contact your IBM service representative. UTE263Error processing options Explanation: An invalid trace option was detected during trace initialization. System action: JVM initialization may fail due to this error. User response: Check the syntax of any trace options specified in the JVM startup options and system properties. If the options are correct, contact your IBM service representative. UTE301RC %d from utcMutexEnter in getTraceLock Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE302RC %d from utcMutexExit in freeTraceLock Explanation: Internal error. System action: None. User response: Contact your IBM service representative. UTE303Invalid special character '%c' in a trace filename. Only %p, %d and %t are allowed. Explanation: Trace output file naming can be modified using special operators. The only supported operators are %p, %d and %t (process ID, date, and time, respectively). System action: The JVM fails to initialize. User response: Remove any % characters from the filename and retry. UTE304Missing closing bracket(s) in trigger property. Explanation: The trigger property did not end in a closing bracket. System action: The JVM fails to initialize. User response: Correct the brackets on the trigger property, then retry the operation. UTE305Out of memory processing trigger property. Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE306TraceFormat.dat is incorrect version Explanation: The Trace format file, TraceFormat.dat, contains a version field. During trace initialization, the contents of this field have been checked and are not what the JVM expected. This could mean that you are picking up the Trace format file from a different release of the JVM. System action: Warning only. This message is issued, but no action is taken. User response: Specify the location of the correct version of the Trace Format file by using the -Dibm.dg.trc.format= system property. UTE307TraceFormat.dat is incorrect format Explanation: The Trace format file TraceFormat.dat contains a version field. During trace initialization, the JVM could not locate this version number because the file is in an unexpected format. System action: The JVM terminates. User response: Specify the location of the correct version of the Trace Format file by using the -Dibm.dg.trc.format= system property. UTE308TraceFormat.dat is incorrect version Explanation: The Trace format file TraceFormat.dat contains a version field. During trace initialization, the contents of this field have been checked and were not what this JVM expected. This could mean that you are picking up the Trace format file from a different release of the JVM. System action: Warning only. This message is issued but no action is taken. User response: Specify the location of the correct version of the Trace Format file by using the -Dibm.dg.trc.format= system property. UTE309Cannot obtain memory for format table Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE310Unable to open trace format file %s Explanation: During trace initialization, the JVM reads the Trace format file into memory. It was unable to open the file, so was unable to do this. System action: Trace format file is not read. Trace is not initialized. User response: Specify the location of the correct version of the Trace format file by using the -Dibm.dg.trc.format= system property. If the problem remains, contact your IBM service representative. UTE311Unable to determine size of trace format file %s Explanation: During trace initialization, the JVM reads the Trace format file into memory. It was unable to open the file, so was unable to do this. System action: Trace format file is not read. Trace is not initialized. User response: Specify the location of the correct version of the Trace Format file by using the -Dibm.dg.trc.format= system property. If the problem remains, contact your IBM service representative. UTE312Cannot obtain memory to process %s Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. UTE313Error reading trace format file %s Explanation: During trace initialization, the JVM has attempted to create an in-memory copy of the Trace format file. An error occurred while the file was being read. System action: The JVM terminates. User response: Specify the location of the correct version of the Trace format file by using the -Dibm.dg.trc.format= system property. If the problem remains, contact your IBM service representative. UTE314Unable to open tracepoint counter file Explanation: The tracepoint count option has been specified and an attempt was made to open the count output file, but this failed. System action: The JVM continues. User response: If the problem remains, contact your IBM service representative. UTE315Counters redirected to stderr Explanation: The tracepoint count option has been specified but the attempt to open the count output file failed. The output is being redirected to stderr instead System action: The JVM continues. User response: None. UTE316Signed number not permitted in this context "%s" Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, a negative delay count was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. If a delaycount is specified, it must be a positive number. UTE317Invalid character(s) encountered in decimal number "%s" Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, a non-numeric character was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. If a delaycount is specified, it must contain only the characters 0 through 9. UTE318Number too long or too short "%s" Explanation: When a clause in the system property -Dibm.dg.trc.trigger was being processed, a bad delay count was found. System action: The JVM fails to initialize. User response: Check the contents of the trigger=tpid(...), method(...), and group(...) clauses. If a delaycount is specified, it must be between one and eight digits long. UTE319Cannot allocate memory for trace module blocks Explanation: While processing trace initialization, no storage was available to allocate an internal structure. System action: Memory for this process is either fragmented or exhausted. If possible the JVM will continue to run, but may fail as a result of this condition. User response: If running with a very large Java heap, try reducing its size to allow allocation of non-Java objects. ============================================= SECTION 5: ============================================= -- Throwable Class Hierarchy class java.lang.Throwable (implements java.io.Serializable) class java.lang.Error class java.awt.AWTError class java.lang.LinkageError class java.lang.ClassCircularityError class java.lang.ClassFormatError class java.lang.ExceptionInInitializerError class java.lang.IncompatibleClassChangeError class java.lang.AbstractMethodError class java.lang.IllegalAccessError class java.lang.InstantiationError class java.lang.NoSuchFieldError class java.lang.NoSuchMethodError class java.lang.NoClassDefFoundError class java.lang.UnsatisfiedLinkError class java.lang.VerifyError class java.lang.ThreadDeath class java.lang.VirtualMachineError class java.lang.InternalError class java.lang.OutOfMemoryError class java.lang.StackOverflowError class java.lang.UnknownError class java.lang.Exception class java.awt.AWTException class java.security.acl.AclNotFoundException class java.rmi.AlreadyBoundException class java.lang.ClassNotFoundException class java.lang.CloneNotSupportedException class java.rmi.server.ServerCloneException class java.util.zip.DataFormatException class java.security.DigestException class java.io.IOException class java.io.CharConversionException class java.io.EOFException class java.io.FileNotFoundException class java.io.InterruptedIOException class java.net.MalformedURLException class java.io.ObjectStreamException class java.io.InvalidClassException class java.io.InvalidObjectException class java.io.NotActiveException class java.io.NotSerializableException class java.io.OptionalDataException class java.io.StreamCorruptedException class java.io.WriteAbortedException class java.net.ProtocolException class java.rmi.RemoteException class java.rmi.AccessException class java.rmi.ConnectException class java.rmi.ConnectIOException class java.rmi.server.ExportException class java.rmi.server.SocketSecurityException class java.rmi.MarshalException class java.rmi.NoSuchObjectException class java.rmi.ServerError class java.rmi.ServerException class java.rmi.ServerRuntimeException class java.rmi.server.SkeletonMismatchException class java.rmi.server.SkeletonNotFoundException class java.rmi.StubNotFoundException class java.rmi.UnexpectedException class java.rmi.UnknownHostException class java.rmi.UnmarshalException class java.net.SocketException class java.net.BindException class java.net.ConnectException class java.net.NoRouteToHostException class java.io.SyncFailedException class java.io.UTFDataFormatException class java.net.UnknownHostException class java.net.UnknownServiceException class java.io.UnsupportedEncodingException class java.util.zip.ZipException class java.lang.IllegalAccessException class java.lang.InstantiationException class java.lang.InterruptedException class java.beans.IntrospectionException class java.lang.reflect.InvocationTargetException class java.security.KeyException class java.security.InvalidKeyException class java.security.KeyManagementException class java.security.acl.LastOwnerException class java.security.NoSuchAlgorithmException class java.lang.NoSuchFieldException class java.lang.NoSuchMethodException class java.security.NoSuchProviderException class java.rmi.NotBoundException class java.security.acl.NotOwnerException class java.text.ParseException class java.beans.PropertyVetoException class java.lang.RuntimeException class java.lang.ArithmeticException class java.lang.ArrayStoreException class java.lang.ClassCastException class java.util.EmptyStackException class java.lang.IllegalArgumentException class java.lang.IllegalThreadStateException class java.security.InvalidParameterException class java.lang.NumberFormatException class java.lang.IllegalMonitorStateException class java.lang.IllegalStateException class java.awt.IllegalComponentStateException class java.lang.IndexOutOfBoundsException class java.lang.ArrayIndexOutOfBoundsException class java.lang.StringIndexOutOfBoundsException class java.util.MissingResourceException class java.lang.NegativeArraySizeException class java.util.NoSuchElementException class java.lang.NullPointerException class java.security.ProviderException class java.lang.SecurityException class java.rmi.RMISecurityException class java.sql.SQLException class java.sql.SQLWarning class java.sql.DataTruncation class java.rmi.server.ServerNotActiveException class java.security.SignatureException class java.util.TooManyListenersException class java.awt.datatransfer.UnsupportedFlavorException -- Class Hierarchy: java.lang.Object java.lang.Boolean (implements java.lang.Comparable, java.io.Serializable) java.lang.Character (implements java.lang.Comparable, java.io.Serializable) java.lang.Character.Subset java.lang.Character.UnicodeBlock java.lang.Class (implements java.lang.reflect.AnnotatedElement, java.lang.reflect.GenericDeclaration, java.io.Serializable, java.lang.reflect.Type) java.lang.ClassLoader java.lang.Compiler java.lang.Enum (implements java.lang.Comparable, java.io.Serializable) java.lang.Math java.lang.Number (implements java.io.Serializable) java.lang.Byte (implements java.lang.Comparable) java.lang.Double (implements java.lang.Comparable) java.lang.Float (implements java.lang.Comparable) java.lang.Integer (implements java.lang.Comparable) java.lang.Long (implements java.lang.Comparable) java.lang.Short (implements java.lang.Comparable) java.lang.Package (implements java.lang.reflect.AnnotatedElement) java.security.Permission (implements java.security.Guard, java.io.Serializable) java.security.BasicPermission (implements java.io.Serializable) java.lang.RuntimePermission java.lang.Process java.lang.ProcessBuilder java.lang.Runtime java.lang.SecurityManager java.lang.StackTraceElement (implements java.io.Serializable) java.lang.StrictMath java.lang.String (implements java.lang.CharSequence, java.lang.Comparable, java.io.Serializable) java.lang.StringBuffer (implements java.lang.CharSequence, java.io.Serializable) java.lang.StringBuilder (implements java.lang.CharSequence, java.io.Serializable) java.lang.System java.lang.Thread (implements java.lang.Runnable) java.lang.ThreadGroup (implements java.lang.Thread.UncaughtExceptionHandler) java.lang.ThreadLocal java.lang.InheritableThreadLocal java.lang.Throwable (implements java.io.Serializable) java.lang.Error java.lang.AssertionError java.lang.LinkageError java.lang.ClassCircularityError java.lang.ClassFormatError java.lang.UnsupportedClassVersionError java.lang.ExceptionInInitializerError java.lang.IncompatibleClassChangeError java.lang.AbstractMethodError java.lang.IllegalAccessError java.lang.InstantiationError java.lang.NoSuchFieldError java.lang.NoSuchMethodError java.lang.NoClassDefFoundError java.lang.UnsatisfiedLinkError java.lang.VerifyError java.lang.ThreadDeath java.lang.VirtualMachineError java.lang.InternalError java.lang.OutOfMemoryError java.lang.StackOverflowError java.lang.UnknownError java.lang.Exception java.lang.ClassNotFoundException java.lang.CloneNotSupportedException java.lang.IllegalAccessException java.lang.InstantiationException java.lang.InterruptedException java.lang.NoSuchFieldException java.lang.NoSuchMethodException java.lang.RuntimeException java.lang.ArithmeticException java.lang.ArrayStoreException java.lang.ClassCastException java.lang.EnumConstantNotPresentException java.lang.IllegalArgumentException java.lang.IllegalThreadStateException java.lang.NumberFormatException java.lang.IllegalMonitorStateException java.lang.IllegalStateException java.lang.IndexOutOfBoundsException java.lang.ArrayIndexOutOfBoundsException java.lang.StringIndexOutOfBoundsException java.lang.NegativeArraySizeException java.lang.NullPointerException java.lang.SecurityException java.lang.TypeNotPresentException java.lang.UnsupportedOperationException java.lang.Void Interface Hierarchy java.lang.Appendable java.lang.CharSequence java.lang.Cloneable java.lang.Comparable java.lang.Iterable java.lang.Readable java.lang.Runnable java.lang.Thread.UncaughtExceptionHandler -- All classes: All Classes AbstractAction AbstractAnnotationValueVisitor6 AbstractBorder AbstractButton AbstractCellEditor AbstractCollection AbstractColorChooserPanel AbstractDocument AbstractDocument.AttributeContext AbstractDocument.Content AbstractDocument.ElementEdit AbstractElementVisitor6 AbstractExecutorService AbstractInterruptibleChannel AbstractLayoutCache AbstractLayoutCache.NodeDimensions AbstractList AbstractListModel AbstractMap AbstractMap.SimpleEntry AbstractMap.SimpleImmutableEntry AbstractMarshallerImpl AbstractMethodError AbstractOwnableSynchronizer AbstractPreferences AbstractProcessor AbstractQueue AbstractQueuedLongSynchronizer AbstractQueuedSynchronizer AbstractScriptEngine AbstractSelectableChannel AbstractSelectionKey AbstractSelector AbstractSequentialList AbstractSet AbstractSpinnerModel AbstractTableModel AbstractTypeVisitor6 AbstractUndoableEdit AbstractUnmarshallerImpl AbstractWriter AccessControlContext AccessControlException AccessController AccessException Accessible AccessibleAction AccessibleAttributeSequence AccessibleBundle AccessibleComponent AccessibleContext AccessibleEditableText AccessibleExtendedComponent AccessibleExtendedTable AccessibleExtendedText AccessibleHyperlink AccessibleHypertext AccessibleIcon AccessibleKeyBinding AccessibleObject AccessibleRelation AccessibleRelationSet AccessibleResourceBundle AccessibleRole AccessibleSelection AccessibleState AccessibleStateSet AccessibleStreamable AccessibleTable AccessibleTableModelChange AccessibleText AccessibleTextSequence AccessibleValue AccountException AccountExpiredException AccountLockedException AccountNotFoundException Acl AclEntry AclNotFoundException Action Action ActionEvent ActionListener ActionMap ActionMapUIResource Activatable ActivateFailedException ActivationDataFlavor ActivationDesc ActivationException ActivationGroup ActivationGroup_Stub ActivationGroupDesc ActivationGroupDesc.CommandEnvironment ActivationGroupID ActivationID ActivationInstantiator ActivationMonitor ActivationSystem Activator ACTIVE ActiveEvent ACTIVITY_COMPLETED ACTIVITY_REQUIRED ActivityCompletedException ActivityRequiredException AdapterActivator AdapterActivatorOperations AdapterAlreadyExists AdapterAlreadyExistsHelper AdapterInactive AdapterInactiveHelper AdapterManagerIdHelper AdapterNameHelper AdapterNonExistent AdapterNonExistentHelper AdapterStateHelper AddressHelper Addressing AddressingFeature Adjustable AdjustmentEvent AdjustmentListener Adler32 AffineTransform AffineTransformOp AlgorithmMethod AlgorithmParameterGenerator AlgorithmParameterGeneratorSpi AlgorithmParameters AlgorithmParameterSpec AlgorithmParametersSpi AllPermission AlphaComposite AlreadyBound AlreadyBoundException AlreadyBoundHelper AlreadyBoundHolder AlreadyConnectedException AncestorEvent AncestorListener AnnotatedElement Annotation Annotation AnnotationFormatError AnnotationMirror AnnotationTypeMismatchException AnnotationValue AnnotationValueVisitor Any AnyHolder AnySeqHelper AnySeqHelper AnySeqHolder AppConfigurationEntry AppConfigurationEntry.LoginModuleControlFlag Appendable Applet AppletContext AppletInitializer AppletStub ApplicationException Arc2D Arc2D.Double Arc2D.Float Area AreaAveragingScaleFilter ARG_IN ARG_INOUT ARG_OUT ArithmeticException Array Array ArrayBlockingQueue ArrayDeque ArrayIndexOutOfBoundsException ArrayList Arrays ArrayStoreException ArrayType ArrayType AssertionError AsyncBoxView AsyncHandler AsynchronousCloseException AtomicBoolean AtomicInteger AtomicIntegerArray AtomicIntegerFieldUpdater AtomicLong AtomicLongArray AtomicLongFieldUpdater AtomicMarkableReference AtomicReference AtomicReferenceArray AtomicReferenceFieldUpdater AtomicStampedReference AttachmentMarshaller AttachmentPart AttachmentUnmarshaller Attr Attribute Attribute Attribute Attribute AttributeChangeNotification AttributeChangeNotificationFilter AttributedCharacterIterator AttributedCharacterIterator.Attribute AttributedString AttributeException AttributeInUseException AttributeList AttributeList AttributeList AttributeListImpl AttributeModificationException AttributeNotFoundException Attributes Attributes Attributes Attributes.Name Attributes2 Attributes2Impl AttributeSet AttributeSet AttributeSet.CharacterAttribute AttributeSet.ColorAttribute AttributeSet.FontAttribute AttributeSet.ParagraphAttribute AttributeSetUtilities AttributesImpl AttributeValueExp AudioClip AudioFileFormat AudioFileFormat.Type AudioFileReader AudioFileWriter AudioFormat AudioFormat.Encoding AudioInputStream AudioPermission AudioSystem AuthenticationException AuthenticationException AuthenticationNotSupportedException Authenticator Authenticator.RequestorType AuthorizeCallback AuthPermission AuthProvider Autoscroll AWTError AWTEvent AWTEventListener AWTEventListenerProxy AWTEventMulticaster AWTException AWTKeyStroke AWTPermission BackingStoreException BAD_CONTEXT BAD_INV_ORDER BAD_OPERATION BAD_PARAM BAD_POLICY BAD_POLICY_TYPE BAD_POLICY_VALUE BAD_QOS BAD_TYPECODE BadAttributeValueExpException BadBinaryOpValueExpException BadKind BadLocationException BadPaddingException BadStringOperationException BandCombineOp BandedSampleModel BaseRowSet BasicArrowButton BasicAttribute BasicAttributes BasicBorders BasicBorders.ButtonBorder BasicBorders.FieldBorder BasicBorders.MarginBorder BasicBorders.MenuBarBorder BasicBorders.RadioButtonBorder BasicBorders.RolloverButtonBorder BasicBorders.SplitPaneBorder BasicBorders.ToggleButtonBorder BasicButtonListener BasicButtonUI BasicCheckBoxMenuItemUI BasicCheckBoxUI BasicColorChooserUI BasicComboBoxEditor BasicComboBoxEditor.UIResource BasicComboBoxRenderer BasicComboBoxRenderer.UIResource BasicComboBoxUI BasicComboPopup BasicControl BasicDesktopIconUI BasicDesktopPaneUI BasicDirectoryModel BasicEditorPaneUI BasicFileChooserUI BasicFormattedTextFieldUI BasicGraphicsUtils BasicHTML BasicIconFactory BasicInternalFrameTitlePane BasicInternalFrameUI BasicLabelUI BasicListUI BasicLookAndFeel BasicMenuBarUI BasicMenuItemUI BasicMenuUI BasicOptionPaneUI BasicOptionPaneUI.ButtonAreaLayout BasicPanelUI BasicPasswordFieldUI BasicPermission BasicPopupMenuSeparatorUI BasicPopupMenuUI BasicProgressBarUI BasicRadioButtonMenuItemUI BasicRadioButtonUI BasicRootPaneUI BasicScrollBarUI BasicScrollPaneUI BasicSeparatorUI BasicSliderUI BasicSpinnerUI BasicSplitPaneDivider BasicSplitPaneUI BasicStroke BasicTabbedPaneUI BasicTableHeaderUI BasicTableUI BasicTextAreaUI BasicTextFieldUI BasicTextPaneUI BasicTextUI BasicTextUI.BasicCaret BasicTextUI.BasicHighlighter BasicToggleButtonUI BasicToolBarSeparatorUI BasicToolBarUI BasicToolTipUI BasicTreeUI BasicViewportUI BatchUpdateException BeanContext BeanContextChild BeanContextChildComponentProxy BeanContextChildSupport BeanContextContainerProxy BeanContextEvent BeanContextMembershipEvent BeanContextMembershipListener BeanContextProxy BeanContextServiceAvailableEvent BeanContextServiceProvider BeanContextServiceProviderBeanInfo BeanContextServiceRevokedEvent BeanContextServiceRevokedListener BeanContextServices BeanContextServicesListener BeanContextServicesSupport BeanContextServicesSupport.BCSSServiceProvider BeanContextSupport BeanContextSupport.BCSIterator BeanDescriptor BeanInfo Beans BevelBorder Bidi BigDecimal BigInteger BinaryRefAddr Binder BindException Binding Binding Binding BindingHelper BindingHolder BindingIterator BindingIteratorHelper BindingIteratorHolder BindingIteratorOperations BindingIteratorPOA BindingListHelper BindingListHolder BindingProvider Bindings BindingType BindingType BindingTypeHelper BindingTypeHolder BitSet Blob BlockingDeque BlockingQueue BlockView BMPImageWriteParam Book Boolean BooleanControl BooleanControl.Type BooleanHolder BooleanSeqHelper BooleanSeqHolder Border BorderFactory BorderLayout BorderUIResource BorderUIResource.BevelBorderUIResource BorderUIResource.CompoundBorderUIResource BorderUIResource.EmptyBorderUIResource BorderUIResource.EtchedBorderUIResource BorderUIResource.LineBorderUIResource BorderUIResource.MatteBorderUIResource BorderUIResource.TitledBorderUIResource BoundedRangeModel Bounds Bounds Box Box.Filler BoxedValueHelper BoxLayout BoxView BreakIterator BreakIteratorProvider BrokenBarrierException Buffer BufferCapabilities BufferCapabilities.FlipContents BufferedImage BufferedImageFilter BufferedImageOp BufferedInputStream BufferedOutputStream BufferedReader BufferedWriter BufferOverflowException BufferStrategy BufferUnderflowException Button ButtonGroup ButtonModel ButtonUI Byte ByteArrayInputStream ByteArrayOutputStream ByteBuffer ByteChannel ByteHolder ByteLookupTable ByteOrder C14NMethodParameterSpec CachedRowSet CacheRequest CacheResponse Calendar Callable CallableStatement Callback CallbackHandler CancelablePrintJob CancellationException CancelledKeyException CannotProceed CannotProceedException CannotProceedHelper CannotProceedHolder CannotRedoException CannotUndoException CanonicalizationMethod Canvas CardLayout Caret CaretEvent CaretListener CDATASection CellEditor CellEditorListener CellRendererPane Certificate Certificate Certificate Certificate.CertificateRep CertificateEncodingException CertificateEncodingException CertificateException CertificateException CertificateExpiredException CertificateExpiredException CertificateFactory CertificateFactorySpi CertificateNotYetValidException CertificateNotYetValidException CertificateParsingException CertificateParsingException CertPath CertPath.CertPathRep CertPathBuilder CertPathBuilderException CertPathBuilderResult CertPathBuilderSpi CertPathParameters CertPathTrustManagerParameters CertPathValidator CertPathValidatorException CertPathValidatorResult CertPathValidatorSpi CertSelector CertStore CertStoreException CertStoreParameters CertStoreSpi ChangedCharSetException ChangeEvent ChangeListener Channel ChannelBinding Channels Character Character.Subset Character.UnicodeBlock CharacterCodingException CharacterData CharacterIterator Characters CharArrayReader CharArrayWriter CharBuffer CharConversionException CharHolder CharSeqHelper CharSeqHolder CharSequence Charset CharsetDecoder CharsetEncoder CharsetProvider Checkbox CheckboxGroup CheckboxMenuItem CheckedInputStream CheckedOutputStream Checksum Choice ChoiceCallback ChoiceFormat Chromaticity Cipher CipherInputStream CipherOutputStream CipherSpi Class ClassCastException ClassCircularityError ClassDefinition ClassDesc ClassFileTransformer ClassFormatError ClassLoader ClassLoaderRepository ClassLoadingMXBean ClassNotFoundException ClientInfoStatus ClientRequestInfo ClientRequestInfoOperations ClientRequestInterceptor ClientRequestInterceptorOperations Clip Clipboard ClipboardOwner Clob Cloneable CloneNotSupportedException Closeable ClosedByInterruptException ClosedChannelException ClosedSelectorException CMMException Codec CodecFactory CodecFactoryHelper CodecFactoryOperations CodecOperations CoderMalfunctionError CoderResult CODESET_INCOMPATIBLE CodeSets CodeSigner CodeSource CodingErrorAction CollapsedStringAdapter CollationElementIterator CollationKey Collator CollatorProvider Collection CollectionCertStoreParameters Collections Color ColorChooserComponentFactory ColorChooserUI ColorConvertOp ColorModel ColorSelectionModel ColorSpace ColorSupported ColorType ColorUIResource ComboBoxEditor ComboBoxModel ComboBoxUI ComboPopup COMM_FAILURE CommandInfo CommandMap CommandObject Comment Comment CommonDataSource CommunicationException Comparable Comparator Compilable CompilationMXBean CompiledScript Compiler Completion Completions CompletionService CompletionStatus CompletionStatusHelper Component Component.BaselineResizeBehavior ComponentAdapter ComponentColorModel ComponentEvent ComponentIdHelper ComponentInputMap ComponentInputMapUIResource ComponentListener ComponentOrientation ComponentSampleModel ComponentUI ComponentView Composite CompositeContext CompositeData CompositeDataInvocationHandler CompositeDataSupport CompositeDataView CompositeName CompositeType CompositeView CompoundBorder CompoundControl CompoundControl.Type CompoundEdit CompoundName Compression ConcurrentHashMap ConcurrentLinkedQueue ConcurrentMap ConcurrentModificationException ConcurrentNavigableMap ConcurrentSkipListMap ConcurrentSkipListSet Condition Configuration Configuration.Parameters ConfigurationException ConfigurationSpi ConfirmationCallback ConnectException ConnectException ConnectIOException Connection ConnectionEvent ConnectionEventListener ConnectionPendingException ConnectionPoolDataSource Console ConsoleHandler Constructor ConstructorProperties Container ContainerAdapter ContainerEvent ContainerListener ContainerOrderFocusTraversalPolicy ContentHandler ContentHandler ContentHandlerFactory ContentModel Context Context ContextList ContextNotEmptyException ContextualRenderedImageFactory Control Control Control.Type ControlFactory ControllerEventListener ConvolveOp CookieHandler CookieHolder CookieManager CookiePolicy CookieStore Copies CopiesSupported CopyOnWriteArrayList CopyOnWriteArraySet CountDownLatch CounterMonitor CounterMonitorMBean CRC32 CredentialException CredentialExpiredException CredentialNotFoundException CRL CRLException CRLSelector CropImageFilter CSS CSS.Attribute CTX_RESTRICT_SCOPE CubicCurve2D CubicCurve2D.Double CubicCurve2D.Float Currency CurrencyNameProvider Current Current Current CurrentHelper CurrentHelper CurrentHelper CurrentHolder CurrentOperations CurrentOperations CurrentOperations Cursor Customizer CustomMarshal CustomValue CyclicBarrier Data DATA_CONVERSION DatabaseMetaData DataBindingException DataBuffer DataBufferByte DataBufferDouble DataBufferFloat DataBufferInt DataBufferShort DataBufferUShort DataContentHandler DataContentHandlerFactory DataFlavor DataFormatException DatagramChannel DatagramPacket DatagramSocket DatagramSocketImpl DatagramSocketImplFactory DataHandler DataInput DataInputStream DataInputStream DataLine DataLine.Info DataOutput DataOutputStream DataOutputStream DataSource DataSource DataTruncation DatatypeConfigurationException DatatypeConstants DatatypeConstants.Field DatatypeConverter DatatypeConverterInterface DatatypeFactory Date Date DateFormat DateFormat.Field DateFormatProvider DateFormatSymbols DateFormatSymbolsProvider DateFormatter DateTimeAtCompleted DateTimeAtCreation DateTimeAtProcessing DateTimeSyntax DebugGraphics DecimalFormat DecimalFormatSymbols DecimalFormatSymbolsProvider DeclaredType DeclHandler DefaultBoundedRangeModel DefaultButtonModel DefaultCaret DefaultCellEditor DefaultColorSelectionModel DefaultComboBoxModel DefaultDesktopManager DefaultEditorKit DefaultEditorKit.BeepAction DefaultEditorKit.CopyAction DefaultEditorKit.CutAction DefaultEditorKit.DefaultKeyTypedAction DefaultEditorKit.InsertBreakAction DefaultEditorKit.InsertContentAction DefaultEditorKit.InsertTabAction DefaultEditorKit.PasteAction DefaultFocusManager DefaultFocusTraversalPolicy DefaultFormatter DefaultFormatterFactory DefaultHandler DefaultHandler2 DefaultHighlighter DefaultHighlighter.DefaultHighlightPainter DefaultKeyboardFocusManager DefaultListCellRenderer DefaultListCellRenderer.UIResource DefaultListModel DefaultListSelectionModel DefaultLoaderRepository DefaultLoaderRepository DefaultMenuLayout DefaultMetalTheme DefaultMutableTreeNode DefaultPersistenceDelegate DefaultRowSorter DefaultRowSorter.ModelWrapper DefaultSingleSelectionModel DefaultStyledDocument DefaultStyledDocument.AttributeUndoableEdit DefaultStyledDocument.ElementSpec DefaultTableCellRenderer DefaultTableCellRenderer.UIResource DefaultTableColumnModel DefaultTableModel DefaultTextUI DefaultTreeCellEditor DefaultTreeCellRenderer DefaultTreeModel DefaultTreeSelectionModel DefaultValidationEventHandler DefinitionKind DefinitionKindHelper Deflater DeflaterInputStream DeflaterOutputStream Delayed DelayQueue Delegate Delegate Delegate DelegationPermission Deprecated Deque Descriptor DescriptorAccess DescriptorKey DescriptorRead DescriptorSupport DESedeKeySpec DesignMode DESKeySpec Desktop Desktop.Action DesktopIconUI DesktopManager DesktopPaneUI Destination Destroyable DestroyFailedException Detail DetailEntry DGC DHGenParameterSpec DHKey DHParameterSpec DHPrivateKey DHPrivateKeySpec DHPublicKey DHPublicKeySpec Diagnostic Diagnostic.Kind DiagnosticCollector DiagnosticListener Dialog Dialog.ModalExclusionType Dialog.ModalityType Dictionary DigestException DigestInputStream DigestMethod DigestMethodParameterSpec DigestOutputStream Dimension Dimension2D DimensionUIResource DirContext DirectColorModel DirectoryManager DirObjectFactory DirStateFactory DirStateFactory.Result DISCARDING Dispatch DisplayMode DnDConstants Doc DocAttribute DocAttributeSet DocFlavor DocFlavor.BYTE_ARRAY DocFlavor.CHAR_ARRAY DocFlavor.INPUT_STREAM DocFlavor.READER DocFlavor.SERVICE_FORMATTED DocFlavor.STRING DocFlavor.URL DocPrintJob Document Document DocumentBuilder DocumentBuilderFactory Documented DocumentEvent DocumentEvent DocumentEvent.ElementChange DocumentEvent.EventType DocumentFilter DocumentFilter.FilterBypass DocumentFragment DocumentHandler DocumentListener DocumentName DocumentParser DocumentType DomainCombiner DomainManager DomainManagerOperations DOMConfiguration DOMCryptoContext DOMError DOMErrorHandler DOMException DomHandler DOMImplementation DOMImplementationList DOMImplementationLS DOMImplementationRegistry DOMImplementationSource DOMLocator DOMLocator DOMResult DOMSignContext DOMSource DOMStringList DOMStructure DOMURIReference DOMValidateContext Double DoubleBuffer DoubleHolder DoubleSeqHelper DoubleSeqHolder DragGestureEvent DragGestureListener DragGestureRecognizer DragSource DragSourceAdapter DragSourceContext DragSourceDragEvent DragSourceDropEvent DragSourceEvent DragSourceListener DragSourceMotionListener Driver DriverManager DriverPropertyInfo DropMode DropTarget DropTarget.DropTargetAutoScroller DropTargetAdapter DropTargetContext DropTargetDragEvent DropTargetDropEvent DropTargetEvent DropTargetListener DSAKey DSAKeyPairGenerator DSAParameterSpec DSAParams DSAPrivateKey DSAPrivateKeySpec DSAPublicKey DSAPublicKeySpec DTD DTD DTDConstants DTDHandler DuplicateFormatFlagsException DuplicateName DuplicateNameHelper Duration DynamicImplementation DynamicImplementation DynamicMBean DynAny DynAny DynAnyFactory DynAnyFactoryHelper DynAnyFactoryOperations DynAnyHelper DynAnyOperations DynAnySeqHelper DynArray DynArray DynArrayHelper DynArrayOperations DynEnum DynEnum DynEnumHelper DynEnumOperations DynFixed DynFixed DynFixedHelper DynFixedOperations DynSequence DynSequence DynSequenceHelper DynSequenceOperations DynStruct DynStruct DynStructHelper DynStructOperations DynUnion DynUnion DynUnionHelper DynUnionOperations DynValue DynValue DynValueBox DynValueBoxOperations DynValueCommon DynValueCommonOperations DynValueHelper DynValueOperations ECField ECFieldF2m ECFieldFp ECGenParameterSpec ECKey ECParameterSpec ECPoint ECPrivateKey ECPrivateKeySpec ECPublicKey ECPublicKeySpec EditorKit Element Element Element Element Element ElementFilter ElementIterator ElementKind ElementKindVisitor6 Elements ElementScanner6 ElementType ElementVisitor Ellipse2D Ellipse2D.Double Ellipse2D.Float EllipticCurve EmptyBorder EmptyStackException EncodedKeySpec Encoder Encoding ENCODING_CDR_ENCAPS EncryptedPrivateKeyInfo EndDocument EndElement Endpoint EndpointReference Entity Entity EntityDeclaration EntityReference EntityReference EntityResolver EntityResolver2 Enum EnumConstantNotPresentException EnumControl EnumControl.Type Enumeration EnumMap EnumSet EnumSyntax Environment EOFException Error ErrorHandler ErrorListener ErrorManager ErrorType EtchedBorder Event Event EventContext EventDirContext EventException EventFilter EventHandler EventListener EventListener EventListenerList EventListenerProxy EventObject EventQueue EventReaderDelegate EventSetDescriptor EventTarget ExcC14NParameterSpec Exception ExceptionDetailMessage ExceptionInInitializerError ExceptionList ExceptionListener Exchanger ExecutableElement ExecutableType ExecutionException Executor ExecutorCompletionService Executors ExecutorService ExemptionMechanism ExemptionMechanismException ExemptionMechanismSpi ExpandVetoException ExportException Expression ExtendedRequest ExtendedResponse Externalizable FactoryConfigurationError FactoryConfigurationError FailedLoginException FaultAction FeatureDescriptor Fidelity Field FieldNameHelper FieldNameHelper FieldPosition FieldView File FileCacheImageInputStream FileCacheImageOutputStream FileChannel FileChannel.MapMode FileChooserUI FileDataSource FileDescriptor FileDialog FileFilter FileFilter FileHandler FileImageInputStream FileImageOutputStream FileInputStream FileLock FileLockInterruptionException FileNameExtensionFilter FilenameFilter FileNameMap FileNotFoundException FileObject FileOutputStream FilePermission Filer FileReader FilerException FileSystemView FileTypeMap FileView FileWriter Filter FilteredImageSource FilteredRowSet FilterInputStream FilterOutputStream FilterReader FilterWriter Finishings FixedHeightLayoutCache FixedHolder FlatteningPathIterator FlavorEvent FlavorException FlavorListener FlavorMap FlavorTable Float FloatBuffer FloatControl FloatControl.Type FloatHolder FloatSeqHelper FloatSeqHolder FlowLayout FlowView FlowView.FlowStrategy Flushable FocusAdapter FocusEvent FocusListener FocusManager FocusTraversalPolicy Font FontFormatException FontMetrics FontRenderContext FontUIResource Format Format.Field FormatConversionProvider FormatFlagsConversionMismatchException FormatMismatch FormatMismatchHelper Formattable FormattableFlags Formatter Formatter Formatter.BigDecimalLayoutForm FormatterClosedException FormSubmitEvent FormSubmitEvent.MethodType FormView ForwardingFileObject ForwardingJavaFileManager ForwardingJavaFileObject ForwardRequest ForwardRequest ForwardRequestHelper ForwardRequestHelper Frame FREE_MEM Future FutureTask GapContent GarbageCollectorMXBean GatheringByteChannel GaugeMonitor GaugeMonitorMBean GeneralPath GeneralSecurityException Generated GenericArrayType GenericDeclaration GenericSignatureFormatError GlyphJustificationInfo GlyphMetrics GlyphVector GlyphView GlyphView.GlyphPainter GradientPaint GraphicAttribute Graphics Graphics2D GraphicsConfigTemplate GraphicsConfiguration GraphicsDevice GraphicsEnvironment GrayFilter GregorianCalendar GridBagConstraints GridBagLayout GridBagLayoutInfo GridLayout Group GroupLayout GroupLayout.Alignment GSSContext GSSCredential GSSException GSSManager GSSName Guard GuardedObject GZIPInputStream GZIPOutputStream Handler Handler HandlerBase HandlerChain HandlerResolver HandshakeCompletedEvent HandshakeCompletedListener HasControls HashAttributeSet HashDocAttributeSet HashMap HashPrintJobAttributeSet HashPrintRequestAttributeSet HashPrintServiceAttributeSet HashSet Hashtable HeadlessException HexBinaryAdapter HierarchyBoundsAdapter HierarchyBoundsListener HierarchyEvent HierarchyListener Highlighter Highlighter.Highlight Highlighter.HighlightPainter HMACParameterSpec Holder HOLDING HostnameVerifier HTML HTML.Attribute HTML.Tag HTML.UnknownTag HTMLDocument HTMLDocument.Iterator HTMLEditorKit HTMLEditorKit.HTMLFactory HTMLEditorKit.HTMLTextAction HTMLEditorKit.InsertHTMLTextAction HTMLEditorKit.LinkController HTMLEditorKit.Parser HTMLEditorKit.ParserCallback HTMLFrameHyperlinkEvent HTMLWriter HTTPBinding HttpCookie HTTPException HttpRetryException HttpsURLConnection HttpURLConnection HyperlinkEvent HyperlinkEvent.EventType HyperlinkListener ICC_ColorSpace ICC_Profile ICC_ProfileGray ICC_ProfileRGB Icon IconUIResource IconView ID_ASSIGNMENT_POLICY_ID ID_UNIQUENESS_POLICY_ID IdAssignmentPolicy IdAssignmentPolicyOperations IdAssignmentPolicyValue IdentifierHelper Identity IdentityHashMap IdentityScope IDLEntity IDLType IDLTypeHelper IDLTypeOperations IDN IdUniquenessPolicy IdUniquenessPolicyOperations IdUniquenessPolicyValue IIOByteBuffer IIOException IIOImage IIOInvalidTreeException IIOMetadata IIOMetadataController IIOMetadataFormat IIOMetadataFormatImpl IIOMetadataNode IIOParam IIOParamController IIOReadProgressListener IIOReadUpdateListener IIOReadWarningListener IIORegistry IIOServiceProvider IIOWriteProgressListener IIOWriteWarningListener IllegalAccessError IllegalAccessException IllegalArgumentException IllegalBlockingModeException IllegalBlockSizeException IllegalCharsetNameException IllegalClassFormatException IllegalComponentStateException IllegalFormatCodePointException IllegalFormatConversionException IllegalFormatException IllegalFormatFlagsException IllegalFormatPrecisionException IllegalFormatWidthException IllegalMonitorStateException IllegalPathStateException IllegalSelectorException IllegalStateException IllegalThreadStateException Image ImageCapabilities ImageConsumer ImageFilter ImageGraphicAttribute ImageIcon ImageInputStream ImageInputStreamImpl ImageInputStreamSpi ImageIO ImageObserver ImageOutputStream ImageOutputStreamImpl ImageOutputStreamSpi ImageProducer ImageReader ImageReaderSpi ImageReaderWriterSpi ImageReadParam ImageTranscoder ImageTranscoderSpi ImageTypeSpecifier ImageView ImageWriteParam ImageWriter ImageWriterSpi ImagingOpException ImmutableDescriptor IMP_LIMIT IMPLICIT_ACTIVATION_POLICY_ID ImplicitActivationPolicy ImplicitActivationPolicyOperations ImplicitActivationPolicyValue INACTIVE IncompatibleClassChangeError IncompleteAnnotationException InconsistentTypeCode InconsistentTypeCode InconsistentTypeCodeHelper IndexColorModel IndexedPropertyChangeEvent IndexedPropertyDescriptor IndexOutOfBoundsException IndirectionException Inet4Address Inet6Address InetAddress InetSocketAddress Inflater InflaterInputStream InflaterOutputStream InheritableThreadLocal Inherited InitialContext InitialContextFactory InitialContextFactoryBuilder InitialDirContext INITIALIZE InitialLdapContext InitParam InlineView InputContext InputEvent InputMap InputMapUIResource InputMethod InputMethodContext InputMethodDescriptor InputMethodEvent InputMethodHighlight InputMethodListener InputMethodRequests InputMismatchException InputSource InputStream InputStream InputStream InputStreamReader InputSubset InputVerifier Insets InsetsUIResource InstanceAlreadyExistsException InstanceNotFoundException InstantiationError InstantiationException Instrument Instrumentation InsufficientResourcesException IntBuffer Integer IntegerSyntax Interceptor InterceptorOperations InterfaceAddress INTERNAL InternalError InternalFrameAdapter InternalFrameEvent InternalFrameFocusTraversalPolicy InternalFrameListener InternalFrameUI InternationalFormatter InterruptedException InterruptedIOException InterruptedNamingException InterruptibleChannel INTF_REPOS IntHolder IntrospectionException IntrospectionException Introspector INV_FLAG INV_IDENT INV_OBJREF INV_POLICY Invalid INVALID_ACTIVITY INVALID_TRANSACTION InvalidActivityException InvalidAddress InvalidAddressHelper InvalidAddressHolder InvalidAlgorithmParameterException InvalidApplicationException InvalidAttributeIdentifierException InvalidAttributesException InvalidAttributeValueException InvalidAttributeValueException InvalidClassException InvalidDnDOperationException InvalidKeyException InvalidKeyException InvalidKeySpecException InvalidMarkException InvalidMidiDataException InvalidName InvalidName InvalidName InvalidNameException InvalidNameHelper InvalidNameHelper InvalidNameHolder InvalidObjectException InvalidOpenTypeException InvalidParameterException InvalidParameterSpecException InvalidPolicy InvalidPolicyHelper InvalidPreferencesFormatException InvalidPropertiesFormatException InvalidRelationIdException InvalidRelationServiceException InvalidRelationTypeException InvalidRoleInfoException InvalidRoleValueException InvalidSearchControlsException InvalidSearchFilterException InvalidSeq InvalidSlot InvalidSlotHelper InvalidTargetObjectTypeException InvalidTransactionException InvalidTypeForEncoding InvalidTypeForEncodingHelper InvalidValue InvalidValue InvalidValueHelper Invocable InvocationEvent InvocationHandler InvocationTargetException InvokeHandler IOError IOException IOR IORHelper IORHolder IORInfo IORInfoOperations IORInterceptor IORInterceptor_3_0 IORInterceptor_3_0Helper IORInterceptor_3_0Holder IORInterceptor_3_0Operations IORInterceptorOperations IRObject IRObjectOperations IstringHelper ItemEvent ItemListener ItemSelectable Iterable Iterator IvParameterSpec JApplet JarEntry JarException JarFile JarInputStream JarOutputStream JarURLConnection JavaCompiler JavaCompiler.CompilationTask JavaFileManager JavaFileManager.Location JavaFileObject JavaFileObject.Kind JAXB JAXBContext JAXBElement JAXBElement.GlobalScope JAXBException JAXBIntrospector JAXBResult JAXBSource JButton JCheckBox JCheckBoxMenuItem JColorChooser JComboBox JComboBox.KeySelectionManager JComponent JdbcRowSet JDesktopPane JDialog JEditorPane JFileChooser JFormattedTextField JFormattedTextField.AbstractFormatter JFormattedTextField.AbstractFormatterFactory JFrame JInternalFrame JInternalFrame.JDesktopIcon JLabel JLayeredPane JList JList.DropLocation JMenu JMenuBar JMenuItem JMException JMRuntimeException JMX JMXAddressable JMXAuthenticator JMXConnectionNotification JMXConnector JMXConnectorFactory JMXConnectorProvider JMXConnectorServer JMXConnectorServerFactory JMXConnectorServerMBean JMXConnectorServerProvider JMXPrincipal JMXProviderException JMXServerErrorException JMXServiceURL JobAttributes JobAttributes.DefaultSelectionType JobAttributes.DestinationType JobAttributes.DialogType JobAttributes.MultipleDocumentHandlingType JobAttributes.SidesType JobHoldUntil JobImpressions JobImpressionsCompleted JobImpressionsSupported JobKOctets JobKOctetsProcessed JobKOctetsSupported JobMediaSheets JobMediaSheetsCompleted JobMediaSheetsSupported JobMessageFromOperator JobName JobOriginatingUserName JobPriority JobPrioritySupported JobSheets JobState JobStateReason JobStateReasons Joinable JoinRowSet JOptionPane JPanel JPasswordField JPEGHuffmanTable JPEGImageReadParam JPEGImageWriteParam JPEGQTable JPopupMenu JPopupMenu.Separator JProgressBar JRadioButton JRadioButtonMenuItem JRootPane JScrollBar JScrollPane JSeparator JSlider JSpinner JSpinner.DateEditor JSpinner.DefaultEditor JSpinner.ListEditor JSpinner.NumberEditor JSplitPane JTabbedPane JTable JTable.DropLocation JTable.PrintMode JTableHeader JTextArea JTextComponent JTextComponent.DropLocation JTextComponent.KeyBinding JTextField JTextPane JToggleButton JToggleButton.ToggleButtonModel JToolBar JToolBar.Separator JToolTip JTree JTree.DropLocation JTree.DynamicUtilTreeNode JTree.EmptySelectionModel JViewport JWindow KerberosKey KerberosPrincipal KerberosTicket Kernel Key KeyAdapter KeyAgreement KeyAgreementSpi KeyAlreadyExistsException KeyboardFocusManager KeyEvent KeyEventDispatcher KeyEventPostProcessor KeyException KeyFactory KeyFactorySpi KeyGenerator KeyGeneratorSpi KeyInfo KeyInfoFactory KeyListener KeyManagementException KeyManager KeyManagerFactory KeyManagerFactorySpi Keymap KeyName KeyPair KeyPairGenerator KeyPairGeneratorSpi KeyRep KeyRep.Type KeySelector KeySelector.Purpose KeySelectorException KeySelectorResult KeySpec KeyStore KeyStore.Builder KeyStore.CallbackHandlerProtection KeyStore.Entry KeyStore.LoadStoreParameter KeyStore.PasswordProtection KeyStore.PrivateKeyEntry KeyStore.ProtectionParameter KeyStore.SecretKeyEntry KeyStore.TrustedCertificateEntry KeyStoreBuilderParameters KeyStoreException KeyStoreSpi KeyStroke KeyValue Label LabelUI LabelView LanguageCallback LastOwnerException LayeredHighlighter LayeredHighlighter.LayerPainter LayoutFocusTraversalPolicy LayoutManager LayoutManager2 LayoutPath LayoutQueue LayoutStyle LayoutStyle.ComponentPlacement LDAPCertStoreParameters LdapContext LdapName LdapReferralException Lease Level LexicalHandler LIFESPAN_POLICY_ID LifespanPolicy LifespanPolicyOperations LifespanPolicyValue LimitExceededException Line Line.Info Line2D Line2D.Double Line2D.Float LinearGradientPaint LineBorder LineBreakMeasurer LineEvent LineEvent.Type LineListener LineMetrics LineNumberInputStream LineNumberReader LineUnavailableException LinkageError LinkedBlockingDeque LinkedBlockingQueue LinkedHashMap LinkedHashSet LinkedList LinkException LinkLoopException LinkRef List List ListCellRenderer ListDataEvent ListDataListener ListenerNotFoundException ListIterator ListModel ListResourceBundle ListSelectionEvent ListSelectionListener ListSelectionModel ListUI ListView LoaderHandler Locale LocaleNameProvider LocaleServiceProvider LocalObject LocateRegistry Location LOCATION_FORWARD Locator Locator2 Locator2Impl LocatorImpl Lock LockInfo LockSupport Logger LoggingMXBean LoggingPermission LogicalHandler LogicalMessage LogicalMessageContext LoginContext LoginException LoginModule LogManager LogRecord LogStream Long LongBuffer LongHolder LongLongSeqHelper LongLongSeqHolder LongSeqHelper LongSeqHolder LookAndFeel LookupOp LookupTable LSException LSInput LSLoadEvent LSOutput LSParser LSParserFilter LSProgressEvent LSResourceResolver LSSerializer LSSerializerFilter Mac MacSpi MailcapCommandMap MalformedInputException MalformedLinkException MalformedObjectNameException MalformedParameterizedTypeException MalformedURLException ManagementFactory ManagementPermission ManageReferralControl ManagerFactoryParameters Manifest Manifest Map Map.Entry MappedByteBuffer MARSHAL MarshalException MarshalException MarshalException MarshalledObject Marshaller Marshaller.Listener MaskFormatter Matcher MatchResult Math MathContext MatteBorder MBeanAttributeInfo MBeanConstructorInfo MBeanException MBeanFeatureInfo MBeanInfo MBeanNotificationInfo MBeanOperationInfo MBeanParameterInfo MBeanPermission MBeanRegistration MBeanRegistrationException MBeanServer MBeanServerBuilder MBeanServerConnection MBeanServerDelegate MBeanServerDelegateMBean MBeanServerFactory MBeanServerForwarder MBeanServerInvocationHandler MBeanServerNotification MBeanServerNotificationFilter MBeanServerPermission MBeanTrustPermission Media MediaName MediaPrintableArea MediaSize MediaSize.Engineering MediaSize.ISO MediaSize.JIS MediaSize.NA MediaSize.Other MediaSizeName MediaTracker MediaTray Member MemoryCacheImageInputStream MemoryCacheImageOutputStream MemoryHandler MemoryImageSource MemoryManagerMXBean MemoryMXBean MemoryNotificationInfo MemoryPoolMXBean MemoryType MemoryUsage Menu MenuBar MenuBarUI MenuComponent MenuContainer MenuDragMouseEvent MenuDragMouseListener MenuElement MenuEvent MenuItem MenuItemUI MenuKeyEvent MenuKeyListener MenuListener MenuSelectionManager MenuShortcut MessageContext MessageContext.Scope MessageDigest MessageDigestSpi MessageFactory MessageFormat MessageFormat.Field MessageProp Messager MetaEventListener MetalBorders MetalBorders.ButtonBorder MetalBorders.Flush3DBorder MetalBorders.InternalFrameBorder MetalBorders.MenuBarBorder MetalBorders.MenuItemBorder MetalBorders.OptionDialogBorder MetalBorders.PaletteBorder MetalBorders.PopupMenuBorder MetalBorders.RolloverButtonBorder MetalBorders.ScrollPaneBorder MetalBorders.TableHeaderBorder MetalBorders.TextFieldBorder MetalBorders.ToggleButtonBorder MetalBorders.ToolBarBorder MetalButtonUI MetalCheckBoxIcon MetalCheckBoxUI MetalComboBoxButton MetalComboBoxEditor MetalComboBoxEditor.UIResource MetalComboBoxIcon MetalComboBoxUI MetalDesktopIconUI MetalFileChooserUI MetalIconFactory MetalIconFactory.FileIcon16 MetalIconFactory.FolderIcon16 MetalIconFactory.PaletteCloseIcon MetalIconFactory.TreeControlIcon MetalIconFactory.TreeFolderIcon MetalIconFactory.TreeLeafIcon MetalInternalFrameTitlePane MetalInternalFrameUI MetalLabelUI MetalLookAndFeel MetalMenuBarUI MetalPopupMenuSeparatorUI MetalProgressBarUI MetalRadioButtonUI MetalRootPaneUI MetalScrollBarUI MetalScrollButton MetalScrollPaneUI MetalSeparatorUI MetalSliderUI MetalSplitPaneUI MetalTabbedPaneUI MetalTextFieldUI MetalTheme MetalToggleButtonUI MetalToolBarUI MetalToolTipUI MetalTreeUI MetaMessage Method MethodDescriptor MGF1ParameterSpec MidiChannel MidiDevice MidiDevice.Info MidiDeviceProvider MidiEvent MidiFileFormat MidiFileReader MidiFileWriter MidiMessage MidiSystem MidiUnavailableException MimeHeader MimeHeaders MimeType MimeTypeParameterList MimeTypeParseException MimeTypeParseException MimetypesFileTypeMap MinimalHTMLWriter MirroredTypeException MirroredTypesException MissingFormatArgumentException MissingFormatWidthException MissingResourceException Mixer Mixer.Info MixerProvider MLet MLetContent MLetMBean ModelMBean ModelMBeanAttributeInfo ModelMBeanConstructorInfo ModelMBeanInfo ModelMBeanInfoSupport ModelMBeanNotificationBroadcaster ModelMBeanNotificationInfo ModelMBeanOperationInfo ModificationItem Modifier Modifier Monitor MonitorInfo MonitorMBean MonitorNotification MonitorSettingException MouseAdapter MouseDragGestureRecognizer MouseEvent MouseEvent MouseInfo MouseInputAdapter MouseInputListener MouseListener MouseMotionAdapter MouseMotionListener MouseWheelEvent MouseWheelListener MTOM MTOMFeature MultiButtonUI MulticastSocket MultiColorChooserUI MultiComboBoxUI MultiDesktopIconUI MultiDesktopPaneUI MultiDoc MultiDocPrintJob MultiDocPrintService MultiFileChooserUI MultiInternalFrameUI MultiLabelUI MultiListUI MultiLookAndFeel MultiMenuBarUI MultiMenuItemUI MultiOptionPaneUI MultiPanelUI MultiPixelPackedSampleModel MultipleComponentProfileHelper MultipleComponentProfileHolder MultipleDocumentHandling MultipleGradientPaint MultipleGradientPaint.ColorSpaceType MultipleGradientPaint.CycleMethod MultipleMaster MultiPopupMenuUI MultiProgressBarUI MultiRootPaneUI MultiScrollBarUI MultiScrollPaneUI MultiSeparatorUI MultiSliderUI MultiSpinnerUI MultiSplitPaneUI MultiTabbedPaneUI MultiTableHeaderUI MultiTableUI MultiTextUI MultiToolBarUI MultiToolTipUI MultiTreeUI MultiViewportUI MutableAttributeSet MutableComboBoxModel MutableTreeNode MutationEvent MXBean Name Name Name NameAlreadyBoundException NameCallback NameClassPair NameComponent NameComponentHelper NameComponentHolder NamedNodeMap NamedValue NameDynAnyPair NameDynAnyPairHelper NameDynAnyPairSeqHelper NameHelper NameHolder NameList NameNotFoundException NameParser Namespace NamespaceChangeListener NamespaceContext NamespaceSupport NameValuePair NameValuePair NameValuePairHelper NameValuePairHelper NameValuePairSeqHelper Naming NamingContext NamingContextExt NamingContextExtHelper NamingContextExtHolder NamingContextExtOperations NamingContextExtPOA NamingContextHelper NamingContextHolder NamingContextOperations NamingContextPOA NamingEnumeration NamingEvent NamingException NamingExceptionEvent NamingListener NamingManager NamingSecurityException NavigableMap NavigableSet NavigationFilter NavigationFilter.FilterBypass NClob NegativeArraySizeException NestingKind NetPermission NetworkInterface NO_IMPLEMENT NO_MEMORY NO_PERMISSION NO_RESOURCES NO_RESPONSE NoClassDefFoundError NoConnectionPendingException NoContext NoContextHelper Node Node NodeChangeEvent NodeChangeListener NodeList NodeSetData NoInitialContextException NON_EXISTENT NoninvertibleTransformException NonReadableChannelException NonWritableChannelException NoPermissionException NormalizedStringAdapter Normalizer Normalizer.Form NoRouteToHostException NoServant NoServantHelper NoSuchAlgorithmException NoSuchAttributeException NoSuchElementException NoSuchFieldError NoSuchFieldException NoSuchMechanismException NoSuchMethodError NoSuchMethodException NoSuchObjectException NoSuchPaddingException NoSuchProviderException NotActiveException Notation NotationDeclaration NotBoundException NotCompliantMBeanException NotContextException NotEmpty NotEmptyHelper NotEmptyHolder NotFound NotFoundHelper NotFoundHolder NotFoundReason NotFoundReasonHelper NotFoundReasonHolder NotIdentifiableEvent NotIdentifiableEventImpl Notification NotificationBroadcaster NotificationBroadcasterSupport NotificationEmitter NotificationFilter NotificationFilterSupport NotificationListener NotificationResult NotOwnerException NotSerializableException NotYetBoundException NotYetConnectedException NoType NullCipher NullPointerException NullType Number NumberFormat NumberFormat.Field NumberFormatException NumberFormatProvider NumberFormatter NumberOfDocuments NumberOfInterveningJobs NumberUp NumberUpSupported NumericShaper NVList OAEPParameterSpec OBJ_ADAPTER Object Object OBJECT_NOT_EXIST ObjectAlreadyActive ObjectAlreadyActiveHelper ObjectChangeListener ObjectFactory ObjectFactoryBuilder ObjectHelper ObjectHolder ObjectIdHelper ObjectIdHelper ObjectImpl ObjectImpl ObjectInput ObjectInputStream ObjectInputStream.GetField ObjectInputValidation ObjectInstance ObjectName ObjectNotActive ObjectNotActiveHelper ObjectOutput ObjectOutputStream ObjectOutputStream.PutField ObjectReferenceFactory ObjectReferenceFactoryHelper ObjectReferenceFactoryHolder ObjectReferenceTemplate ObjectReferenceTemplateHelper ObjectReferenceTemplateHolder ObjectReferenceTemplateSeqHelper ObjectReferenceTemplateSeqHolder ObjectStreamClass ObjectStreamConstants ObjectStreamException ObjectStreamField ObjectView ObjID Observable Observer OceanTheme OctetSeqHelper OctetSeqHolder OctetStreamData Oid OMGVMCID Oneway OpenDataException OpenMBeanAttributeInfo OpenMBeanAttributeInfoSupport OpenMBeanConstructorInfo OpenMBeanConstructorInfoSupport OpenMBeanInfo OpenMBeanInfoSupport OpenMBeanOperationInfo OpenMBeanOperationInfoSupport OpenMBeanParameterInfo OpenMBeanParameterInfoSupport OpenType OpenType OperatingSystemMXBean Operation OperationNotSupportedException OperationsException Option OptionalDataException OptionChecker OptionPaneUI ORB ORB ORBIdHelper ORBInitializer ORBInitializerOperations ORBInitInfo ORBInitInfoOperations OrientationRequested OutOfMemoryError OutputDeviceAssigned OutputKeys OutputStream OutputStream OutputStream OutputStreamWriter OverlappingFileLockException OverlayLayout Override Owner Pack200 Pack200.Packer Pack200.Unpacker Package PackageElement PackedColorModel Pageable PageAttributes PageAttributes.ColorType PageAttributes.MediaType PageAttributes.OrientationRequestedType PageAttributes.OriginType PageAttributes.PrintQualityType PagedResultsControl PagedResultsResponseControl PageFormat PageRanges PagesPerMinute PagesPerMinuteColor Paint PaintContext PaintEvent Panel PanelUI Paper ParagraphView ParagraphView Parameter ParameterBlock ParameterDescriptor ParameterizedType ParameterMetaData ParameterMode ParameterModeHelper ParameterModeHolder ParseConversionEvent ParseConversionEventImpl ParseException ParsePosition Parser Parser ParserAdapter ParserConfigurationException ParserDelegator ParserFactory PartialResultException PasswordAuthentication PasswordCallback PasswordView Patch Path2D Path2D.Double Path2D.Float PathIterator Pattern PatternSyntaxException PBEKey PBEKeySpec PBEParameterSpec PDLOverrideSupported Permission Permission PermissionCollection Permissions PERSIST_STORE PersistenceDelegate PersistentMBean PGPData PhantomReference Pipe Pipe.SinkChannel Pipe.SourceChannel PipedInputStream PipedOutputStream PipedReader PipedWriter PixelGrabber PixelInterleavedSampleModel PKCS8EncodedKeySpec PKIXBuilderParameters PKIXCertPathBuilderResult PKIXCertPathChecker PKIXCertPathValidatorResult PKIXParameters PlainDocument PlainView POA POAHelper POAManager POAManagerOperations POAOperations Point Point2D Point2D.Double Point2D.Float PointerInfo Policy Policy Policy Policy.Parameters PolicyError PolicyErrorCodeHelper PolicyErrorHelper PolicyErrorHolder PolicyFactory PolicyFactoryOperations PolicyHelper PolicyHolder PolicyListHelper PolicyListHolder PolicyNode PolicyOperations PolicyQualifierInfo PolicySpi PolicyTypeHelper Polygon PooledConnection Popup PopupFactory PopupMenu PopupMenuEvent PopupMenuListener PopupMenuUI Port Port.Info PortableRemoteObject PortableRemoteObjectDelegate PortInfo PortUnreachableException Position Position.Bias PostConstruct PreDestroy Predicate PreferenceChangeEvent PreferenceChangeListener Preferences PreferencesFactory PreparedStatement PresentationDirection PrimitiveType Principal Principal PrincipalHolder Printable PrintConversionEvent PrintConversionEventImpl PrinterAbortException PrinterException PrinterGraphics PrinterInfo PrinterIOException PrinterIsAcceptingJobs PrinterJob PrinterLocation PrinterMakeAndModel PrinterMessageFromOperator PrinterMoreInfo PrinterMoreInfoManufacturer PrinterName PrinterResolution PrinterState PrinterStateReason PrinterStateReasons PrinterURI PrintEvent PrintException PrintGraphics PrintJob PrintJobAdapter PrintJobAttribute PrintJobAttributeEvent PrintJobAttributeListener PrintJobAttributeSet PrintJobEvent PrintJobListener PrintQuality PrintRequestAttribute PrintRequestAttributeSet PrintService PrintServiceAttribute PrintServiceAttributeEvent PrintServiceAttributeListener PrintServiceAttributeSet PrintServiceLookup PrintStream PrintWriter PriorityBlockingQueue PriorityQueue PRIVATE_MEMBER PrivateClassLoader PrivateCredentialPermission PrivateKey PrivateMLet PrivilegedAction PrivilegedActionException PrivilegedExceptionAction Process ProcessBuilder ProcessingEnvironment ProcessingInstruction ProcessingInstruction Processor ProfileDataException ProfileIdHelper ProgressBarUI ProgressMonitor ProgressMonitorInputStream Properties PropertyChangeEvent PropertyChangeListener PropertyChangeListenerProxy PropertyChangeSupport PropertyDescriptor PropertyEditor PropertyEditorManager PropertyEditorSupport PropertyException PropertyPermission PropertyResourceBundle PropertyVetoException ProtectionDomain ProtocolException ProtocolException Provider Provider Provider Provider.Service ProviderException Proxy Proxy Proxy.Type ProxySelector PSource PSource.PSpecified PSSParameterSpec PUBLIC_MEMBER PublicKey PushbackInputStream PushbackReader QName QuadCurve2D QuadCurve2D.Double QuadCurve2D.Float Query QueryEval QueryExp Queue QueuedJobCount RadialGradientPaint Random RandomAccess RandomAccessFile Raster RasterFormatException RasterOp RC2ParameterSpec RC5ParameterSpec Rdn Readable ReadableByteChannel Reader ReadOnlyBufferException ReadWriteLock RealmCallback RealmChoiceCallback REBIND Receiver Rectangle Rectangle2D Rectangle2D.Double Rectangle2D.Float RectangularShape ReentrantLock ReentrantReadWriteLock ReentrantReadWriteLock.ReadLock ReentrantReadWriteLock.WriteLock Ref RefAddr Reference Reference Reference Referenceable ReferenceQueue ReferenceType ReferenceUriSchemesSupported ReferralException ReflectionException ReflectPermission Refreshable RefreshFailedException Region RegisterableService Registry RegistryHandler RejectedExecutionException RejectedExecutionHandler Relation RelationException RelationNotFoundException RelationNotification RelationService RelationServiceMBean RelationServiceNotRegisteredException RelationSupport RelationSupportMBean RelationType RelationTypeNotFoundException RelationTypeSupport RemarshalException Remote RemoteCall RemoteException RemoteObject RemoteObjectInvocationHandler RemoteRef RemoteServer RemoteStub RenderableImage RenderableImageOp RenderableImageProducer RenderContext RenderedImage RenderedImageFactory Renderer RenderingHints RenderingHints.Key RepaintManager ReplicateScaleFilter RepositoryIdHelper Request REQUEST_PROCESSING_POLICY_ID RequestInfo RequestInfoOperations RequestingUserName RequestProcessingPolicy RequestProcessingPolicyOperations RequestProcessingPolicyValue RequestWrapper RequiredModelMBean RescaleOp ResolutionSyntax Resolver ResolveResult Resource Resource.AuthenticationType ResourceBundle ResourceBundle.Control Resources RespectBinding RespectBindingFeature Response ResponseCache ResponseHandler ResponseWrapper Result ResultSet ResultSetMetaData Retention RetentionPolicy RetrievalMethod ReverbType RGBImageFilter RMIClassLoader RMIClassLoaderSpi RMIClientSocketFactory RMIConnection RMIConnectionImpl RMIConnectionImpl_Stub RMIConnector RMIConnectorServer RMICustomMaxStreamFormat RMIFailureHandler RMIIIOPServerImpl RMIJRMPServerImpl RMISecurityException RMISecurityManager RMIServer RMIServerImpl RMIServerImpl_Stub RMIServerSocketFactory RMISocketFactory Robot Role RoleInfo RoleInfoNotFoundException RoleList RoleNotFoundException RoleResult RoleStatus RoleUnresolved RoleUnresolvedList RootPaneContainer RootPaneUI RoundEnvironment RoundingMode RoundRectangle2D RoundRectangle2D.Double RoundRectangle2D.Float RowFilter RowFilter.ComparisonType RowFilter.Entry RowId RowIdLifetime RowMapper RowSet RowSetEvent RowSetInternal RowSetListener RowSetMetaData RowSetMetaDataImpl RowSetReader RowSetWarning RowSetWriter RowSorter RowSorter.SortKey RowSorterEvent RowSorterEvent.Type RowSorterListener RSAKey RSAKeyGenParameterSpec RSAMultiPrimePrivateCrtKey RSAMultiPrimePrivateCrtKeySpec RSAOtherPrimeInfo RSAPrivateCrtKey RSAPrivateCrtKeySpec RSAPrivateKey RSAPrivateKeySpec RSAPublicKey RSAPublicKeySpec RTFEditorKit RuleBasedCollator Runnable RunnableFuture RunnableScheduledFuture Runtime RunTime RuntimeErrorException RuntimeException RuntimeMBeanException RuntimeMXBean RunTimeOperations RuntimeOperationsException RuntimePermission SAAJMetaFactory SAAJResult SampleModel Sasl SaslClient SaslClientFactory SaslException SaslServer SaslServerFactory Savepoint SAXException SAXNotRecognizedException SAXNotSupportedException SAXParseException SAXParser SAXParserFactory SAXResult SAXSource SAXTransformerFactory Scanner ScatteringByteChannel ScheduledExecutorService ScheduledFuture ScheduledThreadPoolExecutor Schema SchemaFactory SchemaFactoryLoader SchemaOutputResolver SchemaViolationException ScriptContext ScriptEngine ScriptEngineFactory ScriptEngineManager ScriptException Scrollable Scrollbar ScrollBarUI ScrollPane ScrollPaneAdjustable ScrollPaneConstants ScrollPaneLayout ScrollPaneLayout.UIResource ScrollPaneUI SealedObject SearchControls SearchResult SecretKey SecretKeyFactory SecretKeyFactorySpi SecretKeySpec SecureCacheResponse SecureClassLoader SecureRandom SecureRandomSpi Security SecurityException SecurityManager SecurityPermission Segment SelectableChannel SelectionKey Selector SelectorProvider Semaphore SeparatorUI Sequence SequenceInputStream Sequencer Sequencer.SyncMode SerialArray SerialBlob SerialClob SerialDatalink SerialException Serializable SerializablePermission SerialJavaObject SerialRef SerialStruct Servant SERVANT_RETENTION_POLICY_ID ServantActivator ServantActivatorHelper ServantActivatorOperations ServantActivatorPOA ServantAlreadyActive ServantAlreadyActiveHelper ServantLocator ServantLocatorHelper ServantLocatorOperations ServantLocatorPOA ServantManager ServantManagerOperations ServantNotActive ServantNotActiveHelper ServantObject ServantRetentionPolicy ServantRetentionPolicyOperations ServantRetentionPolicyValue ServerCloneException ServerError ServerException ServerIdHelper ServerNotActiveException ServerRef ServerRequest ServerRequestInfo ServerRequestInfoOperations ServerRequestInterceptor ServerRequestInterceptorOperations ServerRuntimeException ServerSocket ServerSocketChannel ServerSocketFactory Service Service.Mode ServiceConfigurationError ServiceContext ServiceContextHelper ServiceContextHolder ServiceContextListHelper ServiceContextListHolder ServiceDelegate ServiceDetail ServiceDetailHelper ServiceIdHelper ServiceInformation ServiceInformationHelper ServiceInformationHolder ServiceLoader ServiceMode ServiceNotFoundException ServicePermission ServiceRegistry ServiceRegistry.Filter ServiceUI ServiceUIFactory ServiceUnavailableException Set SetOfIntegerSyntax SetOverrideType SetOverrideTypeHelper Severity Shape ShapeGraphicAttribute SheetCollate Short ShortBuffer ShortBufferException ShortHolder ShortLookupTable ShortMessage ShortSeqHelper ShortSeqHolder Sides Signature SignatureException SignatureMethod SignatureMethodParameterSpec SignatureProperties SignatureProperty SignatureSpi SignedInfo SignedObject Signer SimpleAnnotationValueVisitor6 SimpleAttributeSet SimpleBeanInfo SimpleBindings SimpleDateFormat SimpleDoc SimpleElementVisitor6 SimpleFormatter SimpleJavaFileObject SimpleScriptContext SimpleTimeZone SimpleType SimpleTypeVisitor6 SinglePixelPackedSampleModel SingleSelectionModel Size2DSyntax SizeLimitExceededException SizeRequirements SizeSequence Skeleton SkeletonMismatchException SkeletonNotFoundException SliderUI SOAPBinding SOAPBinding SOAPBinding.ParameterStyle SOAPBinding.Style SOAPBinding.Use SOAPBody SOAPBodyElement SOAPConnection SOAPConnectionFactory SOAPConstants SOAPElement SOAPElementFactory SOAPEnvelope SOAPException SOAPFactory SOAPFault SOAPFaultElement SOAPFaultException SOAPHandler SOAPHeader SOAPHeaderElement SOAPMessage SOAPMessageContext SOAPMessageHandler SOAPMessageHandlers SOAPPart Socket SocketAddress SocketChannel SocketException SocketFactory SocketHandler SocketImpl SocketImplFactory SocketOptions SocketPermission SocketSecurityException SocketTimeoutException SoftBevelBorder SoftReference SortControl SortedMap SortedSet SortingFocusTraversalPolicy SortKey SortOrder SortResponseControl Soundbank SoundbankReader SoundbankResource Source SourceDataLine SourceLocator SourceVersion SpinnerDateModel SpinnerListModel SpinnerModel SpinnerNumberModel SpinnerUI SplashScreen SplitPaneUI Spring SpringLayout SpringLayout.Constraints SQLClientInfoException SQLData SQLDataException SQLException SQLFeatureNotSupportedException SQLInput SQLInputImpl SQLIntegrityConstraintViolationException SQLInvalidAuthorizationSpecException SQLNonTransientConnectionException SQLNonTransientException SQLOutput SQLOutputImpl SQLPermission SQLRecoverableException SQLSyntaxErrorException SQLTimeoutException SQLTransactionRollbackException SQLTransientConnectionException SQLTransientException SQLWarning SQLXML SSLContext SSLContextSpi SSLEngine SSLEngineResult SSLEngineResult.HandshakeStatus SSLEngineResult.Status SSLException SSLHandshakeException SSLKeyException SSLParameters SSLPeerUnverifiedException SSLPermission SSLProtocolException SslRMIClientSocketFactory SslRMIServerSocketFactory SSLServerSocket SSLServerSocketFactory SSLSession SSLSessionBindingEvent SSLSessionBindingListener SSLSessionContext SSLSocket SSLSocketFactory Stack StackOverflowError StackTraceElement StandardEmitterMBean StandardJavaFileManager StandardLocation StandardMBean StartDocument StartElement StartTlsRequest StartTlsResponse State StateEdit StateEditable StateFactory Statement Statement StatementEvent StatementEventListener StAXResult StAXSource Streamable StreamableValue StreamCorruptedException StreamFilter StreamHandler StreamPrintService StreamPrintServiceFactory StreamReaderDelegate StreamResult StreamSource StreamTokenizer StrictMath String StringBuffer StringBufferInputStream StringBuilder StringCharacterIterator StringContent StringHolder StringIndexOutOfBoundsException StringMonitor StringMonitorMBean StringNameHelper StringReader StringRefAddr StringSelection StringSeqHelper StringSeqHolder StringTokenizer StringValueExp StringValueHelper StringWriter Stroke Struct StructMember StructMemberHelper Stub StubDelegate StubNotFoundException Style StyleConstants StyleConstants.CharacterConstants StyleConstants.ColorConstants StyleConstants.FontConstants StyleConstants.ParagraphConstants StyleContext StyledDocument StyledEditorKit StyledEditorKit.AlignmentAction StyledEditorKit.BoldAction StyledEditorKit.FontFamilyAction StyledEditorKit.FontSizeAction StyledEditorKit.ForegroundAction StyledEditorKit.ItalicAction StyledEditorKit.StyledTextAction StyledEditorKit.UnderlineAction StyleSheet StyleSheet.BoxPainter StyleSheet.ListPainter Subject SubjectDelegationPermission SubjectDomainCombiner SUCCESSFUL SupportedAnnotationTypes SupportedOptions SupportedSourceVersion SupportedValuesAttribute SuppressWarnings SwingConstants SwingPropertyChangeSupport SwingUtilities SwingWorker SwingWorker.StateValue SYNC_WITH_TRANSPORT SyncFactory SyncFactoryException SyncFailedException SynchronousQueue SyncProvider SyncProviderException SyncResolver SyncScopeHelper SynthConstants SynthContext Synthesizer SynthGraphicsUtils SynthLookAndFeel SynthPainter SynthStyle SynthStyleFactory SysexMessage System SYSTEM_EXCEPTION SystemColor SystemException SystemFlavorMap SystemTray TabableView TabbedPaneUI TabExpander TableCellEditor TableCellRenderer TableColumn TableColumnModel TableColumnModelEvent TableColumnModelListener TableHeaderUI TableModel TableModelEvent TableModelListener TableRowSorter TableStringConverter TableUI TableView TabSet TabStop TabularData TabularDataSupport TabularType TAG_ALTERNATE_IIOP_ADDRESS TAG_CODE_SETS TAG_INTERNET_IOP TAG_JAVA_CODEBASE TAG_MULTIPLE_COMPONENTS TAG_ORB_TYPE TAG_POLICIES TAG_RMI_CUSTOM_MAX_STREAM_FORMAT TagElement TaggedComponent TaggedComponentHelper TaggedComponentHolder TaggedProfile TaggedProfileHelper TaggedProfileHolder Target TargetDataLine TargetedNotification TCKind Templates TemplatesHandler Text Text TextAction TextArea TextAttribute TextComponent TextEvent TextField TextHitInfo TextInputCallback TextLayout TextLayout.CaretPolicy TextListener TextMeasurer TextOutputCallback TextSyntax TextUI TexturePaint Thread Thread.State Thread.UncaughtExceptionHandler THREAD_POLICY_ID ThreadDeath ThreadFactory ThreadGroup ThreadInfo ThreadLocal ThreadMXBean ThreadPolicy ThreadPolicyOperations ThreadPolicyValue ThreadPoolExecutor ThreadPoolExecutor.AbortPolicy ThreadPoolExecutor.CallerRunsPolicy ThreadPoolExecutor.DiscardOldestPolicy ThreadPoolExecutor.DiscardPolicy Throwable Tie TileObserver Time TimeLimitExceededException TIMEOUT TimeoutException Timer Timer Timer TimerMBean TimerNotification TimerTask Timestamp Timestamp TimeUnit TimeZone TimeZoneNameProvider TitledBorder Tool ToolBarUI Toolkit ToolProvider ToolTipManager ToolTipUI TooManyListenersException Track TRANSACTION_MODE TRANSACTION_REQUIRED TRANSACTION_ROLLEDBACK TRANSACTION_UNAVAILABLE TransactionalWriter TransactionRequiredException TransactionRolledbackException TransactionService Transferable TransferHandler TransferHandler.DropLocation TransferHandler.TransferSupport Transform TransformAttribute Transformer TransformerConfigurationException TransformerException TransformerFactory TransformerFactoryConfigurationError TransformerHandler TransformException TransformParameterSpec TransformService TRANSIENT Transmitter Transparency TRANSPORT_RETRY TrayIcon TrayIcon.MessageType TreeCellEditor TreeCellRenderer TreeExpansionEvent TreeExpansionListener TreeMap TreeModel TreeModelEvent TreeModelListener TreeNode TreePath TreeSelectionEvent TreeSelectionListener TreeSelectionModel TreeSet TreeUI TreeWillExpandListener TrustAnchor TrustManager TrustManagerFactory TrustManagerFactorySpi Type TypeCode TypeCodeHolder TypeConstraintException TypeElement TypeInfo TypeInfoProvider TypeKind TypeKindVisitor6 TypeMirror TypeMismatch TypeMismatch TypeMismatch TypeMismatchHelper TypeMismatchHelper TypeNotPresentException TypeParameterElement Types Types TypeVariable TypeVariable TypeVisitor UID UIDefaults UIDefaults.ActiveValue UIDefaults.LazyInputMap UIDefaults.LazyValue UIDefaults.ProxyLazyValue UIEvent UIManager UIManager.LookAndFeelInfo UIResource ULongLongSeqHelper ULongLongSeqHolder ULongSeqHelper ULongSeqHolder UndeclaredThrowableException UndoableEdit UndoableEditEvent UndoableEditListener UndoableEditSupport UndoManager UnexpectedException UnicastRemoteObject UnionMember UnionMemberHelper UNKNOWN UNKNOWN UnknownAnnotationValueException UnknownElementException UnknownEncoding UnknownEncodingHelper UnknownError UnknownException UnknownFormatConversionException UnknownFormatFlagsException UnknownGroupException UnknownHostException UnknownHostException UnknownObjectException UnknownServiceException UnknownTypeException UnknownUserException UnknownUserExceptionHelper UnknownUserExceptionHolder UnmappableCharacterException UnmarshalException UnmarshalException Unmarshaller Unmarshaller.Listener UnmarshallerHandler UnmodifiableClassException UnmodifiableSetException UnrecoverableEntryException UnrecoverableKeyException Unreferenced UnresolvedAddressException UnresolvedPermission UnsatisfiedLinkError UnsolicitedNotification UnsolicitedNotificationEvent UnsolicitedNotificationListener UNSUPPORTED_POLICY UNSUPPORTED_POLICY_VALUE UnsupportedAddressTypeException UnsupportedAudioFileException UnsupportedCallbackException UnsupportedCharsetException UnsupportedClassVersionError UnsupportedDataTypeException UnsupportedEncodingException UnsupportedFlavorException UnsupportedLookAndFeelException UnsupportedOperationException URI URIDereferencer URIException URIParameter URIReference URIReferenceException URIResolver URISyntax URISyntaxException URL URLClassLoader URLConnection URLDataSource URLDecoder URLEncoder URLStreamHandler URLStreamHandlerFactory URLStringHelper USER_EXCEPTION UserDataHandler UserException UShortSeqHelper UShortSeqHolder UTFDataFormatException Util UtilDelegate Utilities UUID ValidationEvent ValidationEventCollector ValidationEventHandler ValidationEventImpl ValidationEventLocator ValidationEventLocatorImpl ValidationException Validator Validator ValidatorHandler ValueBase ValueBaseHelper ValueBaseHolder ValueExp ValueFactory ValueHandler ValueHandlerMultiFormat ValueInputStream ValueMember ValueMemberHelper ValueOutputStream VariableElement VariableHeightLayoutCache Vector VerifyError VersionSpecHelper VetoableChangeListener VetoableChangeListenerProxy VetoableChangeSupport View ViewFactory ViewportLayout ViewportUI VirtualMachineError Visibility VisibilityHelper VM_ABSTRACT VM_CUSTOM VM_NONE VM_TRUNCATABLE VMID VoiceStatus Void VolatileImage W3CDomHandler W3CEndpointReference W3CEndpointReferenceBuilder WCharSeqHelper WCharSeqHolder WeakHashMap WeakReference WebEndpoint WebFault WebMethod WebParam WebParam.Mode WebResult WebRowSet WebService WebServiceClient WebServiceContext WebServiceException WebServiceFeature WebServiceFeatureAnnotation WebServicePermission WebServiceProvider WebServiceRef WebServiceRefs WildcardType WildcardType Window WindowAdapter WindowConstants WindowEvent WindowFocusListener WindowListener WindowStateListener WrappedPlainView Wrapper WritableByteChannel WritableRaster WritableRenderedImage WriteAbortedException Writer WrongAdapter WrongAdapterHelper WrongPolicy WrongPolicyHelper WrongTransaction WrongTransactionHelper WrongTransactionHolder WStringSeqHelper WStringSeqHolder WStringValueHelper X500Principal X500PrivateCredential X509Certificate X509Certificate X509CertSelector X509CRL X509CRLEntry X509CRLSelector X509Data X509EncodedKeySpec X509ExtendedKeyManager X509Extension X509IssuerSerial X509KeyManager X509TrustManager XAConnection XADataSource XAException XAResource Xid XmlAccessOrder XmlAccessorOrder XmlAccessorType XmlAccessType XmlAdapter XmlAnyAttribute XmlAnyElement XmlAttachmentRef XmlAttribute XMLConstants XMLCryptoContext XMLDecoder XmlElement XmlElement.DEFAULT XmlElementDecl XmlElementDecl.GLOBAL XmlElementRef XmlElementRef.DEFAULT XmlElementRefs XmlElements XmlElementWrapper XMLEncoder XmlEnum XmlEnumValue XMLEvent XMLEventAllocator XMLEventConsumer XMLEventFactory XMLEventReader XMLEventWriter XMLFilter XMLFilterImpl XMLFormatter XMLGregorianCalendar XmlID XmlIDREF XmlInlineBinaryData XMLInputFactory XmlJavaTypeAdapter XmlJavaTypeAdapter.DEFAULT XmlJavaTypeAdapters XmlList XmlMimeType XmlMixed XmlNs XmlNsForm XMLObject XMLOutputFactory XMLParseException XmlReader XMLReader XMLReaderAdapter XMLReaderFactory XmlRegistry XMLReporter XMLResolver XmlRootElement XmlSchema XmlSchemaType XmlSchemaType.DEFAULT XmlSchemaTypes XmlSeeAlso XMLSignature XMLSignature.SignatureValue XMLSignatureException XMLSignatureFactory XMLSignContext XMLStreamConstants XMLStreamException XMLStreamReader XMLStreamWriter XMLStructure XmlTransient XmlType XmlType.DEFAULT XMLValidateContext XmlValue XmlWriter XPath XPathConstants XPathException XPathExpression XPathExpressionException XPathFactory XPathFactoryConfigurationException XPathFilter2ParameterSpec XPathFilterParameterSpec XPathFunction XPathFunctionException XPathFunctionResolver XPathType XPathType.Filter XPathVariableResolver XSLTTransformParameterSpec ZipEntry ZipError ZipException ZipFile ZipInputStream ZipOutputStream ZoneView _BindingIteratorImplBase _BindingIteratorStub _DynAnyFactoryStub _DynAnyStub _DynArrayStub _DynEnumStub _DynFixedStub _DynSequenceStub _DynStructStub _DynUnionStub _DynValueStub _IDLTypeStub _NamingContextExtStub _NamingContextImplBase _NamingContextStub _PolicyStub _Remote_Stub _ServantActivatorStub _ServantLocatorStub ============================================= SECTION 6: ============================================= ============================================= SECTION 7: Various errors/messages: ============================================= ------ Note: ------ Error 25099 Error 25099: Unzipping core files failed. Posted: Jun 14, 2008 3:01 AM Reply I am getting this error trying to install the Java 6 Update 10 b25 JRE on a Windows Server 2003 machine. The install progresses for a few minutes and then when it gets to the "Registering product..." phase this error comes up. The only thing unusual about this machine is that I previously (months ago) ran a JRE 6 install that I had to kill manually after 4 hours of inactivity and then I had to manually clean up the registry to get the installer to not think that Java was already installed. I am sure this has something to do with it but I do not know where to start looking for a solution to this problem. Any suggestions? Reply I got this error several times. I was trying to install the public JRE as part of the 1.6.0_10 install, then I tried downloading the JRE from java.com and installing it separately. Each time, I deleted all the Javasoft registry keys first. What finally worked? Well, for some reason, Java Update (jusched.exe) was still running even though I uninstalled my previous JDK and all JRE's - killing it from the Task Manager did the trick. (Though I probably could have terminated it properly, through the Service Control Manager.) I then tried installing the JRE downloaded from java.com and it worked. I have not tried the 1.6.0_10 JDK since killing jusched but I'm figuring it would probably have worked too. denglish Posts: 1 Re: Error 25099: Unzipping core files failed. Posted: Mar 18, 2009 6:42 AM in response to: sjsobol Reply I found that I also needed to kill jqs.exe in Windows Task Manager in addition to removing all Java files and directories. After that, Java 6 installed fine. dolobono Posts: 1 Re: Error 25099: Unzipping core files failed. Posted: Apr 23, 2009 4:56 PM in response to: denglish Reply I did exactly what you did, as well as using the "download offline" option on the Java help page. This worked - thanks!! joestanley Posts: 1 Re: Error 25099: Unzipping core files failed. Posted: May 1, 2009 12:26 PM in response to: denglish Reply Thanks!! Uninstalling all previous Java and killing jqs.exe in Task Manager worked!! Guys, I have tried various ways of solving this problems from webs and Java.com solutions itself but they don't work for me. Here is how it might help it happens to failed trying other ways. This step might help you if you cannot find jqs.exe in you computer Task Manager. 1. Start Task Manager by clicking Ctr l+Alt+Delete keys on you keyboard. 2. Open Task Manager. 3. Click on Processes tab. 4. Find and select the process javaw.exe if you cannot find jqs.exe. 5. Click End Process button after selecting javaw.exe. 6. Close Task manager window Now it should be fine. ------ Note: ------ Error: 25099 during Java installation -------------------------------------------------------------------------------- This article applies to: Platform(s): All Platforms Browser(s): Internet Explorer 6.x , Internet Explorer 7.x , Mozilla 1.4+ , Firefox Java version(s): 6.0 , 6u10+ -------------------------------------------------------------------------------- SYMPTOMS While Java installation is in progress, a message box with the following error is displayed: 'Error 25099. Unzipping core files failed.' -------------------------------------------------------------------------------- CAUSE This error indicates that the Java installation process has failed. Installation process can fail if process named 'Java Quick Starter ' (jqs.exe) is running and has not terminated after uninstallation. -------------------------------------------------------------------------------- WORKAROUND Note: Below workaround has been verified to work on Windows XP, Windows 2000 and Windows 2003 operating systems. Step 1 :Uninstall older versions of the Java Software. See the instructions on how to uninstall the Java from a Windows computer Step 2 : Stop or terminate the jqs.exe process. There are two methods to end this process. Method 1: Steps to terminate the jqs.exe process through Windows Task Manager utility. Start Task Manager by clicking Ctr l+Alt+Delete keys on you keyboard. Open Task Manager. Click on Processes tab. Find and select the process jqs.exe. Click End Process button Close Task manager window Method 2: Steps to terminate the JQS process through Windows Command Prompt utility. Click Start and then Run. In the Run window type command cmd, to open Command Prompt window. In the Command prompt window type net stop "Java Quick Starter" and press enter. If the above command worked then you get message ' The Java Quick Starter service was stopped successfully.' Step 3 : Download and install Java. Go to Java.com Click on the Free Java Download button, and start the installation process ------- Note: ------- Error 1722. There is a problem with this Windows Installer package. -------------------------------------------------------------------------------- This article applies to: Platform(s): Windows 98 , Windows ME , Windows 2000 , Windows XP , Vista , Windows 2003 Browser(s): All Browsers Java version(s): 1.4.2_xx , 1.5.0 , 6.0 -------------------------------------------------------------------------------- SYMPTOMS Java Runtime Environment (JRE) installation has not completed and an error appears: Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. -------------------------------------------------------------------------------- CAUSE Error 1722 is an InstallShield error code. It indicates that the installation process has failed. The exact reason for this error is not known at this time. -------------------------------------------------------------------------------- SOLUTION Possible workaround is try to download and install the offline installation package from the manual download page: ----- Note: ----- Common download and installation errors. -------------------------------------------------------------------------------- This article applies to: Platform(s): Windows 98 , Windows ME , Windows 2000 , Windows XP , Vista Browser(s): Internet Explorer 5.5 , Internet Explorer 6.x , Internet Explorer 7.x , Mozilla 1.4+ , Firefox Java version(s): 1.4.2_xx , 1.5.0 , 6.0 -------------------------------------------------------------------------------- SYMPTOMS During installation of the Java, a dialog box appears displaying one of the following error codes: 1035, 1305, 1311, 1324, 1327, 1335, 1600, 1601, 1606, 1624, 1643, 1722, 1744, 1788, 2352, and 2755 -------------------------------------------------------------------------------- CAUSE These errors are InstallShield error codes, which indicate that an action failed during installation process. -------------------------------------------------------------------------------- SOLUTION Please try to download and install the offline installer: Offline installer ------ Note: ------ Error: 25099 during Java installation -------------------------------------------------------------------------------- This article applies to: Platform(s): All Platforms Browser(s): Internet Explorer 6.x , Internet Explorer 7.x , Mozilla 1.4+ , Firefox Java version(s): 6.0 , 6u10+ -------------------------------------------------------------------------------- SYMPTOMS While Java installation is in progress, a message box with the following error is displayed: 'Error 25099. Unzipping core files failed.' -------------------------------------------------------------------------------- CAUSE This error indicates that the Java installation process has failed. Installation process can fail if process named 'Java Quick Starter ' (jqs.exe) is running and has not terminated after uninstallation. -------------------------------------------------------------------------------- WORKAROUND Note: Below workaround has been verified to work on Windows XP, Windows 2000 and Windows 2003 operating systems. Step 1 :Uninstall older versions of the Java Software. See the instructions on how to uninstall the Java from a Windows computer Step 2 : Stop or terminate the jqs.exe process. There are two methods to end this process. Method 1: Steps to terminate the jqs.exe process through Windows Task Manager utility. Start Task Manager by clicking Ctr l+Alt+Delete keys on you keyboard. Open Task Manager. Click on Processes tab. Find and select the process jqs.exe. Click End Process button Close Task manager window Method 2: Steps to terminate the JQS process through Windows Command Prompt utility. Click Start and then Run. In the Run window type command cmd, to open Command Prompt window. In the Command prompt window type net stop "Java Quick Starter" and press enter. If the above command worked then you get message ' The Java Quick Starter service was stopped successfully.' Step 3 : Download and install Java. Go to Java.com Click on the Free Java Download button, and start the installation process ------ Note: ------ Windows Installation (IFTW) and Java Update FAQ -------------------------------------------------------------------------------- Questions: Q. I have "Check for Updates Automatically" checked in the Java Plug-in Control Panel, but scheduled automatic updates do not seem to happening. Is there something wrong? Q: I downloaded the installer and it is only 1MB. Why is it so small? Q: Why does Java Update ask me to reboot? Q: I had the Java Plug-in Control Panel open for Java Update and the About tab showed version x.x.x. Then I ran Java Update and it still showed version x.x.x. Why is this? Q: Netscape/Mozilla is not working correctly with Java Plug-in. Why? Q: I try to install on the D:\ drive and Java Update is still installing files onto the C:\ drive. Why? Q: How can I uninstall the Java Update version I just installed? Q. After the JRE bootstrap installer is downloaded and executed, the message below shows up. Why is this? This installer cannot proceed with the current Internet Connection settings of this system. Please check your Control Panel -> Internet Options, and make sure the settings and proxy information are correct, and/or make sure you can view webpages through Internet Explorer Q: I found two processes—jucheck.exe and jusched.exe—running in the background of my system after installing JRE. Is there a way to shut them down? Q . After Java Update updates my system, my browser still uses the Microsoft VM, or an older version of the Sun Java VM, to run applets. What's wrong? Q: When I click the Update Now button from the Java Control Panel, it complains about the system being "offline." What does that means? Q: I followed the instruction to install version x.x.x. After the installation and reboot, a message popped-up from system tray saying an update is available for download. What should I do? Q: I want to try out Java Update but I am afraid beta software may cause problems on my computer. What should I do? Q: I encountered the following error when running the J2SE installer: Error 1606: Could not access network location file MSI/CAB and still fail after immediate retry. Q: I encountered the following error when running the J2SE installer: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. Q: Error 1311: Source File Not Found. Could not find C:\Downloads\ja555000.cab. Q: Error 1722. There is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vender. Questions and Answers: Q. I have "Check for Updates Automatically" checked in the Java Plug-in Control Panel, but scheduled automatic updates do not seem to happening. Is there something wrong? A: The automatic update feature works only on Windows 2000 with SP3 and WindowsXP. If you are running on one of the other supported operating system, this feature will not work. If you want to do an update, use the Update Now button for manually updating Java. Q: I downloaded the installer and it is only 1MB. Why is it so small? A: The Java installer is designed for Install On Demand. It will download more installer files based on user selection and system configuration. The size of installer should be roughly 1MB. Q: Why does Java Update ask me to reboot? A: Rebooting may be necessary for any of the following reasons: If you use Netscape/Mozilla browsers and if they are java-enabled, files of previous jre's may have been locked. Installing Windows Installer 2.0 (Microsoft technology used by the Java installer) sometimes requires rebooting. Q: I had the Java Plug-in Control Panel open for Java Update and the About tab showed version x.x.x. Then I ran Java Update and it still showed version x.x.x. Why is this? A: You need to close and restart the Java Plug-in Control Panel to get the updated Control Panel. Q: Netscape/Mozilla is not working correctly with Java Plug-in. Why? A: Were you asked to reboot the system ? Please reboot the system and try again. Q: I try to install on the D:\ drive and Java Update is still installing files onto the C:\ drive. Why? A: Regardless of whether an alternate target directory was selected, Java Update needs to install some update files on the Windows system drive . Doing so saves download time on future updates to the latest version of Java. Q: How can I uninstall the Java Update version I just installed? There are two ways to accomplish this: If you want to uninstall the Java 2 JRE, use the "Add/Remove Programs" utility in the Microsoft Windows Control Panel (Start->Settings->Control Panel to get to "Add/Remove Programs"). Alternatively, if you still have the original installation program that you used to install the Java 2 JRE, you can double-click on it. This will take you to a screen with Modify and Remove options. Select Remove to uninstall the JRE. Note that you must be connected to the Internet for this to work. Q. After the JRE bootstrap installer is downloaded and executed, the message below shows up. Why is this? This installer cannot proceed with the current Internet Connection settings of your system. In your Windows Control Panel, please check Internet Options -> Connections to make sure the settings and proxy information are correct. A: The JRE bootstrap installer uses the system Internet Connection setttings to connect to the web for downloading extra files. If you are behind a firewall and require proxy settings, make sure the proxy settings in Internet Options/Internet Properties are set up properly (Start->Control Panel->Internet Options/Internet Properties->Connections->LAN Settings ...). If you can browser the external web (i.e., outside the firewall) with Internet Explorer, then your proxy settings are properly set up. The installer doesn't understand the proxy settings specified in Netscape/Mozilla. Q: I found two processes—jucheck.exe and jusched.exe—running in the background of my system after installing JRE. Is there a way to shut them down? A: jusched.exe is the scheduler process of Java Update; jucheck.exe is the process for checking/performing updates in Java Update. These processes run automatically and transparently to users. To shutdown these processes, simply uncheck the "Check for Updates Automatically" checkbox in the Update tab of Java Plug-in Control Panel. Q . After Java Update updates my system, my browser still uses the Microsoft VM, or an older version of the Sun Java VM, to run applets. What's wrong? A: If you installed the JRE through the Custom option but unchecked the browser selections, you may run into this situation. To fix the problem, go to the Browser tab in Java Plug-in Control Panel and check the browsers that you want to run the newly installed version of Java. Q: When I click the "Update Now" button from the Java Control Panel, it complains about the system being "offline." What does that means? A: Java Update can only be run if the system is connected to the network. A system that is not connected to the network is referred to as being "offline". When the Update Now button is clicked, it will check the online/offline status of your system. If your system is not currently connected to the network or dial-up networking is disconnected, the error message will show up. Check that your system is currently connected to the network and try it again. Q: I followed the instruction to install version x.x.x. After the installation and reboot, a message popped-up from system tray saying an update is available for download. What should I do? A: The message is part of the Java Auto Update mechanism, which detects at user login time if a newer version of the JRE is available for download . You may simply click on the system tray Java Update icon to download and install the update. Q: I want to run Java Update but I am afraid it may cause problems on my computer. What should I do? A: You may want to backup your Windows registry before testing out Java Update. The following command will export the necessary registry keys to a file: regedit -e reg.1 -t HKEY_LOCAL_MACHINE regedit -e reg.2 -t HKEY_CURRENT_USER regedit -e reg.3 -t HKEY_CLASSES_ROOT To fully restore the registry keys, the following command can be used to import the exported registry values: regedit -i reg.1 regedit -i reg.2 regedit -i reg.3 Q: I encountered the following error when running the J2SE installer: Error 1606: Could not access network location file MSI/CAB and still fail after immediate retry. What does it mean? A: This problem occurs when the server is too busy or when the network is too congested to serve the file. Please retry by running the installer again. Q: I encountered the following error when running the J2SE installer: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. A: There are several possible reasons: Proxy server requires authentication; network connection fails; download manager software interrupts the download process, e.g., GetRight; TSR (Terminate and Stay Resident) programs, like Norton AntiVirus, may distract the installation process. To address these problems, please make sure third-party downloader/TSR programs are turned off and the network connection is setup properly. Also, if a proxy is in use, make sure that proxy authentication is turned off. Q: Error 1311: Source File Not Found. Could not find C:\Downloads\ja555000.cab. A: This is a known MSI engine problem. See following: http://support.microsoft.com/default.aspx?scid=kb;[LN];Q290106 http://support.microsoft.com/default.aspx?scid=kb;[LN];Q307346 http://support.microsoft.com/default.aspx?scid=kb;[LN];290896 Q: Error 1722. There is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vender. A: This is caused by previous unsuccessful install/uninstall of software through MSI engine. This problem will usually disappear if the users run the installer again. ------ Note: ------ Admin console throws error 500 with java.lang.NullPointerExcetion and SAXParseException Premature end of file Technote (troubleshooting) This document applies only to the following language version(s): US English Problem(Abstract) Trying to login to administrative console throws error 500 with java.lang.NullPointerException. Symptom After running out of disk space, trying to login to the administrative console failed with error 500 and following Exception in SystemOut.log: java.lang.NullPointerException at org.apache.jsp._console._jspService(_console.java:172) at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase. java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied (ServletWrapper.java:266) Also in the stderr.log: com.ibm.ws.util.prefs.InvalidPreferencesFormatException: org.xml.sax.SAXParseException Premature end of file. at com.ibm.ws.util.prefs.XmlHelper.importPreferences(XmlHelper.java:126) at com.ibm.ws.util.prefs.BasePreferencesImpl.importPreferences(BasePreferencesImpl.java:449) at com.ibm.ws.console.core.bean.UserPreferenceBean.init(UserPreferenceBean.java:58) at com.ibm.ws.console.core.bean.UserPreferenceBean.setUserName(UserPreferenceBean.java:35) at com.ibm.ws.console.core.User.valueBound(User.java:81) Cause When user tries to login to administrative console, a preferences.xml file is built in /wstemp/. If creation of preferences.xml fails due to lack of disk space, it leaves preferences.xml file with zero length. This zero length preferences.xml file causes the "SAXParseException Premature end of file". Resolving the problem To resolve this issue: Clean up the disk space problem. Delete the /wstemp//preferences.xml file. Try to login to administrative console. This should build a new preferences.xml with the correct data and should allow the user to login to administrative console. Cross Reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK ============================================= SECTION 8: Other Common Errors: ============================================= >> Common Error Messages on Microsoft Windows Systems 'javac' is not recognized as an internal or external command, operable program or batch file If you receive this error, Windows cannot find the compiler (javac). Here's one way to tell Windows where to find javac. Suppose you installed the JDK in C:\jdk6. At the prompt you would type the following command and press Enter: C:\jdk6\bin\javac HelloWorldApp.java If you choose this option, you'll have to precede your javac and java commands with C:\jdk6\bin\ each time you compile or run a program. To avoid this extra typing, consult the section Update the PATH variable in the JDK 6 installation instructions. Class names, 'HelloWorldApp', are only accepted if annotation processing is explicitly requested If you receive this error, you forgot to include the .java suffix when compiling the program. Remember, the command is javac HelloWorldApp.java not javac HelloWorldApp. >> Common Error Messages on UNIX Systems javac: Command not found If you receive this error, UNIX cannot find the compiler, javac. Here's one way to tell UNIX where to find javac. Suppose you installed the JDK in /usr/local/jdk6. At the prompt you would type the following command and press Return: /usr/local/jdk6/javac HelloWorldApp.java Note: If you choose this option, each time you compile or run a program, you'll have to precede your javac and java commands with /usr/local/jdk6/. To avoid this extra typing, you could add this information to your PATH variable. The steps for doing so will vary depending on which shell you are currently running. Class names, 'HelloWorldApp', are only accepted if annotation processing is explicitly requested If you receive this error, you forgot to include the .java suffix when compiling the program. Remember, the command is javac HelloWorldApp.java not javac HelloWorldApp. >> Syntax Errors (All Platforms) If you mistype part of a program, the compiler may issue a syntax error. The message usually displays the type of the error, the line number where the error was detected, the code on that line, and the position of the error within the code. Here's an error caused by omitting a semicolon (;) at the end of a statement: testing.java:14: `;' expected. System.out.println("Input has " + count + " chars.") ^ 1 error Sometimes the compiler can't guess your intent and prints a confusing error message or multiple error messages if the error cascades over several lines. For example, the following code snippet omits a semicolon (;) from the bold line: while (System.in.read() != -1) count++ System.out.println("Input has " + count + " chars."); When processing this code, the compiler issues two error messages: testing.java:13: Invalid type expression. count++ ^ testing.java:14: Invalid declaration. System.out.println("Input has " + count + " chars."); ^ 2 errors The compiler issues two error messages because after it processes count++, the compiler's state indicates that it's in the middle of an expression. Without the semicolon, the compiler has no way of knowing that the statement is complete. If you see any compiler errors, then your program did not successfully compile, and the compiler did not create a .class file. Carefully verify the program, fix any errors that you detect, and try again. >> Semantic Errors In addition to verifying that your program is syntactically correct, the compiler checks for other basic correctness. For example, the compiler warns you each time you use a variable that has not been initialized: testing.java:13: Variable count may not have been initialized. count++ ^ testing.java:14: Variable count may not have been initialized. System.out.println("Input has " + count + " chars."); ^ 2 errors Again, your program did not successfully compile, and the compiler did not create a .class file. Fix the error and try again. >> Runtime Problems Error Messages on Microsoft Windows Systems Exception in thread "main" java.lang.NoClassDefFoundError: HelloWorldApp If you receive this error, java cannot find your bytecode file, HelloWorldApp.class. One of the places java tries to find your .class file is your current directory. So if your .class file is in C:\java, you should change your current directory to that. To change your directory, type the following command at the prompt and press Enter: cd c:\java The prompt should change to C:\java>. If you enter dir at the prompt, you should see your .java and .class files. Now enter java HelloWorldApp again. If you still have problems, you might have to change your CLASSPATH variable. To see if this is necessary, try clobbering the classpath with the following command. set CLASSPATH= Now enter java HelloWorldApp again. If the program works now, you'll have to change your CLASSPATH variable. To set this variable, consult the Update the PATH variable section in the JDK 6 installation instructions. The CLASSPATH variable is set in the same manner. Exception in thread "main" java.lang.NoClassDefFoundError: HelloWorldApp/class A common mistake made by beginner programmers is to try and run the java launcher on the .class file that was created by the compiler. For example, you'll get this error if you try to run your program with java HelloWorldApp.class instead of java HelloWorldApp. Remember, the argument is the name of the class that you want to use, not the filename. Exception in thread "main" java.lang.NoSuchMethodError: main The Java VM requires that the class you execute with it have a main method at which to begin execution of your application. A Closer Look at the "Hello World!" Application discusses the main method in detail. Error Messages on UNIX Systems Exception in thread "main" java.lang.NoClassDefFoundError: HelloWorldApp If you receive this error, java cannot find your bytecode file, HelloWorldApp.class. One of the places java tries to find your bytecode file is your current directory. So, for example, if your bytecode file is in /home/jdoe/java, you should change your current directory to that. To change your directory, type the following command at the prompt and press Return: cd /home/jdoe/java If you enter pwd at the prompt, you should see /home/jdoe/java. If you enter ls at the prompt, you should see your .java and .class files. Now enter java HelloWorldApp again. If you still have problems, you might have to change your CLASSPATH environment variable. To see if this is necessary, try clobbering the classpath with the following command. unset CLASSPATH Now enter java HelloWorldApp again. If the program works now, you'll have to change your CLASSPATH variable in the same manner as the PATH variable above. Exception in thread "main" java.lang.NoClassDefFoundError: HelloWorldApp/class A common mistake made by beginner programmers is to try and run the java launcher on the .class file that was created by the compiler. For example, you'll get this error if you try to run your program with java HelloWorldApp.class instead of java HelloWorldApp. Remember, the argument is the name of the class that you want to use, not the filename. Exception in thread "main" java.lang.NoSuchMethodError: main The Java VM requires that the class you execute with it have a main method at which to begin execution of your application. A Closer Look at the "Hello World!" Application discusses the main method in detail. ============================================= SECTION 9: Java docs: ============================================= 9.1 Compile and Runtime Errors in Java: ======================================= Chapter 1 Introduction Compilers are notorious for their obscure error messages like “not a statement” that leave you wondering what they mean. JAVA is the most widely used language for teaching and learning introductory programming, and most students and teachers use the Sun SDK (System Development Kit) either directly or indirectly through a development environment like BlueJ or DrJava. The error messages produced by this compiler are terse and many novices find it difficult to achieve even syntactically correct programs. This document is a guide to understanding and fixing errors in JAVA. Chapter 2 lists the error messages from the compiler and describes typical mistakes that give rise to them. Chapter 3 does the same for runtime exceptions. Chapter 4 is a short discussion of equality and assignment in JAVA, while Chapter 5 presents ways of debugging without the use of a debugger. The ECLIPSE development environment has its own compiler for JAVA. While the environment is not as elementary as those intended for novices, it has much to recommend it—even in introductory courses—because of its superior error messages and its support for identifying and correcting syntax errors. The compiler is incremental meaning that it checks the correctness of your program as you type. ECLIPSE error message are different from those of the Sun SDK and will be presented alongside them. If you doubt that an error message is correct, you can consult the formal definition of the JAVA language which is contained in the book The Java Language Specification by James Gosling, Bill Joy, Guy L. Steele Jr. and Gilad Bracha. It can also be downloaded from http://java.sun.com/docs/books/jls/index.html. 5 Chapter 2 Compile-time Errors Before we discuss the various errors, it is important to understand that compilers are not very good at recovering from errors. Frequently, a single small mistake will cause the compiler to issue a cascade of messages. For example, in the following code, we forgot to write the closing brace of the method f: class MyClass { void f() { int n = 10; // Error, closing brace is missing void g() { int m = 20; } } An attempt to compile the program results in three error messages: MyClass.java:5: illegal start of expression void g() { ^ MyClass.java:8: ’;’ expected } ^ MyClass.java:9: ’}’ expected ^ Do not invest any effort in trying to fix multiple error messages! Concentrate on fixing the first error and then recompile. ECLIPSE is much better at diagnosing this error and produces only one message: Syntax error, insert "}" to complete MethodBody. 6 2.1 Syntax errors Some errors are caused by violations of the syntax of JAVA. Although they are easy to understand, there is no easy way to find the exact cause of such errors except by checking the code around the location of the error character by character looking for the syntax error. 2.1.1 . . . expected The syntax of JAVA is very specific about the required punctuation. This error occurs, for example, if you forget a semicolon at the end of a statement or don’t balance parentheses: if (i > j // Error, unbalanced parentheses max = i // Error, missing semicolon else max = j; Unfortunately, this syntax error is not necessarily caught precisely at the point of the mistake so you must carefully check the preceding characters in the line or even in a previous line in order to find the problem. ECLIPSE: Syntax error, insert ") Statement" to complete IfStatement. Syntax error, insert ";" to complete Statement ECLIPSE is more informative as to the precise syntax error encountered. 2.1.2 unclosed string literal String literals must be enclosed in quotation marks.1 This error occurs if you fail to terminate the literal with quotation marks. Fortunately, the syntax of JAVA requires that a string literal appear entirely on one line so the error message appears on the same line as the mistake. If you need a string literal that is longer than a single line, create two or more literals and concatenate them with +: String longString = "This is first half of a long string " + "and this is the second half."; ECLIPSE: String literal is not properly closed by a double-quote. In ECLIPSE you can write a string literal of arbitrary length and the environment will break the string and insert the + automatically. 1A literal is a source-code representation of a value; most literals are of primitive types like int or char, but there are also literals of type String and the literal null of any reference type. 7 2.1.3 illegal start of expression Most programming constructs are either statements or expressions. This error occurs when an expression is expected but not found. In JAVA, an assignment statement is considered to be an expression which returns a value, so errors concerning expressions also apply to assignment statements.2 Examples: • An extra right parenthesis after the condition of an if-statement: if (i > j) ) // Error, extra parenthesis max = i; ECLIPSE: Syntax error on token ")", delete this token.3 ECLIPSE diagnoses this as a simple syntax error and does not mention expressions. • Forgetting the right-hand side of an assignment statement: max = ; // Error, missing righthand side ECLIPSE: Syntax error on token "=", Expression expected after this token. 2.1.4 not a statement This error occurs when a syntactically correct statement does not appear where it should. Examples: • Writing an assignment statement without the assignment operator: max ; // Error, missing = ECLIPSE: Syntax error, insert "AssignmentOperator Expression" to complete Expression. • Misspelling else: if (i > j) max = i; els ; // Error, else not spelled correctly The reason you do not get “else expected” is that you need not write an else alternative so this just looks like a bad statement. 2The value of an assignment statement considered as an expression is the value of the expression on the right-hand side that is assigned to the variable on the left-hand side. 3The syntax of a programming language is defined in terms of tokens consisting of one or more characters. Identifiers and reserved keywords are tokens as are single characters like + and sequences of characters like !=. 8 ECLIPSE: els cannot be resolved4 Syntax error, insert "AssignmentOperator Expression" to complete Expression. • The following code: if (i > j) max = i; els // Error, else not spelled correctly max = j; results in a weird error message: x.java:6: cannot find symbol symbol : class els location: class x els The reason is that the compiler interprets this as a declaration: els max = j; and can’t find a class els as the type of the variable max. ECLIPSE: Duplicate local variable max els cannot be resolved to a type. These messages are more helpful: first, the use of the word type instead of class is more exact because the type of a variable need not be a class (it could be a primitive type or interface); second, the message about the duplicate variable gives an extra clue as to the source of the error. • The error can also be caused by attempting to declare a variable whose name is that of a reserved keyword: void f() { int default = 10; } ECLIPSE: Syntax error on token "default", invalid VariableDeclaratorId. 4The same identifier can be used in different methods and classes. An important task of the compiler is to resolve the ambiguity of multiple uses of the same identifer; for example, if a variable is declared both directly within a class and also within a method, the use of its unqualified name is resolved in favor of the local variable. This error message simply means that the compiler could not obtain an (unambiguous) meaning for the identifier els. 9 2.2 Identifiers 2.2.1 cannot find symbol This is probably the most common compile-time error. All identifiers in JAVA must be declared before being used and an inconsistency between the declaration of an identifier and its use will give rise to this error. Carefully check the spelling of the identifier. It is easy to make a mistake by using a lower-case letter instead of an upper case one, or to confuse the letter O with the numeral 0 and the letter l with the numeral 1. Other sources of this error are: calling a constructor with an incorrect parameter signature, and using an identifier outside its scope, for example, using an identifier declared in a for-loop outside the loop: int[] a = {1, 2, 3}; int sum = 0; for (int i = 0; i < a.length; i++) sum = sum + a[i]; System.out.println("Last = " + i); // Error, i not in scope ECLIPSE: . . . cannot be resolved. 2.2.2 . . . is already defined in . . . An identifier can only be declared once in the same scope: int sum = 0; double sum = 0.0; // Error, sum already defined ECLIPSE: Duplicate local variable sum. 2.2.3 array required but . . . found This error is caused by attempting to index a variable which is not an array. int max(int i, int j) { if (i > j) return i; else return j[i]; // Error, j is not an array } ECLIPSE: The type of the expression must be an array type but it resolved to int. 2.2.4 . . . has private access in . . . It is illegal to access a variable declared private outside its class. ECLIPSE: The field . . . is not visible. 10 2.3 Computation This group of errors results from code that is syntactically correct but violates the semantics of JAVA, in particular the rules relating to type checking. 2.3.1 variable . . . might not have been initialized An instance variable declared in a class has a default initial value.5 However, a local variable declared within a method does not, so you are required to initialize it before use, either in its declaration or in an assignment statement: void m(int n) { // n is initialized from the actual parameter int i, j; i = 2; // i is initialized by the assignment int k = 1; // k is initialized in its declaration if (i == n) // OK k = j; // Error, j is not initialized else j = k; } The variable must be initialized on every path from declaration to use even if the semantics of the program ensure that the path cannot be taken: void m(int n) { int i; if (n == n) // Always true i = n; else n = i; // Error, although never executed!! } ECLIPSE: The local variable . . . may not have been initialized. Note: If the expression in the if-statement can be computed at compile-time: if (true) // OK if (’n’ == ’n’) // OK the error will not occur. 2.3.2 . . . in . . . cannot be applied to . . . This error message is very common and results from an incompatibility between a method call and the method’s declaration: 5A class is a template that is used to create or instantiate instances called objects. Since memory is allocated separately for each object, these variables are called instance variables. 11 void m(int i) { ... } m(5.5); // Error, the literal is of type double, not int Check the declaration and call carefully. You can also get the error message cannot find symbol if the declaration of the method is in the API.6 ECLIPSE: The method . . . in the type . . . is not applicable for the arguments . . . . 2.3.3 operator . . . cannot be applied to . . . ,. . . Operators are only defined for certain types, although implicit type conversion is allowed between certain numeric types: int a = 5; boolean b = true; int c = a + b; // Error, can’t add a boolean value double d = a + 1.4; // OK, int is implicitly converted to double ECLIPSE: The operator + is undefined for the argument type(s) int, boolean. 2.3.4 possible loss of precision This error arises when trying to assign a value of higher precision to a variable of lower precision without an explicit type cast. Surprisingly, perhaps, floating point literals are of type double and you will get this message if you try to assign one to a variable of type float: float sum = 0.0; // Error, literal is not of type float The correct way to do this is to use a literal of type float or an explicit type cast: float sum = 0.0f; // OK float sum = (float) 0.0; // OK ECLIPSE: Type mismatch: cannot convert from double to float. 2.3.5 incompatible types JAVA checks that the type of an expression is compatible with the type of the variable in an assignment statement and this error will result if they are incompatible: boolean b = true; int a = b; // Error, can’t assign boolean to int ECLIPSE: Type mismatch: cannot convert from boolean to int. 6The Application Programming Interface (API) describes how to use the library of classes supplied as part of the JAVA system. By extension, it is also used as a name for the library itself. 12 Important note In the C language it is (unfortunately!) legal to write if (a = b) using the assignment operator instead of if (a == b) using the equality operator. The meaning is to execute the assignment, convert the value to an integer and use its value to make the decision for the if-statement (zero is false and non-zero is true). In JAVA, the assignment is legal and results in a value, but (unless a is of type boolean!) this error message will result because the expression in an if-statement must be of type boolean, not int. Writing == instead of = becomes a simple compile-time error in JAVA, whereas in C this error leads to runtime errors that are extremely difficult to find. 2.3.6 inconvertible types Not every type conversion is legal: boolean b = true; int x = (int) b; // Error, can’t convert boolean to int ECLIPSE: Type mismatch: cannot convert from . . . to . . . . 2.4 Return statements There are a number of errors related to the structure of methods and their return statements; in general they are easy to fix. 2.4.1 missing return statement When a method returns a non-void type, every path that leaves the method must have a return-statement,7 even if there is no way that the path can be executed: int max(int i, int j) { if (i > j) return i; else if (i <= j) return j; // Error: what about the path when i>j and i<=j are both false?!! } 7A path may also leave the method via a throw statement. 13 Adding a dummy alternative else return 0; at the end of the method will enable successful compilation. ECLIPSE: This method must return a result of type int. This ECLIPSE message is rather hard to understand because, clearly, the method does return a result of type int, just not on all paths. 2.4.2 missing return value A method returning a type must have a return-statement that includes an expression of the correct type: int max(int i, int j) { return; // Error, missing int expression } ECLIPSE: This method must return a result of type int. 2.4.3 cannot return a value from method whose result type is void Conversely, a return-statement in a void method must not have an expression: void m(int i, int j) { return i + j; // Error, the method was declared void } ECLIPSE: Void methods cannot return a value. 2.4.4 invalid method declaration; return type required Every method except constructors must have a return type or void specified; if not, this error will arise: max(int i, int j) { ... } The error frequently occurs because it is easy to misspell the name of a constructor; the compiler then thinks that it is a normal method without a return type: class MyClass { MyClass(int i) { ... } Myclass(int i, int j) { ... } // Error because of the lowercase c } ECLIPSE: Return type for the method is missing. 14 2.4.5 unreachable statement The error can occur if you write a statement after a return statement: void m(int j) { System.out.println("Value is " + j); return; j++; } The check is purely syntactic, so the error will occur in the following method: if (true) { return n + 1; // Only this alternative executed, but ... } else { return n 1; n = n + 1; // ... this is an error } ECLIPSE: Unreachable code. 2.5 Access to static entities The modifier static means that a variable or method is associated with a class and not with individual objects of a class.8 Normally, static entities are rarely used in JAVA (other than for the declaration of constants), because programs are written as classes to be instantiated to create at least one object: class MyClass { int field; void m(int parm) { field = parm; } public static void main(String[] args) { MyClass myclass = new MyClass(); // Create object myclass.m(5); // Call object’s method System.out.println(myclass.field); // Access object’s field } } Some teachers of elementary programming in JAVA prefer to start with a procedural approach that involves writing a class containing static variables and static methods that are accessed from the main method without instantiating an object as was done above: 8static has other uses that we do not consider here: (a) as a modifier for nested classes and (b) in static initializers. 15 class MyClass1 { static int field; static void m(int parm) { field = parm; } public static void main(String[] args) { m(5); // OK System.out.println(field); // OK } } 2.5.1 non-static variable . . . cannot be referenced from a static context Since the method main is (required to be) static, so must any variable declared in the class that is accessed by the method. Omitting the modifier results in a compile-time error: int field; // Forgot "static" ... System.out.println(field); // Error, which field? The variable field does not exist until an object of the class is instantiated, so using the identifier field by itself is impossible before objects are instantiated. Furthermore, it is ambiguous afterwards, as there may be many objects of the same class. ECLIPSE: Cannot make a static reference to the non-static field . . . . 2.5.2 non-static method . . . cannot be referenced from a static context Similarly, a non-static method cannot be called from a static method like main; the reason is a bit subtle. When a non-static method like m is executed, it receives as an implicit parameter the reference to an object. (The reference can be explicitly referred to using this.) Therefore, when it accesses variables declared in the class like field: void m(int parm) { // Forgot "static" field = parm; // Error, which field? } public static void main(String[] args) { m(5); } it is clear that the variable is the one associated with the object referenced by this. Thus, in the absence of an object, it is meaningless to call a non-static method from a static method. ECLIPSE: Cannot make a static reference to the non-static method . . . from the type . . . . 16 Chapter 3 Runtime Errors When the JAVA interpreter encounters an error during runtime it throws an exception and prints a stack trace showing the entire call stack—the list of methods called from the main program until the statement that caused the exception.1 Consider the following program: class Test { public static void main(String[] args) { String s = "Hello world"; System.out.println(s.substring(10,12)); } } We are trying to extract a substring of the string s but the upper index 12 is not within the string. Attempting to execute this code will cause an exception to be thrown: Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String index out of range: 12 at java.lang.String.substring(Unknown Source) at Test.main(Test.java:4) The exception was thrown from within the library class String during the execution of the method substring. This method was called at line 4 of method main in the class Test. It is unlikely that there is an error that causes an exception in a well established class of the JAVA library like String; more likely, the String class itself identified the error and threw the exception explicitly, so we are advised to seek the error starting at the deepest method of our own program. The calls in the stack trace are listed in reverse order of invocation, that is, the first call listed is the deepest method (where the exception occurred), while the last call listed is the shallowest method, namely main. 1Many programming languages prefer the term raises an exception and even The Java Language Specification uses this term on occasion. 17 Exceptions can be caught by writing a block of code called an exception handler that will be executed when an exception is thrown.2 Exception handlers are discussed in textbooks on the JAVA language; here we limit ourselves to explaining the exceptions that indicate programming errors. We further limit ourselves to exceptions commonly thrown by the language core; classes in the API define their own exceptions and these are explained in the API documentation. 3.1 Out of range These exceptions are the most common and are caused by attempting to access an array or string with an index that is outside the limits of the array or string. C programmers will be familiar with the difficult bugs that are caused by such errors which “smear” memory belonging to other variables; in JAVA the errors cause an exception immediately when they occur thus facilitating debugging. 3.1.1 ArrayIndexOutOfRange This exception is thrown when attempting the index an array a[i] where the index i is not within the values 0 and a.length1, inclusive. Zero-based arrays can be confusing; since the length of the array is larger than the last index, it is not unusual to write the following in a for-statement by mistake: final static int SIZE = 10; int a = new int[SIZE]; for (int i = 0; i <= SIZE; i++) // Error, <= should be < for (int i = 0; i <= a.length; i++) // Better, but still an error 3.1.2 StringIndexOutOfRange This exception is thrown by many methods of the class String if an index is not within the values 0 and s.length(), inclusive. Note that s.length() is valid and means the position just after the last character in the string. 3.2 Dereferencing null 3.2.1 NullPointerException A variable in JAVA is either of a primitive type such as int or boolean or of a reference type: an array type, the type of a class defined in the JAVA API such as String, or the type of a class that you define such as MyClass. When declaring a variable of a 2An alternate terminology is to say that an exception is handled by an exception handler. 18 reference type, you only get a variable that can hold a reference to an object of that class. At this point, attempting to access a field or method of the class will cause the exception NullPointerException to be thrown:3 public static void main(String[] args) {} MyClass my; // Can hold a reference but doesn’t yet my.m(5); // Throws an exception } Only after instantiating the class and executing the constructor do you get an object: public static void main(String[] args) {} MyClass my; // Can hold a reference but doesn’t yet my = new MyClass(); // Instantiates an object and assigns reference my.m(5); // OK } This exception is not often seen in this context because JAVA style prefers that the declaration of the variable include the instantiation as its initial value: public static void main(String[] args) {} MyClass my = new MyClass(); // Declaration + instantiation my.m(5); // OK } If the variable is declared directly within its class, you should initialize it either at its declaration or within the constructor: class YourClass { MyClass[] my; // Can’t initialize here because ... YourClass(int size) { // ... size of array different for each object my = new MyClass[size]; } } The exception is likely to occur when you declare an array whose elements are of reference type. It is easy to forget that the array contains only references and that each element must be separately initialized: MyClass[] my = new MyClass[4]; // Array of references my[1].m(5); // Raises an exception for (int i = 0; i < my.length; i++) my[i] = new MyClass(); // Instantiate objects my[1].m(5); // OK 3The name of the exception is an anachronism, because there are no (explicit) pointers in JAVA. 19 Finally, NullPointerException will occur if you get a reference as a return value from a method and don’t know or don’t check that the value is non-null:4 Node node = getNextNode(); if (node.key > this.key) ... // Error if node is null! if (node != null) { // This should be done first if (node.key > this.key) ... } 3.3 Computation The following three exceptions occur when you try to convert a string to a number and the form of the string does not match that of a number, for example "12a3". 3.3.1 InputMismatchException This exception is thrown by the class Scanner, which is a class introduced into version 5 of JAVA to simplify character-based input to programs. 3.3.2 IllegalFormatException This exception is thrown by the method format in class String that enables output using format specifiers as in the C language. 3.3.3 NumberFormatException This exception is thrown by methods declared in the numeric “wrapper” classes such as Integer and Double, in particular by the methods parseInt and parseDouble that convert from strings to the primitive numeric types. 3.3.4 ArithmeticException This exception is thrown if you attempt to divide by zero. 4You could know this if the method has been verified for a postcondition that specifies a non-null return value. 20 Important note Most computational errors do not result in the raising of an exception! Instead, the result is an artificial value called NaN, short for Not a Number. This value can even be printed: double x = Math.sqrt(1); // Does not throw an exception! System.out.println(x); Any attempt to perform further computation with NaN does not change the value. That is, if x is NaN then so is y after executing y = x+5. It follows that an output value of NaN gives no information as to the statement that first produced it. You will have to set breakpoints or use print statements to search for it. 3.4 Insufficient memory Modern computers have very large memories so you are unlikely to encounter these exceptions in routine programming. Nevertheless, they can occur as a side effect of other mistakes. 3.4.1 outOfMemoryError This exception can be thrown if you run out of memory: int a = new int[100000000]; 3.4.2 StackOverFlowArea A stack is used to store the activation record of each method that is called; it contains the parameters and the local variables as well as other information such as the return address. Unbounded recursion can cause the Java Virtual Machine to run out of space in the stack: int factorial(int n) { if (n == 0) return 1; else return n * factorial(n + 1); // Error, you meant n 1 } 21 3.5 Program execution You can run a JAVA program from within an environment or by executing the interpreter from the command line: java Test where Test is the name of a class containing a main method. Suggestion: It is convenient to write main methods in most classes and to use then for testing classes individually. After the classes are integrated into a single program, you only need ensure that the interpreter is invoked on the class that contains the “real” main method. Two runtime errors can occur if the interpreter is not successful in finding and running the program. 3.5.1 NoClassDefFoundError The interpreter must be able to find the file containing a class with the main method, for example, Test.class. If packages are not used, this must be in the directory where the interpreter is executed. Check that the name of the class is the same as the name of the file without the extension. Case is significant! Warning! If you are compiling and running JAVA from a command window or shell with a history facility, you are likely to encounter this error. First, you compile the program: javac MyClass.java and then you recall that line and erase the c from javac to obtain the command for the interpreter: java MyClass.java Unfortunately, MyClass.java is not the name of the class so you will get this exception. You must erase the .java extension as well to run the interpreter: java MyClass If you are using packages, the main class must be in a subdirectory of that name. For example, given: package project1.userinterface; class Test { public static void main(String[] args) { ... } } 22 the file Test.class must be located in the directory userinterface that is a subdirectory of project1 that is a subdirectory of the directory where the interpreter is executed: c:\projects> dir project1 c:\projects> dir project1 userinterface c:\projects> dir project1\userinterface Test.class The program is invoked by giving the fully qualified name made up of the package names and the class name: c:\projects> java project1.userinterface.Test 3.5.2 NoSuchMethodFoundError: main This error will occur if there is no method main in the class, or if the declaration is not precisely correct: the static modifier, the void return type, the method name main written in lower case, and one parameter of type String[]. If you forget the public modifier, the error message is Main method not public. 23 Chapter 4 Assignment and equality JAVA programmers make mistakes in the use of the assignment and equality operators, especially when strings are used. The concept of reference semantics is (or should be) explained in detail in your textbook, so we limit ourselves to a reminder of the potential problems. 4.1 String equality Given: String s1 = "abcdef"; String s2 = "abcdef"; String s3 = "abc" + "def"; String s4 = "abcdef" + ""; String s5 = s1 + ""; String t1 = "abc"; String t2 = "def"; String s6 = t1 + t2; all strings sn are equal when compared using the method equals in the class String that compares the contents pointed to by the reference: if (s1.equals(s5)) // Condition evaluates to true The string literal "abcdef" is stored only once, so strings s1, s2 and (perhaps surprisingly) s3 and s4 are also equal when compared using the equality operator == that compares the references themselves: if (s1 == s3) // Condition evaluates to true However, s5 and s6 are not equal (==) to s1 through s4, because their values are created at runtime and stored separately; therefore, their references are not the same as they are for the literals created at compile-time. Always use equals rather than == to compare strings, unless you can explain why the latter is needed! 24 4.2 Assignment of references The assignment operator copies references, not the contents of an object. Given: int[] a1 = { 1, 2, 3, 4, 5 }; int[] a2 = a1; a1[0] = 6; since a2 points to the same array, the value of a2[0] is also changed to 6. To copy an array, you have to write an explicit loop and copy the elements one by one. To copy an object pointed to by a reference, you can create a new object and pass the old object as a parameter to a constructor: class MyClass { int x; MyClass(int y) { x = y; } MyClass(MyClass myclass) { this.x = myclass.x; } } class Test { public static void main(String[] args) { MyClass myclass1 = new MyClass(5); MyClass myclass2 = new MyClass(myclass1); myclass1.x = 6; System.out.println(myclass1.x); // Prints 6 System.out.println(myclass2.x); // Prints 5 } } Alternatively, you can use clone as described in JAVA textbooks. 25 Chapter 5 On debugging without a debugger Debugging is perhaps best done using a debugger such as those provided by integrated development environments. Nevertheless, many programmers debug programs by inserting print statements. This section describes some of the techniques that can be used in JAVA. 5.1 Printing number data and arrays The methods System.out.print and System.out.println are predefined for primitive types as well as for strings: int i = 1; double d = 5.2; System.out.print(i); System.out.println(d); Furthermore, automatic conversion to String type is performed by the concatenation operator +: System.out.println("d = " + d + "and i = " + i); The print statements can not print an entire array, so a method must be written: public static void print(int[] a) { for (int i = 0; i < a.length; i++) System.out.print(a[i]); System.out.println(); } public static void main(String[] args) { int[] a = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10 }; print(a); } Since the number of elements of an array can be large, it is better to write the method so that it inserts a newline after printing a fixed number of elements: 26 public static void print(int[] a) { for (int i = 0; i < a.length; i++) { System.out.print(a[i]); if (i % 8 == 7) System.out.println(); } System.out.println(); } You can put this static method in a publicly accessible class and use it to print any integer array. Similar methods can be written for the other primitive types. 5.2 Converting objects to strings Within the class Object, the root class for all other classes, a method toString is declared. The default implementation will not give useful information, so it is a good idea to override it in each class that you write: class Node { int key; double value; public String toString() { return "The value at key " + key + " is " + value; } } Then, you can simply call the print statements for any object of this class and the conversion to String is done automatically: Node node = new Node(); ... System.out.println(node); The predefined class java.util.Arrays constains a lot of useful (static) methods for working with arrays, among them toString methods for arrays whose elements are of any primitive type: int[] a = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10 }; System.out.println(java.util.Arrays.toString(a)); or import java.util.Arrays; ... System.out.println(Arrays.toString(a)); You will receive a predefined representation of the array (the elements are separated by commas), so if you want an alternate representation (such as printing on multiple lines) you will have to write your own print method as we did in the previous section. 27 An array of objects of any reference type can be printed by defing a single method since any object can be converted to Object: public static void print(Object[] a) { for (int i = 0; i < a.length; i++) System.out.print(a[i]); System.out.println(); } Node[] nodes = new Node[]; ... // Create elements of the array print(nodes); or by calling the predefined method deepToString: Node[] nodes = new Node[]; ... // Create elements of the array System.out.println(java.util.Arrays.deepToString(node)); 5.3 Forcing a stack trace Suppose that you have isolated a bug to a certain method but you do not know which call of that method was responsible. You can force the interpreter to print a trace of the call stack by inserting the line: new Exception().printStackTrace(); within the method. It creates a new object of type Exception and then invokes the method printStackTrace. Since the exception is not thrown, the execution of the program proceeds with no interruption. A program can always be terminated by calling System.exit(n) for an integer n. 5.4 Leave the debug statements in the program Once you have found a bug, it is tempting to delete the print statements used for debugging, but it is better not to do so because you may need them in the future. You can comment out the statements that you don’t need, but a better solution is to declare a global constant and then use it to turn the print statements on and off: public class Global { public static boolean DEBUG = false; public static void print(int[] a) {...} public static void print(Object[] a) {...} } if (Global.DEBUG) Global.print(nodes); 28 8.2 JavaTM 2 Platform, Standard Edition 5.0: ============================================ 1 Diagnostics Tools and Options 1.1 Introduction This chapter introduces the various diagnostic and monitoring tools which can be used with J2SE 5.0. The tools described here include command line utilities, command line options, and log files. In almost all cases the command line utilities described in this chapter are either included in the Java 2 Platform Standard Edition Development Kit (JDK 5.0), or are operating system tools and utilities. Although the JDK 5.0 command line utilities are included in the JDK download, it is important to note that they can be used to diagnose issues and monitor applications that are deployed with the Java 2 Platform Standard Edition Runtime Environment 5.0 (JRE 5.0). In general, the diagnostic tools and options described in this chapter use various mechanisms to obtain the information they report. In many cases the mechanisms are specific to the virtual machine implementation (5.0 in the case of this document), operating system, and version of each. Consequently, there is some overlap of the information reported by some of the tools. This should be viewed in the context of the various problems and issues for which these tools are intended. In many cases only a subset of the tools will be applicable to an issue at a particular point in time. 1.1.1 Caveats and Other Notes Some of the command line utilities described in this chapter are experimental. The jstack, jinfo, and jmap utilities are examples of utilities that are experimental. These utilities are subject to change in future JDK releases, and may not be included in future releases. The format of log files and other output from command line utilities or options is version specific. For example, if you develop a script that relies on the format of the fatal error log (hs_err_pid.log file) then this script may cease to work as expected if the format of the log file changes in the future. Command line options that are prefixed with -XX are Java HotSpotTM Virtual Machine specific options. In general, most -XX options are unsupported, undocumented, and were originally included for the purposes of testing components of the HotSpot Virtual Machine during its development. However many -XX options are important for performance tuning and diagnostic purposes, and are therefore described in this chapter. In some cases, the command tool utilities described here are not included in the JDK release on all operating systems. For example, the jstack, jinfo, and jmap command line utilities are included in the JDK release for Solaris and Linux only. In addition to operating system specific utilities we also describe a number of diagnostic features and tools that are specific to the Solaris 10 Operating Environment. Solaris 10 has many advanced diagnostic features that are usable in production environments, and many of the native tools are capable of providing information that is specific to the Java Runtime Environment. 10 1.1.2 Post-Mortem Diagnostics A number of the options and tools described in this chapter are designed for post-mortem diagnostics. That is, if the application crashes because of an application or JRE bug, these are the options and tools that can be used to obtain additional information (either at the time of the crash or later using information from the crash dump). Tool or Option Description and Usage Fatal Error Log The fatal error log (hs_err_.log) contains a lot of information obtained at the time of the fatal error (crash). In many cases it will be the first thing to examine when a crash happens. -XX:OnError Used to specify a sequence of user-supplied scripts or commands to be executed when a fatal error (crash) occurs. For example, on Windows, it can be used to execute a command to force a crash dump – very useful on systems that do not have post-mortem debugger configured. -XX:+ShowMessageBoxOnError Used to suspend the process when a fatal error (crash) occurs. Depending on the user response it can launch the native debugger (dbx, gdb, msdev) to attach to the VM. The option is very useful in the development environment to attach the native debugger when a crash happens. jinfo (Solaris and Linux only) The jinfo utility can obtain configuration information from a core file obtained from a crash (or a core obtained using the gcore utility). jmap (Solaris and Linux only) The jmap utility can obtain memory map information, including a heap histogram, from a core file obtained from a crash (or a core obtained using the gcore utility). jstack (Solaris and Linux only) The jstack utility can obtain java and native stack information from a core file obtained from a crash (or a core obtained using the gcore utility). jdb (Solaris and Linux only) The debugger support in the JDK includes an AttachingConnector which allows jdb, and other Java Language debuggers to attach to a core file. This can be very useful when trying to understand what the application was doing at the time of the crash. Native tools Each operating system has native tools and utilities that can be used for post-mortem diagnosis. A list of native tools is provided later in this chapter. 1.1.3 Hung Processes Some of the options and tools described in this chapter can help in scenarios involving a hung or deadlocked process. Tools in the following list do not require that the application be started with any special options. 11 Tool or Option Description and Usage Ctrl-Break Handler Used to get thread dump information. It also executes a deadlock detection algorithm and will report any deadlocks detected involving synchronized code. jstack (Solaris and Linux only) The jstack utility can obtain java and native stack information from a running process even in cases where the ctrl-break handler does not respond. jdb (Solaris and Linux only) The debugger support in the JDK includes an AttachingConnector which allows jdb, and other Java Language debuggers to attach to a hung process. This can be useful when trying to understand what each thread is doing at the time of the hang/deadlock. Native tools Each operating system has native tools and utilities that can be useful in hang/deadlock scenarios. A list of native tools is provided later in this chapter. 1.1.4 Monitoring Tools The following options and tools described in this chapter are designed for monitoring running applications. Tool Description and Usage jconsole The JDK includes a Java Management Extensions (JMX)- based monitoring tool called jconsole. The tool uses the built-in JMX instrumentation in the Java Virtual Machine to provide information on performance and resource consumption of running applications. jstat The jstat utility uses the built-in instrumentation in the HotSpot VM to provide information on performance and resource consumption of running applications. The tool can be used when diagnosing performance issues, and in particular issues related to heap sizing and garbage collection. The utility does not require that the application be started with any special options as instrumentation is enabled by default. Native tools Each operating system has native tools and utilities that can be useful for monitoring purposes. The dynamic tracing (dtrace) capability on Solaris 10 can do very advanced monitoring. A list of native tools is provided later in this chapter. 1.1.5 Other Tools and Options In addition to the tools listed in the previous categories this chapter also describes a number of options and tools that can be useful to diagnose other issues : 12 Tool or Option Description and Usage HPROF Profiler The HPROF profiler is a simple profiler included in the JDK. It is capable of presenting CPU usage, heap allocation statistics and monitor contention profiles. In addition it can also report complete heap dumps and states of all the monitors and threads in the Java virtual machine. In terms of diagnosing problems, HPROF can be useful when analyzing performance, lock contention, memory leaks, and other issues. Heap Analysis Tool (HAT) The Heap Analysis Tool (HAT) is not included in JDK 5.0 but it can be downloaded from the java.net site. It is a useful tool when diagnosing unnecessary object retention (or memory leaks). It can be used to browse an object dump, view all reachable objects in the heap, and understand which references are keeping an object alive. Java Heap Analysis Tool (jhat) The jhat utility provides several improvements over HAT. See section 1.12. It is delivered with Java SE 6 but can read heap dumps created on Java SE 5.0 systems. -XX:+HeapDumpOnOutOfMemoryError Used to generate a heap dump when the VM detects an OutOfMemoryError. (Introduced in Java SE 5.0 update 7.) -XX:+HeapDumpOnCtrlBreak Used to generate a heap dump with Ctrl-Break. (Introduced in Java SE 5.0 update 14.) -Xcheck:jni The -Xcheck:jni option is useful option when trying to diagnose problems with applications that use the Java Native Interface (JNI). This option can be be useful when an application employs third-party libraries (some JDBC drivers for example). 13 1.2 jinfo The jinfo command-line utility gets configuration information from a running java process or crash dump. It is included in the Solaris and Linux releases of the JDK. It is not included in the JDK5.0 release on Windows. jinfo prints the system properties or the command line flags that were used to start the VM. Following is an example to demonstrate the output: $ jinfo 19846 Attaching to process ID 19846, please wait... Debugger attached successfully. Server compiler detected. JVM version is 1.5.0-rc-b63 Java System Properties: java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition sun.boot.library.path = /net/server/export/disk09/jdk/1.5.0/rc/b63/binaries/solsparc/jre/lib/sparc java.vm.version = 1.5.0-rc-b63 java.vm.vendor = Sun Microsystems Inc. java.vendor.url = http://java.sun.com/ path.separator = : java.vm.name = Java HotSpot(TM) Server VM file.encoding.pkg = sun.io sun.os.patch.level = unknown java.vm.specification.name = Java Virtual Machine Specification user.dir = /space/user/jakarta-tomcat-5.0.12/bin java.runtime.version = 1.5.0-rc-b63 java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment java.endorsed.dirs = /space/user/jakarta-tomcat-5.0.12/common/endorsed os.arch = sparc java.io.tmpdir = /space/user/jakarta-tomcat-5.0.12/temp line.separator = java.vm.specification.vendor = Sun Microsystems Inc. java.naming.factory.url.pkgs = org.apache.naming os.name = SunOS sun.jnu.encoding = ISO646-US java.library.path = /net/server/export/disk09/jdk/1.5.0/rc/b63/binaries/solsparc/jre/lib/sparc/server :/net/server/export/disk09/jdk/1.5.0/rc/b63/binaries/solsparc/jre/lib/sparc:/net/ server/export/disk09/jdk/1.5.0/rc/b63/binaries/solsparc/jre/../lib/sparc:/usr/lib java.specification.name = Java Platform API Specification java.class.version = 49.0 sun.management.compiler = HotSpot Server Compiler os.version = 5.10 user.home = /home/user catalina.useNaming = true user.timezone = Asia/Calcutta java.awt.printerjob = sun.print.PSPrinterJob file.encoding = ISO646-US java.specification.version = 1.5 catalina.home = /space/user/jakarta-tomcat-5.0.12 java.class.path = /net/myserver/export1/user/j2sdk1.5.0/lib/tools.jar:/space/user/jakarta-tomcat- 5.0.12/bin/bootstrap.jar 14 user.name = user java.naming.factory.initial = org.apache.naming.java.javaURLContextFactory java.vm.specification.version = 1.0 java.home = /net/server/export/disk09/jdk/1.5.0/rc/b63/binaries/solsparc/jre sun.arch.data.model = 32 user.language = en java.specification.vendor = Sun Microsystems Inc. java.vm.info = mixed mode java.version = 1.5.0-rc java.ext.dirs = /net/server/export/disk09/jdk/1.5.0/rc/b63/binaries/solsparc/jre/lib/ext sun.boot.class.path = /space/user/jakarta-tomcat- 5.0.12/common/endorsed/xercesImpl.jar:/space/user/jakarta-tomcat- 5.0.12/common/endorsed/xmlParserAPIs.jar:/net/server/export/disk09/jdk/1.5.0/rc/b 63/binaries/solsparc/jre/lib/rt.jar:/net/server/export/disk09/jdk/1.5.0/rc/b63/bi naries/solsparc/jre/lib/i18n.jar:/net/server/export/disk09/jdk/1.5.0/rc/b63/binar ies/solsparc/jre/lib/sunrsasign.jar:/net/server/export/disk09/jdk/1.5.0/rc/b63/bi naries/solsparc/jre/lib/jsse.jar:/net/server/export/disk09/jdk/1.5.0/rc/b63/binar ies/solsparc/jre/lib/jce.jar:/net/server/export/disk09/jdk/1.5.0/rc/b63/binaries/ solsparc/jre/lib/charsets.jar:/net/server/export/disk09/jdk/1.5.0/rc/b63/binaries /solsparc/jre/classes java.vendor = Sun Microsystems Inc. catalina.base = /space/user/jakarta-tomcat-5.0.12 file.separator = / java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi sun.io.unicode.encoding = UnicodeBig sun.cpu.endian = big sun.cpu.isalist = sparcv9+vis2 sparcv9+vis sparcv9 sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc VM Flags: -Djava.endorsed.dirs=/space/user/jakarta-tomcat-5.0.12/common/endorsed -Dcatalina .base=/space/user/jakarta-tomcat-5.0.12 -Dcatalina.home=/space/user/jakartatomcat- 5.0.12 -Djava.io.tmpdir=/space/user/jakarta-tomcat-5.0.12/temp The above example was based on a Jakarta Tomcat server. The “VM Flags” output shows that the server is using the endorsed override mechanism to override the implementation of some classes – this type of information is useful when, for example, an XML-related issue requires investigation. The classpath and bootclasspath output can also be very useful for debugging class loader issues. In addition to obtaining information from a process, the jinfo tool can use a core file as input. On Solaris, for example, we could use the gcore utility to get a core file of the Tomcat process in the above example. The core file will be named core.19846 and will be generated in the working directory of the process. The path to the java executable and the core file must be specified as arguments. jinfo $JAVA_HOME/bin/java core.19846 (JAVA_HOME indicates the home directory of the JDK installation.) Sometimes the binary name will not be “java”. This arises when the VM is created using the JNI invocation API. The jinfo tool requires the binary from which the core file was generated. For more information, the manual page for jinfo is available at: http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jinfo.html 15 1.3 jmap The jmap command-line utility is included in the Solaris and Linux releases of the JDK. It is not included in the JDK5.0 release on Windows. jmap prints memory related statistics for a running VM or core file. If jmap is used with a process or core file without any command line options then it prints the list of shared objects loaded (the output is similar to the Solaris pmap utility). For more specific information the -heap, -histo, or -permstat options can be used. These are described in the following sections. 1.3.1 Heap Configuration and Usage The -heap option is used to obtain java heap information including: 1. GC algorithm specific information: This includes the name of the GC algorithm (Parallel GC for example) and algorithm specific details (such as number of threads for parallel GC). 2. Heap configuration: The heap configuration may have been specified as command line options or selected by the VM based on the machine configuration. 3. Heap usage summary: For each generation it prints the total capacity, in-use and available free memory. If a generation is organized as a collection of spaces (the new generation for example), then a space-wise memory size summary is included. The following is example output from jmap -heap : $ jmap -heap 19846 Attaching to process ID 19846, please wait... Debugger attached successfully. Server compiler detected. JVM version is 1.5.0-rc-b63 using thread-local object allocation. Parallel GC with 2 thread(s) Heap Configuration: MinHeapFreeRatio = 40 MaxHeapFreeRatio = 70 MaxHeapSize = 536870912 (512.0MB) NewSize = 2228224 (2.125MB) MaxNewSize = 4294901760 (4095.9375MB) OldSize = 1441792 (1.375MB) NewRatio = 2 SurvivorRatio = 32 PermSize = 16777216 (16.0MB) MaxPermSize = 67108864 (64.0MB) Heap Usage: PS Young Generation Eden Space: capacity = 9240576 (8.8125MB) used = 9159544 (8.735221862792969MB) free = 81032 (0.07727813720703125MB) 99.12308496786348% used From Space: capacity = 2555904 (2.4375MB) 16 used = 2431992 (2.3193283081054688MB) free = 123912 (0.11817169189453125MB) 95.1519305889423% used To Space: capacity = 2686976 (2.5625MB) used = 0 (0.0MB) free = 2686976 (2.5625MB) 0.0% used PS Old Generation capacity = 25165824 (24.0MB) used = 2426464 (2.314056396484375MB) free = 22739360 (21.685943603515625MB) 9.641901652018229% used PS Perm Generation capacity = 16777216 (16.0MB) used = 9523600 (9.082412719726562MB) free = 7253616 (6.9175872802734375MB) 56.765079498291016% used 1.3.2 Heap Histogram The -histo option can be used to obtain a class-wise histogram of the heap. For each class, it prints the number of objects, memory size in bytes, and fully qualified class name. Note that internal classes in the HotSpot VM are prefixed with an “*”. The histogram is useful when trying to understand how the heap is used. To get the size of an object you need to divide the total size by the count of that object type. The following shows an example of jmap -histo output: $ jmap -histo 19846 Attaching to process ID 19846, please wait... Debugger attached successfully. Server compiler detected. JVM version is 1.5.0-rc-b63 Iterating over heap. This may take a while... Object Histogram: Size Count Class description ------------------------------------------------------- 4473488 44525 char[] 2663464 21830 * ConstMethodKlass 1575128 21830 * MethodKlass 1297600 40550 java.util.HashMap$ValueIterator 1272064 34452 * SymbolKlass 1262664 52611 java.lang.String 1129928 2142 byte[] 1042984 1761 * ConstantPoolKlass 80235240186 org.apache.catalina.Container[] 6730721535 * ConstantPoolCacheKlass 6518321761 * InstanceKlassKlass 5524564326 int[] 3482404353 java.lang.reflect.Method 3189604430 org.apache.naming.resources.FileDirContext$FileResourceAttributes 17 2861363274 java.lang.Object[] 2321205815 java.lang.String[] 2178009075 java.util.HashMap$Entry 2020002005 java.util.HashMap$Entry[] 1760962393 short[] 1747681986 java.lang.Class 142808495 * MethodDataKlass 1393842771 java.lang.Object[] 1070246689 java.io.File 81336 3389 java.util.Hashtable$Entry 79080 1977 java.util.HashMap 70560 4410 java.lang.StringBuilder 66600 875 java.util.Hashtable$Entry[] 63400 3733 java.lang.Class[] 60032 1876 java.util.LinkedHashMap$Entry 56448 196 * ObjArrayKlassKlass 49608 2067 java.util.ArrayList 44832 1401 java.lang.ref.SoftReference 41408 1294 org.apache.xerces.dom.DeferredAttrImpl 38232 1593 java.lang.ref.WeakReference 37104 1546 java.io.ExpiringCache$Entry 35520 555 org.apache.commons.modeler.AttributeInfo 35008 2188 javax.management.modelmbean.DescriptorSupport$CaseIgnoreString 33880 847 java.util.Hashtable 31344 653 java.beans.MethodDescriptor 23160 222 java.lang.reflect.Method[] 22976 359 java.lang.reflect.Constructor 19952 325 javax.management.modelmbean.ModelMBeanAttributeInfo[] 19416 809 org.apache.xerces.xni.QName 18336 382 org.apache.xerces.dom.DeferredElementImpl 17280 720 java.util.Vector 17264 83 org.apache.catalina.core.StandardWrapper 16744 299 java.nio.DirectByteBuffer 14472 603 javax.management.ObjectName$Property 14400 450 org.apache.xerces.dom.DeferredTextImpl 13376 209 java.beans.PropertyDescriptor 11960 299 sun.misc.Cleaner [... more lines removed here to reduce output ...] 8 1 sun.reflect.GeneratedMethodAccessor31 Heap traversal tool 7.12 seconds. 1.3.3 Getting Information on the Permanent Generation The permanent generation is the area of heap that holds all the reflective data of the virtual machine itself, such as class and method objects (also called “method area” in The Java Virtual Machine Specification). Configuring the size of the permanent generation can be important for applications that dynamically generate and load a very large number of classes (Java Server Pages/web containers for example). If an application loads “too many” classes then it is possible it will abort with an OutOfMemoryError. The specific error is: “Exception in thread XXXX java.lang.OutOfMemoryError: PermGen space” (See section 2.1.1 for a description of this and other reasons for OutOfMemoryError.) 18 To get further information about the permanent generation, the -permstat option can be used. It prints statistics for the objects in the permanent generation. Here is a sample of the output: $ jmap -permstat 19846 Attaching to process ID 19846, please wait... Debugger attached successfully. Server compiler detected. JVM version is 1.5.0-rc-b63 finding class loader instances .. done. computing per loader stat ..done. please wait.. computing liveness..........................................................done. class_loader classes bytes parent_loader alive? type 1189 2727472 null live 0xee431d58 1 1392 0xee22b3d0 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee3fbd08 1 1400 0xee227418 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee3fb860 1 1400 0xee227ba0 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee3fc330 1 1400 0xee227418 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee3fc4f8 1 1400 0xee227418 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee431578 1 1400 0xee227418 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee431198 1 1400 null dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee431f68 1 1400 0xee22b3d0 dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee3fb4b0 1 848 null dead sun/reflect/DelegatingClassLoader@0xd4042360 0xee3fc628 1 1392 0xee227418 dead sun/reflect/DelegatingClassLoader@0xd4042360 [.. more lines removed here to reduce output...] total = 65 2303 5900688 N/A alive=11, dead=54 N/A For each class loader object, the following details are printed: 1. The address of the class loader object – at the snapshot when the utility was run. 2. The number of classes loaded (defined by this loader with the method java.lang.ClassLoader.defineClass). 3. The approximate number of bytes consumed by meta-data for all classes loaded by this class loader. 4. The address of the parent class loader (if any). 5. A “live” or “dead” indication – indicates whether the loader object will be garbage collected in the future. 6. The class name of this class loader. For more information, refer to the jmap manual page at: http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.info 19 1.4 jstack The jstack command-line utility is included in the Solaris and Linux releases of the JDK. It is not included in the JDK5.0 release on Windows. The utility attaches to the specified process (or core file) and prints the stack traces of all threads that are attached to the virtual machine (this includes Java threads and VM internal threads). A stack trace of all threads can be useful when trying to diagnose a number of issues such as deadlocks or hangs. In many cases a thread dump can be obtained by pressing Ctrl-\ at the application console (standard input) or by sending the process a QUIT signal (section 1.16). Thread dumps can also be obtained programmatically using the Thread.getAllStackTraces method, or in the debugger using the debugger option to print all thread stacks (the “where” command in the case of the jdb sample debugger). In these examples the VM process must be in a state where it can execute code. In rare cases (for example if you encounter a bug in the thread library or HotSpot VM) this may not be possible, but it may be possible with the jstack utility as it attaches to the process using an operating system interface. Here is example output from the jstack command to demonstrate how the output looks : $ jstack 7034 Debugger attached successfully. Server compiler detected. JVM version is 1.5.0-rc-b63 Thread t@44: (state = BLOCKED) - java.lang.Object.wait(long) (Interpreted frame) - java.lang.Object.wait(long) (Interpreted frame) - org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run() @bci=8, line=549 (Interpreted frame) - java.lang.Thread.run() @bci=11, line=595 (Interpreted frame) Thread t@43: (state = IN_NATIVE) - java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl) (Interpreted frame) - java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl) (Interpreted frame) - java.net.PlainSocketImpl.accept(java.net.SocketImpl) @bci=7, line=384 (Interpreted frame) - java.net.ServerSocket.implAccept(java.net.Socket) @bci=50, line=450 (Interpreted frame) - java.net.ServerSocket.accept() @bci=48, line=421 (Interpreted frame) - org.apache.jk.common.ChannelSocket.accept(org.apache.jk.core.MsgContext) @bci=12, line=278 (Interpreted frame) - org.apache.jk.common.ChannelSocket.acceptConnections() @bci=71, line=572 (Interpreted frame) - org.apache.jk.common.SocketAcceptor.runIt(java.lang.Object[]) @bci=4, line=758 (Interpreted frame) - org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run() @bci=174, line=666 (Interpreted frame) - java.lang.Thread.run() @bci=11, line=595 (Interpreted frame) Thread t@42: (state = BLOCKED) - java.lang.Object.wait(long) (Interpreted frame) - java.lang.Object.wait(long) (Interpreted frame) 20 - java.lang.Object.wait() @bci=2, line=474 (Interpreted frame) - org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run() @bci=19, line=642 (Interpreted frame) - java.lang.Thread.run() @bci=11, line=595 (Interpreted frame) Thread t@41: (state = BLOCKED) - java.lang.Object.wait(long) (Interpreted frame) - java.lang.Object.wait(long) (Interpreted frame) - java.lang.Object.wait() @bci=2, line=474 (Interpreted frame) - org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run() @bci=19, line=642 (Interpreted frame) - java.lang.Thread.run() @bci=11, line=595 (Interpreted frame) [... more lines removed here to reduce output ...] The jstack utility can also try to obtain stack traces from a core dump: jstack $JAVA_HOME/bin/java core (JAVA_HOME indicates the JDK installation directory.) For each thread, it prints the thread identifier (an integer) and the thread state. The following are the possible thread states that can be printed: UNINTIALIZED Thread is not created. This will normally not happen (unless there is a serious bug such as memory corruption). NEW Thread has been created but it has not started running yet. IN_NATIVE Thread is running native code. IN_VM Thread is running VM code. IN_JAVA Thread is running (either interpreted or compiled) Java code. BLOCKED Thread is blocked. ..._TRANS If you see any of the above states but followed by "_TRANS", it means the thread is changing to a different state. These are the thread states as of JDK5.0 – future releases may include new or different states. After the thread information, there is a line of output for each java stack frame formatted as follows: java.lang.Thread.run() @bci=11, line=595 (Interpreted frame) | | | | | | | | | +-- Method compiled/interpreted? | | | +-------------- Source line number | | +----------------------- Byte code index | +------------------------------ Method name +----------------------------------------------- Fully qualified class name 21 The bci and line are not printed for JNI/native methods. If a method accepts arguments, then the argument types are printed (as shown below) so that overloaded methods can be differentiated. org.apache.jk.common.SocketAcceptor.runIt(java.lang.Object[]) @bci=4, line=758 (Interpreted frame) The jstack utility may also be used to print a mixed stack. That is, it can print native stack frames in addition to the java stack. Native frames are the C/C++ frames associated with VM code, and JNI/native code. To print a mixed stack the -m option is used. An output example follows: $ jstack -m 7034 Debugger attached successfully. Server compiler detected. JVM version is 1.5.0-rc-b63 ----------------- t@1 ----------------- 0xff32cf84 _so_accept + 0x4 0xfa8db248 Java_java_net_PlainSocketImpl_socketAccept + 0x200 0xf880c280 * java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl) bci:7852 (Interpreted frame) 0xf880c224 * java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl) bci:0 (Interpreted frame) 0xf8805764 * java.net.PlainSocketImpl.accept(java.net.SocketImpl) bci:7 line:384 (Interpreted frame) 0xf8805764 * java.net.ServerSocket.implAccept(java.net.Socket) bci:50 line:450 (Interpreted frame) 0xf8805764 * java.net.ServerSocket.accept() bci:48 line:421 (Interpreted frame) 0xf8805874 * org.apache.catalina.core.StandardServer.await() bci:74 line:552 (Interpreted frame) 0xf8805c2c * org.apache.catalina.startup.Catalina.await() bci:4 line:634 (Interpreted frame) 0xf8805764 * org.apache.catalina.startup.Catalina.start() bci:113 line:596 (Interpreted frame) 0xf8800218 0xfe98dfd8 void JavaCalls::call_helper(JavaValue*,methodHandle*,JavaCallArguments*,Thread*) + 0x528 0xfea25954 oopDesc*Reflection::invoke(instanceKlassHandle,methodHandle,Handle,int,objArrayHandle,Bas icType,objArrayHandle,int,Thread*) + 0x14a8 0xfeaeac9c oopDesc*Reflection::invoke_method(oopDesc*,Handle,objArrayHandle,Thread*) + 0x268 0xfeae8ca8 JVM_InvokeMethod + 0x234 0xfe7a0314 Java_sun_reflect_NativeMethodAccessorImpl_invoke0 + 0x10 method entry point (kind = native) 0xf880c224 * sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) bci:0 (Interpreted frame) 0xf8805874 * sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) bci:87 line:39 (Interpreted frame) 0xf8805874 * sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) bci:6 line:25 (Interpreted frame) 0xf8805d3c * java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) bci:111 line:585 (Interpreted frame) 0xf8805874 * org.apache.catalina.startup.Bootstrap.start() bci:31 line:295 (Interpreted frame) 0xf8805764 * org.apache.catalina.startup.Bootstrap.main(java.lang.String[]) bci:114 line:392 (Interpreted frame) 0xf8800218 0xfe98dfd8 void JavaCalls::call_helper(JavaValue*,methodHandle*,JavaCallArguments*,Thread*) + 0x528 0xfeac8160 jni_CallStaticVoidMethod + 0x46c 22 0x000123b4 main + 0x1314 0x00011088 _start + 0x108 [... more thread stacks removed here to reduce output ...] Note that the output in the previous example was obtained using the following command (where JAVA_HOME indicates the JDK installation directory): jstack -m $JAVA_HOME/bin/java core | c++filt Frames prefixed with '*' are Java frames, and others are native C/C++ frames. The output of the utility was piped through c++filt to demangle C++ mangled symbol names. The HotSpot Virtual Mahcine is developed in the C++ Language so jstack prints C++ mangled symbol names for the HotSpot internal functions. For more information, the manual page for jstack is available at: http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html 23 1.5 jconsole J2SE 5.0 has comprehensive monitoring and management support. Among the tools included in the JDK download is a Java Management Extensions (JMX)-compliant monitoring tool called jconsole. The tool uses the built-in JMX instrumentation in the Java Virtual Machine to provide information on performance and resource consumption of running applications. Although the tool is included in the JDK download it can also be used to monitor and manage applications deployed with the Java 2 Platform Standard Edition Runtime Environment 5.0 (JRE 5.0). jconsole can attach to any application that is started with the JMX agent. A system property defined on the command line enables the JMX agent. Once attached jconsole can be used to display useful information such as thread usage, memory consumption, and details about class loading, runtime compilation, and the operating system. Following is an overview of the information that can be monitored using jconsole. Each heading corresponds to a tab pane in the monitoring tool: Summary • Uptime: how long the JVM has been running • Total compile time: the amount of time spent in runtime compilation • Process CPU time: the total amount of CPU time consumed by the JVM Memory • Current heap size: Number of Kbytes currently occupied by the heap • Committed memory: Total amount of memory allocated for use by the heap • Maximum heap size: Maximum number of Kbytes occupied by the heap • Objects pending for finalization: Number of objects pending for finalization • Garbage collector information: Information on GC, including the garbage collector names, number of collections performed, and total time spent performing GC Threads • Live threads: Current number of live daemon threads plus non-daemon threads • Peak: Highest number of live threads since JVM started • Daemon threads: Current number of live daemon threads • Total started: Total number of threads started since the JVM started (including daemon, nondaemon, and terminated) Classes • Current classes loaded: Number of classes currently loaded into memory • Total classes loaded: Total number of classes loaded into memory since the JVM started, including those subsequently unloaded • Total classes unloaded: Number of classes unloaded from memory since the JVM started Operating System • Total physical memory: Amount of random-access memory (RAM) that the machine has. • Free physical memory: Amount of free RAM the machine has. • Committed virtual memory: Amount of virtual memory guaranteed to be available to the running process. 24 In addition to monitoring, jconsole can be used to dynamically change several parameters in the running system. For example, the setting of the -verbose:gc option can be changed so that garbage collection trace output can be dynamically enabled or disabled for a running application. A complete tutorial on the jconsole tool is beyond the scope of this document. However getting started with jconsole is straight-forward : 1. Start the application with the -Dcom.sun.management.jmxremote option. This option sets the com.sun.management.jmxremote system property which enabled the JMX agent. 2. Start jconsole with the jconsole command. Jconsole ships as a binary in the $JAVA_HOME/bin directory. (JAVA_HOME indicates the home directory of the J2SE installation.) 3. When jconsole starts, it shows a window with the list of managed VMs on the machine. The process-id (pid) and command line arguments for each VM are printed. Select a VM, and jconsole will attach to it. As an example of the output of the monitoring tool, following is a sample screen-shot showing a chart of heap memory usage: 25 In summary, jconsole can be useful in providing high-level diagnosis on problems such as memory leaks, excessive class loading or running threads. It can also be useful when tuning or heap sizing. jconsole can also be used to view more detailed information about the running application. For example, it can examine the stack traces of running threads, if the application has additional instrumentation. The following documents describe in more detail the monitoring and management capabilities, and how to use jconsole: Monitoring and Management for the Java Platform : http://java.sun.com/j2se/1.5.0/docs/guide/management/index.html Monitoring and Management Using JMX : http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html Using jconsole : http://java.sun.com/j2se/1.5.0/docs/guide/management/jconsole.html 26 1.6 jps The jps utility lists the instrumented HotSpot Virtual Machines on the target system. The utility is very useful in environments where the VM is embedded (meaning it is started using the JNI Invocation API rather than the java launcher). In these environments it is not always easy to recognize the java processes in the process list. The following example demonstrates its usage : $ jps 16217 MyApplication 16342 jps The utility lists the virtual machines for which the user has access rights. This is determined by operating system specific access control mechanisms. On Solaris, for example, if a non-root user executes the jps utility then it lists the virtual machines that were started with that user's uid. In addition to listing the process id the utility provides options to output the arguments passed to the application's main method, the complete list of VM arguments, and the full package name of the application's main class. jps can also list processes on a remote system if the remote system is running the jstat daemon (jstatd). The documentation for the utility can be found here : http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jps.html The document includes examples that obtain the process status from a remote host. The utility is included in the JDK download for all operating system platforms supported by Sun. However, the HotSpot instrumentation is not accessible on Windows 98 or Windows ME. In addition the instrumentation may not be accessible on Windows if the temporary directory is on a FAT32 file system1. 1 Workarounds to this issue can be found in the FAQ at http://developers.sun.com/dev/coolstuff/jvmstat/faq.html 27 1.7 jstat The jstat utility uses the built-in instrumentation in the HotSpot VM to provide information on performance and resource consumption of running applications. The tool can be used when diagnosing performance issues, and in particular issues related to heap sizing and garbage collection. The jstat utility does not require the VM to be started with any special options. The built-in instrumentation in the HotSpot VM is enabled by default. The utility is included in the JDK download for all operating system platforms supported by Sun. However, the instrumentation is not accessible on Windows 98 or Windows ME2. Following are the jstat utility options : • -class – prints statistics on the behavior of the class loader. • -compiler – prints statistics of the behavior of the HotSpot compiler. • -gc – prints statistics of the behavior of the garbage collected heap. • -gccapacity – prints statistics of the capacities of the generations and their corresponding spaces. • -gccause – prints the summary of garbage collection statistics (same as -gcutil), with the cause of the last and current (if applicable) garbage collection events. • -gcnew – prints statistics of the behavior of the new generation. • -gcnewcapacity - prints statistics of the sizes of the new generations and its corresponding spaces. • -gcold – prints statistics of the behavior of the old and permanent generations. • -gcoldcapacity – prints statistics of the sizes of the old generation. • -gcpermcapacity – print statistics of the sizes of the permanent generation. • -gcutil – prints a summary of garbage collection statistics. • -printcompilation – prints HotSpot compilation method statistics. The jstat tool documentation provides a complete description of the tool : http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstat.html The documentation includes a number of examples. A few of these examples are repeated here. The jstat utility uses a vmid to identify the target process. The documentation describes the syntax of a vmid but in the simplest case a vmid can be a local virtual machine identifier. In the case of Solaris, Linux, and Windows, it can be considered to be the process id. (This is typical but may not always be the case.) Here is an example of the -gcutil option. The example attaches to lvmid 21891 and takes 7 samples 2 Instrumentation is also not accessible on Windows NT, 2000, or XP if a FAT32 file system is used. 28 at 250 millisecond intervals and displays the output as specified by the -gcutil option. jstat -gcutil 21891 250 7 S0 S1 E O P YGC YGCT FGC FGCT GCT 12.44 0.00 27.20 9.49 96.70 78 0.176 5 0.495 0.672 12.44 0.00 62.16 9.49 96.70 78 0.176 5 0.495 0.672 12.44 0.00 83.97 9.49 96.70 78 0.176 5 0.495 0.672 0.00 7.74 0.00 9.51 96.70 79 0.177 5 0.495 0.673 0.00 7.74 23.37 9.51 96.70 79 0.177 5 0.495 0.673 0.00 7.74 43.82 9.51 96.70 79 0.177 5 0.495 0.673 0.00 7.74 58.11 9.51 96.71 79 0.177 5 0.495 0.673 The output of this example shows that a young generation collection occurred between the 3rd and 4th sample. The collection took 0.001 seconds and promoted objects from the eden space (E) to the old space (O), resulting in an increase of old space utilization from 9.49% to 9.51%. Before the collection, the survivor space was 12.44% utilized, but after this collection it is only 7.74% utilized. The following example attaches to lvmid 21891 and takes samples at 250 millisecond intervals and displays the output as specified by the -gcutil option. In addition, it uses the -h3 option to output the column header after every 3 lines of data. jstat -gcnew -h3 21891 250 S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT 64.0 64.0 0.0 31.7 31 31 32.0 512.0 178.6 249 0.203 64.0 64.0 0.0 31.7 31 31 32.0 512.0 355.5 249 0.203 64.0 64.0 35.4 0.0 2 31 32.0 512.0 21.9 250 0.204 S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT 64.0 64.0 35.4 0.0 2 31 32.0 512.0 245.9 250 0.204 64.0 64.0 35.4 0.0 2 31 32.0 512.0 421.1 250 0.204 64.0 64.0 0.0 19.0 31 31 32.0 512.0 84.4 251 0.204 S0C S1C S0U S1U TT MTT DSS EC EU YGC YGCT 64.0 64.0 0.0 19.0 31 31 32.0 512.0 306.7 251 0.204 In addition to showing the repeating header string, this example shows that between the 2nd and 3rd samples, a young GC occurred. Its duration was 0.001 seconds. The collection found enough live data that the survivor space 0 utilization (S0U) would have exceeded the Desired Survivor Size (DSS). As a result, objects were promoted to the old generation (not visible in this output), and the tenuring threshold (TT) was lowered from 31 to 2. Another collection occurs between the 5th and 6th samples. This collection found very few survivors and returned the tenuring threshold to 31. This example attaches to lvmid 21891 and takes 3 samples at 250 millisecond intervals. The -t option is used to generate a time stamp for each sample in the first column. A small font is used here so that the output doesn't wrap. jstat -gcoldcapacity -t 21891 250 3 Timestamp OGCMN OGCMX OGC OC YGC FGC FGCT GCT 150.1 1408.0 60544.0 11696.0 11696.0 194 80 2.874 3.799 150.4 1408.0 60544.0 13820.0 13820.0 194 81 2.938 3.863 150.7 1408.0 60544.0 13820.0 13820.0 194 81 2.938 3.863 The Timestamp column reports the elapsed time in seconds since the start of the target JVM. In 29 addition, the -gcoldcapacity output shows the old generation capacity (OGC) and the old space capacity (OC) increasing as the heap expands to meet allocation and/or promotion demands. The old generation capacity (OGC) has grown from 11696 KB to 13820 KB after the 81st Full GC (FGC). The maximum capacity of the generation (and space) is 60544 KB (OGCMX), so it still has room to expand. 1.7.1 visualgc A related tool to jstat is the visualgc tool. The visualgc tool provides a graphical view of the garbage collection system. As with jstat it uses the built-in instrumentation of the HotSpot VM. The visualgc tool is not included in JDK5.0 but is available as a separate download from this site : -http://developers.sun.com/dev/coolstuff/jvmstat/index.html Following is a sample screen-shot to demonstrate how the GC and heap are visualized : 30 1.8 HPROF - Heap Profiler HPROF is a simple profiler agent shipped with JDK 5.0. It is a dynamically-linked library that interfaces to the VM using the Java Virtual Machine Tools Interface (JVM TI). It writes out profiling information either to a file or to a socket in ASCII or binary format. This information can be further processed by a profiler front-end tool. HPROF is capable of presenting CPU usage, heap allocation statistics and monitor contention profiles. In addition it can also report complete heap dumps and states of all the monitors and threads in the Java virtual machine. In terms of diagnosing problems, HPROF is useful when analyzing performance, lock contention, memory leaks, and other issues. In addition to the HPROF library the JDK also includes the source to HPROF as a JVM TI demonstration code. It can be found in the $JAVA_HOME/demo/jvmti/hprof directory (where $JAVA_HOME indicates the directory where the JDK is installed). HPROF is invoked as follows : java -agentlib:hprof Depending on the type of profiling requested, HPROF instructs the virtual machine to send it the relevant events and processes the event data into profiling information. For example, the following command obtains the heap allocation profile: java -agentlib:hprof=heap=sites ToBeProfiledClass The complete list of options is printed if the HPROF agent is provided with the help option: $ java -agentlib:hprof=help HPROF: Heap and CPU Profiling Agent (JVMTI Demonstration Code) hprof usage: java -agentlib:hprof=[help]|[