Most of the error messages issued by the client are of limited use if the
problem is actually in CICS®, but you can sometimes get useful information from
the client, and it is an obvious place to start. Some of the more useful client
exceptions are as follows:
- NoClassDefFoundException and ClassNotFoundException
- If the client issues either of these, there is probably something missing
or corrupt on your client-side classpath. The exception should give you a
good indication of which class is missing, and from this you may be able to
work out which JAR to add to the classpath. Remember that you need j2ee.jar,
and the fully deployed jar in the classpath. It is unlikely that CICS will
issue any useful additional information for these problems.
- NoClassDefFoundError:javax/ejb/HomeHandle
- This indicates that a client application does not have EJB 1.1 level classes
available on the classpath. Ensure that j2ee.jar is available.
- ObjectNotFoundException
- This exception can indicate that a session bean has timed out or that
an attempt has been made to use the session bean in two or more concurrent
transactions.
- RemoteException
- This indicates a problem in the server application and often contains
a nested exception giving more information. These include:
- NoClassDefFoundError
- This points to a missing JAR file on the server side. Check the CICS system
console and the JVM standard error and output files for additional information.
- CORBA.INTERNAL
- This indicates a failure in the server side application outside the JVM
(for example, in a COBOL program called by an enterprise bean). Check the
CICS system console for more information.