NotSerializableException accessing EJB 3 remotely

Question

Hello everyone, thanks for reading...
I have an EJB3.0 application that runs on a OC4J 10.1.3.3
I have a remote client that needs of the ejb application services.
When the client tries to access the remote ejb services I get the : java.io.NotSerializableException, It's kinda odd because the class that is supposed to be Not Serrializable it's the Oracle's XML parser (oracle.xml.parser.v2.XMLError.)
Here's the first part of the stacktrace:
com.evermind.reflect.UndeclaredExceptionTypeException: oracle.oc4j.rmi.OracleRemoteException
     at __Proxy1.getUser(Unknown Source)
     at test.appclient.client.UserServiceEJBClient.main(UserServiceEJBClient.java:55)
oracle.oc4j.rmi.OracleRemoteException: Invocation error: java.rmi.UnmarshalException: Error deserializing exception-value: writing aborted; java.io.NotSerializableException: oracle.xml.parser.v2.XMLError; nested exception is:
     java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: oracle.xml.parser.v2.XMLError
     at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:142)
     at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
     at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
     at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
     at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
     at __Proxy1.getUser(Unknown Source)
     at test.appclient.client.UserServiceEJBClient.main(UserServiceEJBClient.java:55)
     Nested exception is:
java.rmi.UnmarshalException: Error deserializing exception-value: writing aborted; java.io.NotSerializableException: oracle.xml.parser.v2.XMLError; nested exception is:
     java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: oracle.xml.parser.v2.XMLError
     at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:110)
     at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
     at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
     at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
     at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
     at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
     at __Proxy1.getUser(Unknown Source)
Here's the client code:
Properties props = new Properties();
// Standalone OC4J connection details
props.put( Context.INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory" );
props.put( Context.SECURITY_PRINCIPAL, getUserContext().getUserCode() );
props.put( Context.SECURITY_CREDENTIALS, getUserContext().getUserCredentials() );
props.put(Context.PROVIDER_URL, "ormi://serverxxx:23791/UserServiceEjb");
try {
     InitialContext context = new InitialContext(props);
     UserService service = (UserService) context.lookup("UserServiceEJB");
     if (service!=null) {
          UserTO usr = service.getUser("root");
          System.out.println(usr);
} catch (InvalidDatabaseOperationException e) {
     e.printStackTrace();
} catch (ServiceException e) {
     e.printStackTrace();
} catch (NamingException e) {
     e.printStackTrace();
}catch (Exception e) {
     e.printStackTrace();
It's really weird the oracle.xml.parser.v2.XMLError thing, because it looks like the EJB is sending that exception...
Any hints would be very appreciated...
Thanks in advise...

Answer 1

Problem solved people.
OC4J includes in the classpath of all the deployed applications some inherited libraries like xmlparserv2.
xmlparsev2's XmlError exception doesn't seems to be Serializable.
So how did we solved the problem?
At deploy time we edited the classpath for the application and excluded the xml parser library. Now it finallly works.
Thanks to everyone.
Thanks jferman.