We are running the following scenario:
Weblogic <-- WL RMI --> JVM1 <-- WL RMI --> JVM2
I am able to connect via RMI from a client app directly to JVM2 and execute
an RMI call. When I use an EJB in Weblogic to call JVM1, which calls JVM2,
I get the following exception in JVM1. Has anyone seen this before? Please
let me know if this does not make sense.
TIA
Peter
java.util.EmptyStackException:
Start server side stack trace:
java.util.EmptyStackException
at weblogic.utils.collections.Stack.pop(Stack.java:72)
at weblogic.rjvm.InboundMsgAbbrev.getAbbrev(InboundMsgAbbrev.java:85)
at
weblogic.rjvm.MsgAbbrevInputStream.readImmutable(MsgAbbrevInputStream.java:
174)
at
weblogic.rjvm.MsgAbbrevInputStream.getMethodDescriptor(MsgAbbrevInputStream
.java:262)
at
weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:140)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:186)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:624)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.ja
va:50)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:639)
at
weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:311)
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)
End server side stack trace
:
Start server side stack trace:
java.util.EmptyStackException
at weblogic.utils.collections.Stack.pop(Stack.java:72)
at weblogic.rjvm.InboundMsgAbbrev.getAbbrev(InboundMsgAbbrev.java:85)
at
weblogic.rjvm.MsgAbbrevInputStream.readImmutable(MsgAbbrevInputStream.java:
174)
at
weblogic.rjvm.MsgAbbrevInputStream.getMethodDescriptor(MsgAbbrevInputStream
.java:262)
at
weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:140)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:186)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:624)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.ja
va:50)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:639)
at
weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:311)
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)
End server side stack trace
Peter
Peter Mularien <pmularie...@deploy.com> wrote in
news:Xns91157759A9A02p...@209.11.114.100: