peer gone exception

[c l]

When I trid to connect the server from a client, which will require server do some
time-consuming or cpu-consuming operation, I always got such exception.

prompts in client side:

Connected successfully using http to localhost/127.0.0.1:7001
java.rmi.RemoteException: ; nested exception is:
weblogic.rjvm.PeerGoneException: no message was received for 240 seconds
weblogic.rjvm.PeerGoneException: no message was received for 240 seconds
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at com.ffusion.alert.adminEJB.AEAlertAdminBeanEOImpl_WLStub.init(AEAlertAdminBeanE
OImpl_WLStub.java:2211)
at com.ffusion.alert.adminEJB.AEAlertAdminBeanEOImpl_ServiceStub.init(AEAlertAdmin
BeanEOImpl_ServiceStub.java:1603)
at EndToEnd.run(EndToEnd.java:98)
at EndToEndEJB.main(EndToEndEJB.java:27)
Connected successfully using http to localhost/127.0.0.1:7001
com.ffusion.alert.interfaces.AEException: The Universal Alert Engine has not yet
been init
ialized.
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at com.ffusion.alert.adminEJB.AEAlertAdminBeanEOImpl_WLStub.shutdown(AEAlertAdminB
eanEOImpl_WLStub.java:2473)
at com.ffusion.alert.adminEJB.AEAlertAdminBeanEOImpl_ServiceStub.shutdown(AEAlertA
dminBeanEOImpl_ServiceStub.java:1880)
at EndToEnd.run(EndToEnd.java:256)
at EndToEndEJB.main(EndToEndEJB.java:27)

prompts server side:

Fri Jul 13 10:49:44 EDT 2001:<I> <TX> Transaction (TxC (1366395200, xid = 995035
453906_1, timeout = 300, txState = Marked Rollback, root = null) rolled back aft
er 300 sec.
Fri Jul 13 10:50:00 EDT 2001:<I> <EJB JAR deployment d:\aeinstall\engine\weblogi
c\UAEAdminEJB10.jar> Exception during commit of transaction: '995035453906_1'
javax.transaction.RollbackException: Transaction TxC (1366395200, xid = 99503545
3906_1, timeout = 0, txState = Rolledback, root = null has been rolled back.Reas
on: Transaction (TxC (1366395200, xid = 995035453906_1, timeout = 300, txState
=
Marked Rollback, root = null) rolled back after 300 sec.
at weblogic.jts.internal.CoordinatorImpl.throwRollbackException(Coordina
torImpl.java:727)
at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:352
)
at weblogic.jts.internal.TxContext.commit(TxContext.java:246)
at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJB
Object.java:88)
at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:661
)
at com.ffusion.alert.adminEJB.AEAlertAdminBeanEOImpl.init(AEAlertAdminBe
anEOImpl.java:297)
at com.ffusion.alert.adminEJB.AEAlertAdminBeanEOImpl_WLSkel.invoke(AEAle
rtAdminBeanEOImpl_WLSkel.java:798)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerOb
jectAdapter.java, Compiled Code)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicReques
tHandler.java:69)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

Fri Jul 13 10:50:42 EDT 2001:<D> <JVMSocketHTTPServer> Closing JVM socket: 'webl
ogic.socket.JVMSocketHTTPServer@bd2d8942 - id: '1', closed: 'true', lastRecv:
'9
95035842468''
java.lang.Throwable: Stack trace
at weblogic.socket.JVMSocketHTTPServer.close(JVMSocketHTTPServer.java:43
3)
at weblogic.socket.JVMAbbrevSocket.close(JVMAbbrevSocket.java:383)
at weblogic.rjvm.ConnectionManager.shutdown(ConnectionManager.java, Comp
iled Code)
at weblogic.rjvm.ConnectionManagerServer.shutdown(ConnectionManagerServe
r.java, Compiled Code)
at weblogic.rjvm.RJVMImpl.peerGone(RJVMImpl.java, Compiled Code)
at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:523)
at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManag
er.java:720)
at weblogic.socket.JVMAbbrevSocket.gotExceptionReceiving(JVMAbbrevSocket
java:397)
at weblogic.socket.JVMSocketHTTPServer.checkIsDead(JVMSocketHTTPServer.j
ava:266)
at weblogic.socket.JVMSocketHTTPServer$TunnelScavenger.trigger(JVMSocket
HTTPServer.java, Compiled Code)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
edTrigger.java, Compiled Code)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
er.java, Compiled Code)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java,
Compiled Code)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)

[Shiva Paranandi]

Looks like the transaction is taking so much time that the tcp sockets are timing out on the
client/server side. Also, are you doing any explicit setRollBack's? What platform are you on?
Check for the tcpListenDrop parameter on Solaris. You might also want to see this link
http://www.weblogic.com/platforms/sun/index.html
If you are on other platforms you might want to search around for TCP parameters.
I think a tcpdump on NT would help too.

Shiva.