I am getting occasional failure when looking up an EJB stateless session bean
from a stand alone client app. I am using glassfish 2.1.1. This happens
about once a day, the server log shows
#|2011-12-16T11:17:22.558+0000|WARNING|sun-appserver2.1|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=17;_ThreadName=p:
thread-pool-1; w:
84;6000;7280;;_RequestID=654e3872-0338-458e-b3b9-e9fbb0439b84;|"IOP00410225:
(COMM_FAILURE) Write of message exceeded TCP timeout : max wait time = 6,000
ms, total time spent blocked, waiting to write = 7,280 ms."
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 225 completed: No
and the client log shows
[ERROR][20 Dec 2011 10:46:55][ClientThread.java:257][run] - [Thread ID
1280] Exception javax.ejb.EJBException: nested exception is:
java.rmi.MarshalException: CORBA COMM_FAILURE 1398079707 Maybe; nested
exception is:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 219 completed:
Maybe
Restarting the client fixes the problem. Have you any ideas on what would
cause this, or how we could recover without doing a manual restart of the
client.
Thanks
--
View this message in context: http://old.nabble.com/EJB-look-up-failing-occsasionally-tp33024602p33024602.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.