Discussions

General J2EE: java.io.EOFException: Attempt to send message on closed socket

  1. I am getting the following error if a transaction takes longer time to respond. Please let me know if anyone knows the solution. Environment: weblogic 8.1 server, client: Swing invokes EJB in the server through RMI. ---------------------- Server error log: --------------------- <Failed to send exception class java.rmi.RemoteException: java.rmi.MarshalException: IOException while sending; nested exception is: java.io.EOFException: Attempt to send message on closed socket. java.rmi.MarshalException: IOException while sending; nested exception is: java.io.EOFException: Attempt to send message on closed socket at weblogic.iiop.EndPointImpl.send(EndPointImpl.java:1112) at weblogic.iiop.OutboundResponseImpl.sendThrowable(OutboundResponseImpl.java:200) at weblogic.rmi.internal.BasicServerRef.handleThrowable(BasicServerRef.java:594) at weblogic.rmi.internal.BasicServerRef.postInvoke(BasicServerRef.java:549) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:435) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: java.io.EOFException: Attempt to send message on closed socket at weblogic.iiop.MuxableSocketIIOP.sendMsg(MuxableSocketIIOP.java:364) at weblogic.protocol.AsyncMessageSender.sendOutMsg(AsyncMessageSender.java:76) at weblogic.protocol.AsyncMessageSender.send(AsyncMessageSender.java:32) at weblogic.iiop.EndPointImpl.send(EndPointImpl.java:1106) -------------------------------- Client side error: ------------------------- java.rmi.MarshalException: CORBA COMM_FAILURE 1398079697 No; nested exception is: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 209 completed: No at com.sun.corba.se.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:92) at javax.rmi.CORBA.Util.mapSystemException(Util.java:65) -shankar
  2. Try to increment socket connection timeout. In console: click server, then protocols tab, then general subtab, then in advanced options try to increment Idle Connection Timeout parameter. Maybe it could help.