Weblogic.rjvm.PeerGoneException

this package is not in the API doc on the web for WL5.1... but i still get
an error:
 <RJVM> Signaling
peer -2000438937484024190S110.20.116.265:[7031,7031,7032,7032,7031,-1] gone:
weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException]
anyone know where I can find some info on it?

Hendry Janto wrote:
Hi,
I got problem in my weblogic server. I got 1 table SQL Server 2000 contains 31 millions of records. When I try to delete some records using Statement.executeUpdate, it tooks about 7 hours, and then comes out error message as follow :
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read]]
My question is, what is the meaning of this error message, and will this situation cause the weblogic server performance / SQL Server 2000 performance dropping ? Coz after I restart the weblogic server, the performance back to normal again. Thanks.Hi. The PeerGoneException has nothing to do with JDBC, but indicates a communication failure
between WLS and an external client. The SQLServer issue is separate. Whose JDBC driver
are you using? The SQLServer delete problem is internal to the DBMS and certainly a function of the
size of the table. How are you doing the update? Is it via a PreparedStatement? Please show it
to me.
Joe Weinstein at BEA

Similar Messages

Getting weblogic.rjvm.PeerGoneException while posting request to foreign Q

Hi,
There are two application deployed on 2 different weblogic server .Say application A(EJB) is deployed on weblogic 9 and Application B (Oracle service Bus) is runing on Weblogic 10.3.
Application A sends request to a queue that is on applcation B server. Weblogic (app A) has foreign JMS server that exports the queue of app B. Configuration at Application A is :
<foreign-server name="JmsSyncServer">
<sub-deployment-name>SUBDEPLOYMENT_xyz</sub-deployment-name>
<foreign-destination name="Synchronous Request Queue">
<local-jndi-name>spain.queue.sebulasyncoutput</local-jndi-name>
<remote-jndi-name>osb.jms.queue.extern.service.request</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="Sebula Synchronous QCF">
<local-jndi-name>spain.SebulaSyncQueueConnectionFactory</local-jndi-name>
<remote-jndi-name>osb.jms.cf.nonXA</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<connection-url>t3://abcd.1.com:20001,abcd.2.com::20002</connection-url>
</foreign-server>
Now this cf and queue osb.jms.cf.nonXA and osb.jms.queue.extern.service.request are implemented on application B weblogic server. No authentication is given to this implementation. As soon as application A posts request to Application B following exception is thrown in application A logs :
2010.05.21 16:31:04,919 | ERROR | SyncEaiSebulaDelegate | <null|null|U289145226331099999430000> Failed to send JMS request: properties[{ClientID=SPAIN, Operation=MsisdnDetails, message_type=sebula.sync.out, RequestTag=U289145226331099999430000}].
com.o2.spain.jms.MessagingException: Failure during JMS setup: destination[sebula_sync_output].
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:382)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.o2.spain.jms.ServiceLocator.lookupDestination(ServiceLocator.java:130)
at com.o2.spain.jms.ServiceLocator.getDestination(ServiceLocator.java:109)
at com.o2.spain.jms.MessageDestinationHandler.setup(MessageDestinationHandler.java:193)
at com.o2.spain.jms.MessageDestinationHandler.setupLazyAndAfterFailure(MessageDestinationHandler.java:165)
at com.o2.spain.jms.MessageDestinationHandler.getTemporaryReceiver(MessageDestinationHandler.java:543)
at com.o2.spain.jms.MessageDestination.getTemporaryReceiver(MessageDestination.java:318)
at com.o2.spain.jms.JmsClientImpl.doRequest(JmsClientImpl.java:147)
at com.o2.spain.jms.JmsClientImpl.request(JmsClientImpl.java:125)
at com.o2.spain.interfaces.sebula.sync.SyncEaiSebulaDelegate.executeRequest(SyncEaiSebulaDelegate.java:345)
at com.o2.spain.interfaces.sebula.sync.SyncEaiSebulaDelegate.getMsisdnDetails(SyncEaiSebulaDelegate.java:182)
at com.o2.spain.ejb.SynchronousEaiFacadeBean.getMsisdnDetails(SynchronousEaiFacadeBean.java:221)
at com.o2.spain.ejb.SynchronousEaiFacade_letkhg_ELOImpl.getMsisdnDetails(SynchronousEaiFacade_letkhg_ELOImpl.java:405)
at com.o2.spain.ejb.SpainWebFacadeBean.getMsisdnDetails(SpainWebFacadeBean.java:1084)
at com.o2.spain.ejb.SpainWebFacade_sesxly_ELOImpl.getMsisdnDetails(SpainWebFacade_sesxly_ELOImpl.java:1787)
at com.o2.spain.ejb.ws.SpainWebWSPortSoapBindingImpl.getMsisdnDetails(SpainWebWSPortSoapBindingImpl.java:379)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.o2.spain.ejb.ws.AxisServletFilter.doFilter(AxisServletFilter.java:29)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3242)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: com.o2.spain.jms.MessagingException: Failed looking up Destination [spain.queue.sebulasyncoutput].
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jndi.internal.ServerNamingNode_923_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:379)
... 58 more
Caused by: javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:382)
... 58 more
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jndi.internal.ServerNamingNode_923_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:379)
... 58 more
Caused by: java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:383)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:737)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:684)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:845)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:802)
at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:120)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
It will be great if someone helps in finding out the cause....waiting for reply..
thanks,
Kshitij

