Application client log error indicates missing JAR file
The following error message appears in the client log file because a Java
archive (JAR) file is missing from the classpath on the client machine. The
Object Request Broker (ORB) needs this file to unmarshal the nested exception
that is part of the EJB exception, returned by the server to the client application.
For example, if the EJB returns a DB2® JCC SQL exception nested inside of
the EJB exception that it returns to the client, the ORB is not able to unmarshal
the nested exception if the db2jcc.jar file that contains the DB2 SQL exception
is not in the client classpath.
java.rmi.MarshalException: CORBA MARSHAL 0x4942f89a No; nested exception is: org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Custom marshaling (4) Sender's class does not match local class vmcid: 0x4942f000 minor code: 2202 completed: No*
To avoid this error, include the JAR file that contains the class for the nested exception that is returned in the EJB exception.