I'm having problems accessing ejbs through rmi/iiop in the latest night
build. The server.log seems to indicate a class loading problem:
[#|2009-08-18T10:54:55.454-0700|WARNING|glassfish|com.sun.enterprise.naming|_Thr
eadID=32;_ThreadName=Thread-2;|Failed to load
com.sun.jndi.cosnaming.CNCtxFactor
y using thread context class loader 111.0|#]
On the driver side, the error looks like this:
Aug 18, 2009 11:28:13 AM
com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoo
mImpl waitForResponse
WARNING: "IOP00410219: (COMM_FAILURE) Communications timeout waiting for
respons
e. Exceeded 1,800,000 milliseconds"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 219 completed: Maybe
at
com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTi
meoutWaitingForResponse(ORBUtilSystemException.java:3237)
at
com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTi
meoutWaitingForResponse(ORBUtilSystemException.java:3252)
at
com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl.waitForR
esponse(CorbaResponseWaitingRoomImpl.java:198)
at
com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.waitFor
Response(SocketOrChannelConnectionImpl.java:1154)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.waitForRespon
se(CorbaMessageMediatorImpl.java:291)
at
com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marsh
alingComplete1(CorbaClientRequestDispatcherImpl.java:386)
Is this a known issue?
Thanks,
Eileen