I had the exact same issue and found a solution here:
http://kr.forums.oracle.com/forums/thread.jspa?threadID=755132
"The root cause of the PGE in this instance was missing Principle classes in the remote JVM. An authenticated subject's (has our custom principles) security context is propagated to the remote JVM which throws a ClassNotFoundException, this is wrapped in the PGE."

Weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException

Hi,
We are working with Weblogic 6.1.
The system was quite stable, but a couple of days ago some batch process suddenly
started to fail, with no apparent reason, there was no change in the system neither
in the code.
The following exception is received:
Stopped, RemoteException weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
We have also noticed that other jobs had failed before due to some memory problems,
but using the Weblogic Console; Monitoring; Performance, then when some jobs had
some memory problems forcing the garbage collection the batches worked properly.
Maybe these 2 problems have no relation between one an other, but they appeared
at the same time.
Any help will be appreciated.
Thanks and best regards.

Hi,
We are working with Weblogic 6.1.
The system was quite stable, but a couple of days ago some batch process suddenly
started to fail, with no apparent reason, there was no change in the system neither
in the code.
The following exception is received:
Stopped, RemoteException weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
We have also noticed that other jobs had failed before due to some memory problems,
but using the Weblogic Console; Monitoring; Performance, then when some jobs had
some memory problems forcing the garbage collection the batches worked properly.
Maybe these 2 problems have no relation between one an other, but they appeared
at the same time.
Any help will be appreciated.
Thanks and best regards.

Weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds

Hi to All
when i am trying to retrieve huge amount of data using the application deployed in the weblogic server 9.1
i am getting the following exception at the client side...
my client was using "weblogic.jar" to run and compile...
this application will take 10-15 mins to process the request.. but i am getting this exception at the 5 min of the request...
the exception follows.....
weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
.java:315)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
.java:250)
at com.nybot.prd.businesscomponent.ProductDictionaryMaintenanceBean_etiu
ur_EOImpl_910_WLStub.retrieveInstruments(Unknown Source)
at RetrieveFuturesInstruments.testInstruments(RetrieveFuturesInstruments
.java:67)
at RetrieveFuturesInstruments.main(RetrieveFuturesInstruments.java:87)
S.Prabhu

Senthamarai Prabhu wrote:
Hi to All
when i am trying to retrieve huge amount of data using the application
deployed in the weblogic server 9.1 i am getting the following exception
at the client side... my client was using "weblogic.jar" to run and
compile... this application will take 10-15 mins to process the request..
but i am getting this exception at the 5 min of the request...
the exception follows.....
weblogic.rjvm.PeerGoneException: No message was received for: '240'Hi,
Just increase the timeout on JTA level
B
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst

Root exception is weblogic.rjvm.PeerGoneException:

