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
Similar Messages
-
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,
EdHello 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). -
Error msg: "Config message not received after 45 seconds"
I have developed a simple stateless session bean. After being called once, the following is output to the log:
Thu Jan 04 18:15:46 CST 2001:<I> <RJVM> Signaling peer 3978882810638278829C198.171.129.36 gone: weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.net.SocketException: Connection reset by peer]
Exactly 45 seconds later the following is output and I can no longer access a JDBC connection from my pool:
Thu Jan 04 18:16:31 CST 2001:<I> <CliCon-#|myserver|0.978653734170> Connection to client for ClientContext - id: '#|myserver|0.978653734170', bound: 'true', dead: 'false' has been unexpectedly lost be
cause weblogic.rjvm.PeerGoneException: Config message not received after 45 seconds.
Initiating hard disconnect.
Can anyone shed some light on this for me?
Thanks in advance!Hi,
this is the explanation why this occours:
If there is a t3 Client connects to the server, every ( weblogic.system.configTimeoutCheckVal
) time, ConfigTimeoutChecker will run to check the t3 client is disconnected or
not. The problem is, if the client has already disconnected, the ConfigTimeoutChecker
still runs every time to check the disconnected t3Client again and again.
This should be solved with SP11.
Christian Plenagl
Developer Relations Engineer
BEA Support
"kelvin" <[email protected]> wrote:
>
I am using WLS 5.1 sp8 128SSL, I got this error. I results that the java
object
in the JMS channel is sometimes missing. I increased the weblogic server
thread
from 15 to 30. But still can't help. I also ugrade the client server
to use the
same sp8. But can't help. Some one mentions the sp9 can solve this problem.
It
is true? anyone have it for unix ? where can I download it? I can't
find it in
weblogic web site.
Kelvin -
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:<I> <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.YDear 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:<I> <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:<I> <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:<I> <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<p>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.</p>
<p>
Hussein Badakhchani
London Middleware
</p>
Edited by hoos at 01/09/2007 1:48 AM
Edited by hoos at 01/09/2007 1:49 AM -
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,
KshitijI 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." -
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
this package is not in the API doc on the web for WL5.1... but i still get
an error:
<I> <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 -
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: ; 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 moreHi
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 -
A Kerberos Error Message was received: on logon session
Hi i am getting this error in event viewer in a client machine, from where powershell sccripts collecting data from our sharepoint servers
Log Name: System
Source: Microsoft-Windows-Security-Kerberos
Date: 9/16/2014 11:09:42 PM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PortalHealthChe.XYZportal.com
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 20:9:42.0000 9/16/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XYZPORTAL.COM
Server Name: HTTP/XYZWFE01.XYZPORTAL.COM
Target Name: HTTP/[email protected]
Error Text:
File: 9
Line: f09
Error Data is in record data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Kerberos" Guid="{98E6CFCB-EE0A-41E0-A57B-622D4E1B30B1}" EventSourceName="Kerberos" />
<EventID Qualifiers="32768">3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-16T20:09:42.000000000Z" />
<EventRecordID>5466</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>PortalHealthChe.XYZportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="LogonSession">
</Data>
<Data Name="ClientTime">
</Data>
<Data Name="ServerTime">20:9:42.0000 9/16/2014 Z</Data>
<Data Name="ErrorCode">0x7</Data>
<Data Name="ErrorMessage"> KDC_ERR_S_PRINCIPAL_UNKNOWN</Data>
<Data Name="ExtendedError">0xc0000035 KLIN(0)</Data>
<Data Name="ClientRealm">
</Data>
<Data Name="ClientName">
</Data>
<Data Name="ServerRealm">XYZPORTAL.COM</Data>
<Data Name="ServerName">HTTP/XYZWFE01.XYZPORTAL.COM</Data>
<Data Name="TargetName">HTTP/[email protected]</Data>
<Data Name="ErrorText">
</Data>
<Data Name="File">9</Data>
<Data Name="Line">f09</Data>
<Binary>3015A103020103A20E040C350000C00000000001000000</Binary>
</EventData>
</Event>
adilHi
i am getting this error in a client machine
Log Name: System
Source: Microsoft-Windows-Security-Kerberos
Date: 9/16/2014 11:09:42 PM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PortalHealthChe.XYZportal.com
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 20:9:42.0000 9/16/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XYZPORTAL.COM
Server Name: HTTP/XYZWFE01.XYZPORTAL.COM
Target Name: HTTP/[email protected]
Error Text:
File: 9
Line: f09
Error Data is in record data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Kerberos" Guid="{98E6CFCB-EE0A-41E0-A57B-622D4E1B30B1}" EventSourceName="Kerberos" />
<EventID Qualifiers="32768">3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-16T20:09:42.000000000Z" />
<EventRecordID>5466</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>PortalHealthChe.XYZportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="LogonSession">
</Data>
<Data Name="ClientTime">
</Data>
<Data Name="ServerTime">20:9:42.0000 9/16/2014 Z</Data>
<Data Name="ErrorCode">0x7</Data>
<Data Name="ErrorMessage"> KDC_ERR_S_PRINCIPAL_UNKNOWN</Data>
<Data Name="ExtendedError">0xc0000035 KLIN(0)</Data>
<Data Name="ClientRealm">
</Data>
<Data Name="ClientName">
</Data>
<Data Name="ServerRealm">XYZPORTAL.COM</Data>
<Data Name="ServerName">HTTP/XYZWFE01.XYZPORTAL.COM</Data>
<Data Name="TargetName">HTTP/[email protected]</Data>
<Data Name="ErrorText">
</Data>
<Data Name="File">9</Data>
<Data Name="Line">f09</Data>
<Binary>3015A103020103A20E040C350000C00000000001000000</Binary>
</EventData>
</Event>
adil -
Invoice reduction: no message was found for partner
Hi
As soon as I post invoice reduction, I am getting error msg - invoice reduction: no message was found for partner
Pls guide me
Thanks
KarthikeyanDear,
Please follow the below configuration, I guess in some point you missed the configuration, so please check your configuration.
1) Tax Treatment in Invoice Reduction
2) Maintain reasons for Invoice Reduction
3) IN OBYC - Transaction Type - RKA - Assign the debit & credit gl accounts
4) Go to OMWA - Double Click on Document Type - Double Click on Document type MIRO - Assign KG document type against -
document type invoice reduction
5) Assign No. Ranges to document type - KG
6) Orocess MIRO document with Invoice Reduction.
Thanks & Regards,
Siva Reddy.S -
Ichat: 'no data received for 10 seconds' message and both users using macs
my sister and i are both using macs. i have a desktop and she has a laptop. we used ichat several times with no problem. she's in cali, i'm in utah. then all of a sudden we started getting 'no data received for 10 seconds' error every time we try to chat. i've tried to find some answers on the boards, but all the explanations are over my head. i'm not a techie, so i needs things in simple, layman terms.
we're using AIM, and like i said, we're both on macs.
this is the error message the connection doctor gave me:
Chat ended with error -20
2007-04-04 22:23:38 -0600: No data has been received for the last 10 seconds.
Audio channel info: local machine using xxx.xxx.x.101:16388, expecting remote machine to send to xx.x.xx.xxx:16388
Video channel info: local machine using xxx.xxx.x.101:16388, expecting remote machine to send to xx.x.xx.xxx:16388
Chat ended with error -20
i would appreciate any assistance anyone can give me. thank you!Hi Matt,
Item 1
Go to System Preference > Sharing > Firewall Tab
Is this On ?
If it is do you have a separate iChat Setting (Not the bonjour ichat preset) ?
If it is On then do the pic around the Second pic here http://www.ralphjohnsuk.dsl.pipex.com/page4.html#_ports
Item 2
Next go to System Preferences > Network
In here choose the Connection method from the second drop down.
The choose the TCP/IP tab
From the information you posted in the first post I suggest that reads "Using DHCP" in the drop down and then an IP of 192.168.1.101
Further down it lists the DNS servers and SubNet Mask
And the the "Router" IP
This "router" maybe a actual router or a modem that routes.
The number at the end of your log is suggestive of a Linksys device.
Info for you 1
Now if this a router we will also ned to know if the Modem is doing DHCP (You should not have two device doing this)
If the "router" IP is 192.168.1.1 then type this in to a we browser.
The Pop up will ask for a User ID and Password which for a Linksys are bith admin by defualt.
Info needed 1
If you get this far can you tells how this set up page says you are connected to the modem ?
Info needed 2
If it is a modem can you tells the same info ?
Either may say DHCP but we need to ascertain where that is coming from. A cable modem may be passing the DHCP IP given by your ISP and we would not have to worry about that.
Info for you 2
Now if the set up is Modem > Linsys > Computer I need you to find out the IP the modem is giving out or passsing on to see if it is a DHCP server.
Info needed 3
Can you connect the computer direct to the modem and repeat Item 2 please and tells that IP.
Item 3
If that IP is the same as when you go to this site http://myip.dk/ then the modem is doing pass through and all we have to do it make sure the Linksys device has the port open.
Summary.
1) You now should be able to tell and set the Ports in the Mac Firewall
2) You should be able to find out the IP your computer is getting from your router device (Same as the Log)
3) You should be able to access the router if it is a Linksys device.
4) You can tells us if the device is s router or a combined roter and Modem.
5) If there is a separate modem you will be able to tell if the IP is being passed through to the Router (when normally set up)
6) You will know what that IP is.
Please post back with the information I have asked for.
Also lets us know makes and models of any router and/or modem
10:18 PM Monday; April 9, 2007 -
We have installed HCM and CRM modules on Fusion Application 11.1.7 version.
This is 2 node architecture ie IDM components installed in one node and Fusion components installed in another node.
We are able to start the IDM components and Fusion components successfully, but when users are trying to access any task from Fusion application home page, they are getting the below error
A portlet consumer error was received for the task Manage Worker Goal Setting Lookups. Report the error details to the following owning product Goal Management.
An error was received for the task Manage Worker Goal Setting Lookups. This task is identified with the code HRG_MANAGE_WORKER_GOAL_SETTING_LOOKUPS that invokes program /WEB-INF/oracle/apps/fnd/applcore/lookups/publicUi/flow/ManageCommonLookupsTF.xml#ManageCommonLookupsTF of module code fndSetup. Review the consumer and producer logs for more details on this error.This may be related to the other issue regarding "FUSION_APPS_WSM_APPID-KEY" as the logs contains exceptions like:
oracle.wsm.policymanager.PolicyManagerException: WSM-02081 : Failed to login to perform requested action.
Please refer to document Fusion Application Service Account Password Expiration Causes Portlet Producer Errors (1486388.1) for steps on how to verify and set the password. There is also exception:
javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User FUSION_APPS_PROV_PATCH_APPID denied
This is also likely caused by an expired password, please see Fusion Apps Servers Are Not Starting Up - Password Policy Error :9000: GSL_PWDEXPIRED_EXCP :Your Password has expired (1629927.1).
Jani Rautiainen
Fusion Applications Developer Relations
https://blogs.oracle.com/fadevrel/ -
I was charged for 240,000 coins in slotmania and did not receive that many
This is a customer support forum, Apple advisors will not address your concerns here. If you need assistance, visit the link below to contact support:
http://www.apple.com/support/itunes/contact/
Maybe you are looking for
-
How to create one node for multiple cards?
I want a single minor device node to act as the interface to all instances of my pci-cards. I have the same pci-cards(pcixxx, xxx).
-
Interval Timing Issue On Solaris 10/Intel
Not sure this is the right forum for this, but I'll give it a shot. Please redirect me if you think there's a better forum. This is going to look like a "C" problem, but this really is a question about something going on in the interactions between t
-
Hi, I am currently using 4.6 C, I want to know what are the main features available in 4.7 which is not present in 4.6 C . What is UNICODE ? Thanks &Regards, Rajanidhi Rajassekeran.
-
How to maintain entry in V_T160M_CS
Hi, Can anybody help me to know, how to maintain entry in table V_T160M_CS? Raj
-
Accidently moved dv start/stop marker
hello people...so I have a clip in the editor which I used the dv start/stop tool on. I want to go through the clip and use the media manager to take out any unwanted footage. here's the issue. the clip shows all the red markings for when I stopped r