Hello everyone,
My client system connects to remote server to call a business method. Client initial context lookup works normally just fine. Problem starts after connection with server is lost and has been reestablished. During connection loss remote call fails and throws exception back to application (this is good and expected).
But after connection is established, initial context lookup() is simply logging an exception (pasted below) but not throwing back to application. so application just continuing normally and thinking that remote call performed successfully. But in reality server never gets the method call. So CORBA is eating up the error and not throwing back to application. The only way to fix this problem is by restarting the client application.
Anyone came across this issue? found reason or remedy? Any suggestions from gurus? Here is the stack trace.
Jan 22, 2009 5:55:44 PM com.sun.enterprise.naming.SerialContext lookup
SEVERE: NAM0004: Exception during name lookup : {0}
java.rmi.MarshalException: CORBA COMM_FAILURE 1398079696 Maybe; nested exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 208 completed: Maybe
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:271)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:205)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)
at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)
at com.sun.enterprise.naming._SerialContextProvider_DynamicStub.lookup(com/sun/enterprise/naming/_SerialContextProvider_DynamicStub.java)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
[Message sent by forum member 'tsnaveen' (tsnaveen)]
http://forums.java.net/jive/thread.jspa?messageID=327863