I have a problem doing the Look onto the Weblogic server.
 Here is the code I use in a method for this purpose and call the
 method from main(). I paste the code below (enclosed within "CODE
 BEGINS", "CODE ENDS")
 -----------------CODE BEGINS-----------------------------------------
 System.out.println("DataCollector : Look up serverHome called");
 Hashtable props = new Hashtable();
 props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
 props.put(Context.PROVIDER_URL, url);
 props.put(Context.SECURITY_PRINCIPAL, userName);
 props.put(Context.SECURITY_CREDENTIALS, passWord);
 System.out.println("Before Inital Context "+props);
 Context ctx = new InitialContext(props);
 System.out.println("Initial Context successful");
 serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
 System.out.println("Look up successful");
 ctx.close();
 System.out.println("Closed context successfully");
 -----------------CODE ENDS-----------------------------------------
 On executing this piece of code, I receive the following Exceptions
 -------------OUTPUT OF CODE BEGINS---------------------
 DataCollector : Look up serverHome called
 Before Inital Context
 {java.naming.provider.url=T3://njecomprod06:10817,
 java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
 java.naming.security.principal=system,
 java.naming.security.credentials=security}
 Initial Context successful
 Exception in thread "main" javax.naming.CommunicationException. Root
 exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
 java.io.EOFException
 java.io.EOFException
 at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
 at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
 at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 -------------OUTPUT OF CODE ENDS---------------------
 This piece of code fails in the line
 serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
 The weblogic server is standalone (not on a cluster). All other
 details give for this purpose like port no, username, password etc are
 correct.
 Also, On the WebLogic server prompt, the following stack trace is
 printed. Please let me know what is wrong in this look up code
 element.
 Thanks in advance for your help.
 -------------------------------------------------------EXCEPTION ON
 WEBLOGIC SIDE BEGINS--------------------------
 java.io.EOFException
 at java.io.DataInputStream.readInt(DataInputStream.java:343)
 at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
 creating response stream ] - with nested exception:
 [java.io.EOFException]
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 <Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
 <Uncaught Throwable in processSockets
 java.io.EOFException:
 Start server side stack trace:
 java.io.EOFException
 at java.io.DataInputStream.readInt(DataInputStream.java:343)
 at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 at java.io.DataInputStream.readInt(DataInputStream.java:343)
 at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
 creating response stream ]
 Start server side stack trace:
 java.io.EOFException
 at java.io.DataInputStream.readInt(DataInputStream.java:343)
 at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 --------------- nested within: ------------------
 weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
 creating response stream ] - with nested exception:
 [java.io.EOFException]
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 - with nested exception:
 [java.io.EOFException:
 Start server side stack trace:
 java.io.EOFException
 at java.io.DataInputStream.readInt(DataInputStream.java:343)
 at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 End server side stack trace
 at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
 at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 -------------------------------------------------------EXCEPTION ON
 WEBLOGIC SIDE ENDS--------------------------


You may want to open a support case with BEA to resolve this issue. I
 suspect that you may be using some server patches which have not also
 been applied to your WebLogic client JVMs. If that is the case,
 upgrading to the latest service pack may be the easiest and best remedy.
 Sincerely,
 Charlie Therit
 Developer Relations Engineer
 BEA Support
 Lakshmi Narasimhan wrote:
 >I have a problem doing the Look onto the Weblogic server.
 >
 >Here is the code I use in a method for this purpose and call the
 >method from main(). I paste the code below (enclosed within "CODE
 >BEGINS", "CODE ENDS")
 >
 >
 >-----------------CODE BEGINS-----------------------------------------
 >{
 > System.out.println("DataCollector : Look up serverHome called");
 > Hashtable props = new Hashtable();
 > props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
 > props.put(Context.PROVIDER_URL, url);
 > props.put(Context.SECURITY_PRINCIPAL, userName);
 > props.put(Context.SECURITY_CREDENTIALS, passWord);
 > System.out.println("Before Inital Context "+props);
 > Context ctx = new InitialContext(props);
 > System.out.println("Initial Context successful");
 > serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
 > System.out.println("Look up successful");
 > ctx.close();
 > System.out.println("Closed context successfully");
 >}
 >-----------------CODE ENDS-----------------------------------------
 >
 >On executing this piece of code, I receive the following Exceptions
 >
 >-------------OUTPUT OF CODE BEGINS---------------------
 >DataCollector : Look up serverHome called
 >Before Inital Context
 >{java.naming.provider.url=T3://njecomprod06:10817,
 >java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
 >java.naming.security.principal=system,
 >java.naming.security.credentials=security}
 >Initial Context successful
 >
 >Exception in thread "main" javax.naming.CommunicationException. Root
 >exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
 >java.io.EOFException
 >java.io.EOFException
 > at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
 > at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
 > at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >-------------OUTPUT OF CODE ENDS---------------------
 >
 >This piece of code fails in the line
 >
 >serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
 >
 >The weblogic server is standalone (not on a cluster). All other
 >details give for this purpose like port no, username, password etc are
 >correct.
 >
 >Also, On the WebLogic server prompt, the following stack trace is
 >printed. Please let me know what is wrong in this look up code
 >element.
 >
 >Thanks in advance for your help.
 >
 >-------------------------------------------------------EXCEPTION ON
 >WEBLOGIC SIDE BEGINS--------------------------
 >java.io.EOFException
 > at java.io.DataInputStream.readInt(DataInputStream.java:343)
 > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >--------------- nested within: ------------------
 >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
 >creating response stream ] - with nested exception:
 >[java.io.EOFException]
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 ><Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
 ><Uncaught Throwable in processSockets
 >java.io.EOFException:
 >Start server side stack trace:
 >java.io.EOFException
 > at java.io.DataInputStream.readInt(DataInputStream.java:343)
 > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >End server side stack trace
 >
 > at java.io.DataInputStream.readInt(DataInputStream.java:343)
 > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >--------------- nested within: ------------------
 >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
 >creating response stream ]
 >
 >Start server side stack trace:
 >java.io.EOFException
 > at java.io.DataInputStream.readInt(DataInputStream.java:343)
 > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >--------------- nested within: ------------------
 >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
 >creating response stream ] - with nested exception:
 >[java.io.EOFException]
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >End server side stack trace
 > - with nested exception:
 >[java.io.EOFException:
 >Start server side stack trace:
 >java.io.EOFException
 > at java.io.DataInputStream.readInt(DataInputStream.java:343)
 > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
 > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
 > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
 > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >End server side stack trace
 >]
 > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
 > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
 > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
 > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
 > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
 > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 >
 >
 >-------------------------------------------------------EXCEPTION ON
 >WEBLOGIC SIDE ENDS--------------------------
 >
 >
 [att1.html]

Weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds with WLS 7.0

I've got an EJB application which, at one stage, has to go off and import a lot
of data from another external application. A java client is triggering this execution.
I've updated the Transaction timeout setting and Stuck Thread timeout setting
on the server. But the client is still getting a weblogic.rjvm.PeerGoneException.
I've found a previous message which talks about updating either the weblogic.system.periodLength
property on the server or the weblogic.system.idlePeriodsUntilTimeout on the client.
However, the thread was referring to older versions of WLS (5 & 6). Is this
still a valid approach for WLS 7.0? I couldn't find the weblogic.properties file
on the server, and if I try to use the client system property, my client doesn't
start.
If anyone has any guidance on this, I would be very grateful.
Thanks,
Ed

Hello Ed,
It appears that the config.dtd is bundled in the weblogic.jar archive. I don't
believe that the exact location of the DTD/Schema is specified at the top of the
config.xml file. I hope that you are able to figure out how to solve your problem.
Perhaps you could investigate the issue further with a BEA Engineer.
Take care,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Ed Hillmann" <[email protected]> wrote:
>
Thanks for the help, Ryan. What is the address for the config.xml Schema/DTD?
It doesn't appear in the file.
That JTA settings is already handled. This error doesn't seem to be
due to a
Transaction being left open (I believe it spits out another exception).
Thanks,
Ed
"Ryan LeCompte" <[email protected]> wrote:
Hello Ed,
I am not very familiar with this particular error, but I did a bit of
research
and it appears that most of these kinds of issues occured in the WLS
5/6 days
(as you mentioned, various parameters are set in the weblogic.properties
file).
However, weblogic.properties is not really used in WLS 6+. There isa
document
describing how to convert the old weblogic.properties to the currently
used config.xml
file:
http://edocs.bea.com/wls/docs70/ConsoleHelp/conversion.html
Also, you may wish to look at the DTD for the config.xml file, as you
may find
various parameters that you can set which may help solve your problem
(for example):
http://edocs.bea.com/wls/docs70/config_xml/JTA.html#536936
There is a TimeoutSeconds parameter which defaults to 30. You may try
changing
this value.
Hope this helps!
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Try adding the -classic parameter along with the other parameters in
the startWebLogic.cmd
file (with the other parameters for remot debugging).

Weblogic.rjvm.PeerGoneException: ; nested exception is

Hi,
I am trying to access Remote EJB(deployed in server A) from Client (deployed in server B). I am getting this error.
Please help!!!
weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
     java.io.InvalidClassException: com.sybase.jdbc2.tds.SybTimestamp; local class incompatible: stream classdesc serialVersionUID = 4038526507615253075, local class serialVersionUID = -4859870295624974195
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:315)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:250)
     at com.bankofny.gdoasis.payment.ejb.PaymentCalculationManagerRemoteEJB_suyjh6_EOImpl_910_WLStub.rollInterestPeriod(Unknown Source)
     at com.bankofny.gdoasis.batch.payment.RollInterestPeriod.main(RollInterestPeriod.java:96)
Caused by: java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
     java.io.InvalidClassException: com.sybase.jdbc2.tds.SybTimestamp; local class incompatible: stream classdesc serialVersionUID = 4038526507615253075, local class serialVersionUID = -4859870295624974195
     at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:430)
     at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:362)
     at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:359)
     at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:851)
     at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:787)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: java.io.InvalidClassException: com.sybase.jdbc2.tds.SybTimestamp; local class incompatible: stream classdesc serialVersionUID = 4038526507615253075, local class serialVersionUID = -4859870295624974195
     at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:546)
     at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
     at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
     at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:36)
     at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
     at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:65)
     at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:37)
     at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:214)
     at weblogic.rjvm.MsgAbbrevInputStream.init(MsgAbbrevInputStream.java:169)
     at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:424)
     ... 9 more

