Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

*** PLEASE HELP ***

5 views
Skip to first unread message

Alexandre Vauthey

unread,
Jun 1, 2000, 3:00:00 AM6/1/00
to
Hi,

This is becoming a very serious problem for us !!!!!! We run a stability
test to accept /reject wl and after a few hours, the server thinks that
the client jvm is gone, for no reason. Has anyone in BEA any idea why a
server would wrongly believe that a cliant jvm is gone, while it is not
??

Exception :

Tue May 30 20:05:22 CDT 2000:<I> <RJVM> Closing connection to
BENCH2/209.110.169.106 -540294427895942277
weblogic.rjvm.PeerGoneException: JVM -540294427895942277C209.110.169.106
is gone
at weblogic.rmi.extensions.BasicRequest.sendReceive(Compiled
Code)
at weblogic.jms.common.SessionCallback_WLStub.deliver(Compiled
Code)
at weblogic.jms.server.SessionState.sendCallback(Compiled Code)
at weblogic.jms.server.SessionState.deliver(Compiled Code)
at weblogic.jms.server.SessionState.deliverMessage(Compiled
Code)
at weblogic.jms.server.TopicSessionState.deliverMessage(Compiled
Code)
at
weblogic.jms.server.TopicSessionState.processOutgoingMessages(Compiled
Code)
at weblogic.jms.server.SessionState.readQueue(Compiled Code)
at weblogic.jms.common.MessageQueue.execute(Compiled Code)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:106)
at source unknown
at source unknown
at source unknown
at source unknown
at source unknown
at source unknown
at source unknown


Steven Pozarycki

unread,
Jun 2, 2000, 3:00:00 AM6/2/00
to
Alexandre,

>> >two quick possibilities:
>> >1. the initial context is closed for some reason
>> >2. the client rjvm runs out of threads (i've seen this happen
>> > in cases where people have tests simulating multiple clients)
>> > In this case, heartbeats may not get delivered, so the server
>> > thinks the client is dead. You can try to increase
:weblogic.system.executeThreadCount to some higher number


Thanks.

Alexandre Vauthey

unread,
Jun 2, 2000, 3:00:00 AM6/2/00
to
Hi,

I seems that the one to blame is IBM jdk 118. This pb does not happen with Sun
jdk. Also, when the pb occurs, one execute thread seems to be indefinitely
waiting for data from a socket :

----------------------------------------------------------------------

"ExecuteThread-4" (TID:0xc69ef8, sys_thread_t:0x8f5870, Win32ID:0x3f,
state:R) prio=5
java.net.SocketInputStream.read(SocketInputStream.java:77)

weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:250)

weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:106)
----------------------------------------------------------------------

Thanks, Alexandre.

Steven Pozarycki wrote:

--
**************************

Alexandre Vauthey
Software Engineer

Application Networks
1050 Chestnut street
Menlo Park, CA 94025

tel: (650) 462-7220
alexandr...@appl.net

**************************

0 new messages