PeerGoneException?

[George A. Withers, Jr.]

I have an application where I have a command-line utility run on demand and
send a message via JMS managed on a Weblogic 4.5 server. The message is
received and processed and the client exits. After the client exits the
Weblogic console reports a "PeerGoneException". This doesn't seem to cause
anything to go wrong but can this be avoided somehow? Is there something I
should call in the command-line application?

The exception (for what it's worth) follows.

Thanks,

George Withers
Revenio, Inc.

Fri Mar 31 18:09:57 EST 2000:<I> <RJVM> Closing connection to
localhost/127.0.0.1 -7873292179747081968
weblogic.rjvm.PeerGoneException: JVM -7873292179747081968C10.0.3.35 is gone
at
weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
at
weblogic.jms.common.SessionCallback_WLStub.deliver(SessionCallback_WLStub.ja
va:89)
at weblogic.jms.server.SessionState.sendCallback(SessionState.java,
Compiled Code)
at weblogic.jms.server.SessionState.deliver(SessionState.java,
Compiled Code)
at
weblogic.jms.server.SessionState.deliverMessage(SessionState.java, Compiled
Code)
at
weblogic.jms.server.TopicSessionState.deliverMessage(TopicSessionState.java,
Compiled Code)
at
weblogic.jms.server.TopicSessionState.processOutgoingMessages(TopicSessionSt
ate.java, Compiled Code)
at weblogic.jms.server.SessionState.readQueue(SessionState.java,
Compiled Code)
at weblogic.jms.common.MessageQueue.execute(MessageQueue.java,
Compiled Code)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException: Undeclared checked exception
- with nested exception:
[weblogic.rjvm.PeerGoneException: JVM -7873292179747081968C10.0.3.35 is
gone]
at
weblogic.jms.common.SessionCallback_WLStub.deliver(SessionCallback_WLStub.ja
va:105)
at weblogic.jms.server.SessionState.sendCallback(SessionState.java,
Compiled Code)
at weblogic.jms.server.SessionState.deliver(SessionState.java,
Compiled Code)
at
weblogic.jms.server.SessionState.deliverMessage(SessionState.java, Compiled
Code)
at
weblogic.jms.server.TopicSessionState.deliverMessage(TopicSessionState.java,
Compiled Code)
at
weblogic.jms.server.TopicSessionState.processOutgoingMessages(TopicSessionSt
ate.java, Compiled Code)
at weblogic.jms.server.SessionState.readQueue(SessionState.java,
Compiled Code)
at weblogic.jms.common.MessageQueue.execute(MessageQueue.java,
Compiled Code)
at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
Code)

[Zach]

do you set up a listener and a not clean it up before you exit? do you
close your session and your connection before you exit. it looks like it
is trying to delover a message to your listener which is no longer there.

_sjz.

"George A. Withers, Jr." <wit...@net1plus.com> wrote in message
news:8c3atj$ch2$1...@bayview.weblogic.com...