Hi
This is due to invalid class compatibility. May be you are using the two different versions of classes. one at server side and another at your client side. please make sure both are having the SerialVersion Id's.
regards,
Sudheer

RJVM Signaling peer 3688822629303549796C160.96.179.40 gone: weblogic.rjvm.PeerGoneException:

Hi,
We are using WebLogic Server 5.1 SP8 as our AppServer.
The server is killed abruptly with the following message :
Mon Aug 20 14:44:39 GMT+08:00 2001: <RJVM> Signaling peer 3688822629303549796C160.96.179.40
gone: weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException]
What should be the possible reasons?
Is it something to do with the N/W breakups ?
Regards,
TejoKiran.Y

Dear Kumar,
Thanks for your interest in answering the Q.
Well, there is no other stack trace available.
The last message we saw is ,
Mon Aug 20 14:44:39 GMT+08:00 2001: <RJVM> Signaling peer 3688822629303549796C160.96.179.40
gone: weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException]
The server was killed completely.
Infact, 160.96.179.40 is the IP Address of our Application Server (WebLogic Server
is runnning at port 7001).
That is the last statement.
We observed this error few times before in our log file, but it
didnot bring down the server.
Would U mind explaining me what exactly does that error mean?
For your info:
We also saw this message few times,
Fri Aug 17 15:08:36 GMT+08:00 2001: <CliCon-#|ccls|0.998032002043> Connection
to client for ClientContext - id: '#|ccls|0.998032002043', bound: 'true', dead:
'false' has been unexpectedly lost because weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException].
Initiating hard disconnect.
Regards,
TejoKiran.Y
Kumar Allamraju <[email protected]> wrote:
Are you sure that the server is killed (crashed)?
The following informative message only says that the client
with IP 160.96.179.40 has peer gone'd
Could you post complete stack trace?
TejoKiran wrote:
Hi,
We are using WebLogic Server 5.1 SP8 as our AppServer.
The server is killed abruptly with the following message :
Mon Aug 20 14:44:39 GMT+08:00 2001: <RJVM> Signaling peer 3688822629303549796C160.96.179.40
gone: weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.io.EOFException]
What should be the possible reasons?
Is it something to do with the N/W breakups ?
Regards,
TejoKiran.Y

WLS 9.2 - weblogic.rjvm.PeerGoneException

