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

weblogic.rjvm.PeerGoneException

2 views
Skip to first unread message

Krisztián Noll

unread,
May 24, 2001, 7:02:03 AM5/24/01
to

Hi!

We have the following exception under BEA WebLogic 5.1 SP6 and Apache + Tomcat
server enviroment:

java.rmi.RemoteException: ; nested exception is:
weblogic.rjvm.PeerGoneException: Peer requested connection shutdown
weblogic.rjvm.PeerGoneException: Peer requested connection shutdown
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at gft.onlaw.usermanagement.dict.DictBeanEOImpl_WLStub.getAllAnrede(DictBeanEOImpl_WLStub.java:425)
at gft.onlaw.usermanagement.dict.DictBeanEOImpl_ServiceStub.getAllAnrede(DictBeanEOImpl_ServiceStub.java:177)
at mm._0002fmm_0002fmm_0005fdetail_0002ejspmm_0005fdetail_jsp_0._jspService(_0002fmm_0002fmm_0005fdetail_0002ejspmm_0005fdetail_jsp_0.java:725)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:177)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
at org.apache.tomcat.core.Handler.service(Handler.java:286)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:166)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)

Does anybody have an idea why do we have this message? After the server restart
it works correctly.

Thank you:

Krisztián Noll
(k...@gft.com)
GFT, Hungary

0 new messages