Hello, I am currently dealing with a particularly annoying problem for which I have already raised a support case with BEA.
Our application makes calls to a thired party security application via EJBs provided by the thired party.
The thired party application registers and RMI stub on the WLS JNDI tree and the thired party EJBs use this stub to make calls to the security application.
We have a simple test harness that Remotely looks up the different EJBs and calls methods on them. This works for the limited set of methods that we test.
However at specific points in the applications usage we run into:
####<Dec 10, 2006 8:13:38 PM GMT> <Notice> <Stdout> <myserver> <examplesServer> <[ACTIVE] ExecuteThread: '0' for
queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1165781618271> <000000> <20:13:38.271: Error: at.client.
AtClient.doService() : Client: Service com/thalesesecurity/at/server/wl92dsms -
has gone down! Trying next server.
Exception: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException>
Once we get this error all further calls to the thired party beans that use the stub fail with:
####<Dec 10, 2006 8:13:38 PM GMT> <Notice> <Stdout> <myserver> <examplesServer> <[ACTIVE] ExecuteThread: '0' for
queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1165781618489> <000000> <<Dec 10, 2006 20:13:38> <FATAL>
com.output.rule.impl.ValidateAcknowledgement.checkSignature(86): common.service.security.exceptions.Securit
yException: Unexpected exception: com.thalesesecurity.at.service.ServiceException: Client: Could not connect to any server
Error(s):
Client: Service com/thalesesecurity/at/server/wl92dsms -
has gone down! Trying next server.
Exception: java.rmi.ConnectException: Could not establish a connection with 5640100714642584389C:172.21.4.27R:-522103521865481
3556S:myserver:[7003,7003,-1,-1,-1,-1,-1]:wl_server:examplesServer, java.rmi.ConnectException: Destination is not
a server; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination is not a server; No available router to destination
The thired party server is running and is reachable. It seems the exception may be masking some other problem.
So far the only real lead I have has come from turning up some debug parameters which reveals that the EOF at the root of the POE seems to occur shortly after the last of the 100 principles that belong to the user has been transmitted over the socket:
12928: ace2 d273 7100 7e00 0c74 0023 434f 4c4c ...sq.~..t.#COLL
12944: 4543 545f 5052 4f43 4553 5349 4e47 5f52 ECT_PROCESSING_R
12960: 4550 4f52 545f 5052 494e 4349 5041 4c75 EPORT_PRINCIPALu
12976: 7100 7e00 1100 0000 0d31 3136 3733 3239 q.~......1167329
12992: 3636 3638 3130 7571 007e 0011 0000 0010 666810uq.~......
13008: b82b 60ed 529c c990 fa98 c67e d667 174e .+`.R......~.g.N
13024: 78 x
>
####<Dec 28, 2006 7:31:24 PM GMT> <Debug> <RJVM> <myserver> <examplesServer> <ExecuteThread: '8' for queue: 'weblogic.soc
ket.Muxer'> <<WLS Kernel>> <> <> <1167334284325> <BEA-000517> <Error on connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMCo
nnection@1f78388'
java.io.EOFException
java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:383)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:732)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:679)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:840)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:797)
at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:120)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
I have asked our application team to try reducing the number of principles that can be assigned to the user to see if this has any effect on the problem. I have already tried, among others, incleasing the maximum message size for all protocols and ensureing and security jar files before the weblogic.jar file but so far I have had no luck. Any suggestions would be most welcome.
Hussein Badakhchani
http://dev2dev.bea.com/blog/hoos
London Middleware
http://londonmiddleware.org/index.html
Edited by hoos at 12/29/2006 9:25 PM

The root cause of the PGE in this instance was missing Principle classes in the remote JVM. An authenticated subject's (has our custom principles) security context is propagated to the remote JVM which throws a ClassNotFoundException, this is wrapped in the PGE.

Hussein Badakhchani
London Middleware

Edited by hoos at 01/09/2007 1:48 AM
Edited by hoos at 01/09/2007 1:49 AM

RMI client losing connection and weblogic.rjvm.PeerGoneException

What causes PeerGoneExceptions? We are seeing this very often on our
production and test systems. We use WLS RMI clients connected to WLS 4.5.1
servers w/ service pack 10. I understand that there is a heartbeat between
the client JVM and the server JVM. Is there any documentation that explains
how this actually works. For example, how often does the client send its
heartbeat. Is it configurable? What could cause it to stop or drop the
connection. We are using straight T3 (no T3S or HTTP).
thanks for your help,
Edwin Marcial
Intercontinental Exchange

What causes PeerGoneExceptions? We are seeing this very often on our
production and test systems. We use WLS RMI clients connected to WLS 4.5.1
servers w/ service pack 10. I understand that there is a heartbeat between
the client JVM and the server JVM. Is there any documentation that explains
how this actually works. For example, how often does the client send its
heartbeat. Is it configurable? What could cause it to stop or drop the
connection. We are using straight T3 (no T3S or HTTP).
thanks for your help,
Edwin Marcial
Intercontinental Exchange

Java.lang.NoClassDefFoundError: weblogic/rjvm/LocalRJVM

Has anyone seen this error, when trying to get an InitialContext?
java.lang.NoClassDefFoundError: weblogic/rjvm/LocalRJVM
If I create an InitialContext within the main function of my test
program everything is fine. However, when
I try to call a method on the class that is supposed to create the
InitialContext I get this error. The settings for
creating the InitialContext are identical in 'main' and the helper class
I have to create the InitialContext. I can't
make any sense out of this one. I'm running WLS 5.1 with service pack
3.
Jay
[att1.html]

Has anyone seen this error, when trying to get an InitialContext?
java.lang.NoClassDefFoundError: weblogic/rjvm/LocalRJVM
If I create an InitialContext within the main function of my test
program everything is fine. However, when
I try to call a method on the class that is supposed to create the
InitialContext I get this error. The settings for
creating the InitialContext are identical in 'main' and the helper class
I have to create the InitialContext. I can't
make any sense out of this one. I'm running WLS 5.1 with service pack
3.
Jay
[att1.html]

Serializing an instance of weblogic.rjvm.RJVM

 I'm migrating a WebApp from WebLogic 5.1 (single server) to a 6.0 Cluster, and
 I've discovered that when one of the servlets attempts to retrieve the HttpSession
 from the Request, a NotSerializableException is thrown. When I look through the
 stack-trace, I can see the servlet requesting the HttpSession from the Request,
 and then WebLogic sometimes needs to retrieve it from another server within the
 cluster. I did a bit of digging, and found that somewhere within the object-graph,
 there's a Hashtable that contains an instance of weblogic.rjvm.RJVM, and that's
 not Serializable (not surprising).
 Being that I didn't write this application, I don't know how deeply nested
 this object is - my assumption is that in the HttpSession, one of the objects
 is the parent of an object (or many objects), one of which contains the Hashtable
 which contains the RJVM reference. The problem is, I don't know how to identify
 the rogue object's parent(s). This wan't an issue on 5.1 because it never ran
 in a cluster. This app also runs fine on a WebLogic 6.0 stand-alone server. It's
 only when we activate clustering that we see this problem of Serializing the RJVM
 object.
 I've tried to guess what kind of object would contain the Hashtable that posesses
 the RJVM object. One possibility is some type of Context object - this application
 uses sfsb and slsb, and in some cases the application designers decided to put
 a reference to the EJB in the HttpSession, rather than an EJBHandle. It may be
 that when HttpSession is replicated throughout the cluster, the sfsb is serialized,
 along with the SessionContext that it posesses?
 Any ideas on how I'd locate the parent(s) of the instance of weblogic.rjvm.RJVM?
 Thanks,
 --Benjamin Peter
 [email protected]


Have you tried examining the contents of the session? You can iterate
 through the entries.
 Peace,
 Cameron Purdy
 Tangosol Inc.
 << Tangosol Server: How Weblogic applications are customized >>
 << Download now from http://www.tangosol.com/download.jsp >>
 "Benjamin Peter" <[email protected]> wrote in message
 news:[email protected]...
 >
 > I'm migrating a WebApp from WebLogic 5.1 (single server) to a 6.0
 Cluster, and
 > I've discovered that when one of the servlets attempts to retrieve the
 HttpSession
 > from the Request, a NotSerializableException is thrown. When I look
 through the
 > stack-trace, I can see the servlet requesting the HttpSession from the
 Request,
 > and then WebLogic sometimes needs to retrieve it from another server
 within the
 > cluster. I did a bit of digging, and found that somewhere within the
 object-graph,
 > there's a Hashtable that contains an instance of weblogic.rjvm.RJVM, and
 that's
 > not Serializable (not surprising).
 >
 > Being that I didn't write this application, I don't know how deeply
 nested
 > this object is - my assumption is that in the HttpSession, one of the
 objects
 > is the parent of an object (or many objects), one of which contains the
 Hashtable
 > which contains the RJVM reference. The problem is, I don't know how to
 identify
 > the rogue object's parent(s). This wan't an issue on 5.1 because it never
 ran
 > in a cluster. This app also runs fine on a WebLogic 6.0 stand-alone
 server. It's
 > only when we activate clustering that we see this problem of Serializing
 the RJVM
 > object.
 >
 > I've tried to guess what kind of object would contain the Hashtable
 that posesses
 > the RJVM object. One possibility is some type of Context object - this
 application
 > uses sfsb and slsb, and in some cases the application designers decided to
 put
 > a reference to the EJB in the HttpSession, rather than an EJBHandle. It
 may be
 > that when HttpSession is replicated throughout the cluster, the sfsb is
 serialized,
 > along with the SessionContext that it posesses?
 >
 > Any ideas on how I'd locate the parent(s) of the instance of
 weblogic.rjvm.RJVM?
 >
 > Thanks,
 > --Benjamin Peter
 > [email protected]

Couldn't connect to weblogic.rjvm.RJVMImpl

Hi,
Could anyone tell me something about the possible reason of this exception? Is
there any meaningful information in the "id" which can describe what caused this
exception?
Thanks for you help,
SB
2002-11-27 11:47:18,243 ERROR [ExecuteThread: '8' for queue: 'default'] ucp.MyListener
- UcpConnector.sendMessage failed, trying to relookup remote object: java.rmi.ConnectException:
Couldn't connect to weblogic.rjvm.RJVMImpl@24cb85 - id: '-67972920144506
84392C:172.20.161.27R:-7681834094030937225S:172.20.161.27:[7004,7004,-1,-1,7004,-1,-1]:test_domain:test_node03'
connect time: 'Wed Nov 27 11:47:18 CET 2002'

I've done the steps but the problem still persists. I don't know if I had this before, but now both machines can't see each other.
From Node1 logs *.out file:
<Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member MyJMSModule!MyJMSServer2@my_cacheTopic:
weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException:
Couldn't connect to weblogic.rjvm.RJVMImpl@62017d - id: '4786464166486913267S:10.48.92.70:[7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp2'
connect time: 'Wed Nov 05 16:03:53 EET 2008' - it is likely that the connection has already been shut down; nested exception is:
java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@62017d - id: '4786464166486913267S:10.48.92.70:[7001,7001,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp2'
connect time: 'Wed Nov 05 16:03:53 EET 2008' - it is likely that the connection has already been shut downand from Node2 logs *.out file:
<Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member MyJMSModule!MyJMSServer1@my_cacheTopic:
weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException:
Couldn't connect to weblogic.rjvm.RJVMImpl@24b64a - id: '-788798942991630857S:10.48.92.69:[7003,7003,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp1'
connect time: 'Wed Nov 05 16:03:59 EET 2008' - it is likely that the connection has already been shut down; nested exception is:
java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@24b64a - id: '-788798942991630857S:10.48.92.69:[7003,7003,-1,-1,-1,-1,-1]:app1:7003,app2:7001:my_domain:NodeApp1'
connect time: 'Wed Nov 05 16:03:59 EET 2008' - it is likely that the connection has already been shut downThis happens just after the managed servers have been started with the application previously deployed.

How to look up a TxDataSource bound in weblogic JNDI

HI,
How can i look up a TxDataSource bound in weblogic JNDI. When i access it using
javax.sql.XADataSourse ds = (XADataSourse)context.lookUp(jndiName)
..it gives me classcast exception.
and if i lookup it using javax.sql.DataSource like below
javax.sql.DataSourse ds = (DataSourse)context.lookUp(jndiName)
then while executing my sql on the connection object it throws some other excepiton
like below
java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jdbc.rmi.SerialStatement.executeQuery(SerialStatement.java:92)
at TestTransactionMgr.main(TestTransactionMgr.java:46)
How can i solve this problem.. Actually my application needs to handle distributed transactions so i need to implement XADataSource.
can somebody help me iin this.
Thanks & Regards
Akhil Nagpla

Hi Akhil did u get the solution for distributed database /
I am also working on same but i dint get the solution yet. Please if u have any solution for the same do mail me to [email protected] and [email protected]
here goes my problem !
we have 2 oracle databases.
I am using Stateless EJB and container managed transaction !
And inside a ejb method i am getting 2 different connection from 2 different datasources ok !
Since am using container managed transaction it starts transaction automatically when the method begins,
and the transaction ends when the method exit out ok !
Now i insert into 2 databases and when the method exits it gives an error listed below !
i am using NON emulated datasource with class name "com.evermindsql.DriverManagerDataSource"
and looking up this datasource in the EJB with name specified in location attribute of datasource !
"com.evermind.server.rmi.OrionRemoteExcepttion: Transaction was rolled back: javax.transaction.SystemException: could not commit: error code 29540- for additional error code check the oracle log file"
For distributed database we configured DBLINK also !
If u can give more info regarding DBlink it will be better ! Even after we set DBlink we are getting error !
Please tell us how to configure the database !
Oracle 9iAS
Oracle 9i DB
regards
Sreenath.V

How can i look up a TxDataSource bound in Weblogic JNDI

          HI,
          How can i look up a TxDataSource bound in weblogic JNDI. When i access it using
          javax.sql.XADataSourse ds = (XADataSourse)context.lookUp(jndiName)
          .it gives me classcast exception.
          and if i lookup it using javax.sql.DataSource like below
          javax.sql.DataSourse ds = (DataSourse)context.lookUp(jndiName)
          then while executing my sql on the connection object it throws some other excepiton
          like below
          java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected
          Exception - with nested exception:
          [weblogic.rjvm.PeerGoneException: ; nested exception is:
                  java.io.EOFException]
          at weblogic.jdbc.rmi.SerialStatement.executeQuery(SerialStatement.java:92)
          at TestTransactionMgr.main(TestTransactionMgr.java:46)
          How can i solve this problem.. Actually my application needs to handle distributed
          transactions so i need to implement XADataSource.
          can somebody help me iin this.
          Thanks & Regards
          Akhil Nagpla


          HI,
          How can i look up a TxDataSource bound in weblogic JNDI. When i access it using
          javax.sql.XADataSourse ds = (XADataSourse)context.lookUp(jndiName)
          .it gives me classcast exception.
          and if i lookup it using javax.sql.DataSource like below
          javax.sql.DataSourse ds = (DataSourse)context.lookUp(jndiName)
          then while executing my sql on the connection object it throws some other excepiton
          like below
          java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected
          Exception - with nested exception:
          [weblogic.rjvm.PeerGoneException: ; nested exception is:
                  java.io.EOFException]
          at weblogic.jdbc.rmi.SerialStatement.executeQuery(SerialStatement.java:92)
          at TestTransactionMgr.main(TestTransactionMgr.java:46)
          How can i solve this problem.. Actually my application needs to handle distributed
          transactions so i need to implement XADataSource.
          can somebody help me iin this.
          Thanks & Regards
          Akhil Nagpla

Weblogic.rjvm.PeerGoneException

Similar Messages

Maybe you are looking for