RemoteInvokable, can't keep reference to Stateful bean

Jan Henrik Gundelsby

unread,

Nov 26, 2001, 9:40:37 AM11/26/01

to

Hi!

I'm using WLServer 6.1, sp1, and for testing purposes my client does a
Thread.sleep(10000) between two subsequent calls to the same stateful
session bean. In the second call it seems as the bean has been removed by
the container (allthough no ejbRemove has been called). The server also
hangs after a bit after this with an OutOfMemoryError...

I guess missing out on something here?

--
jan henrik

My Stateful bean has the following settings (and stack trace attached):

<stateful-session-descriptor>
<stateful-session-cache>
<max-beans-in-cache>500</max-beans-in-cache>
<idle-timeout-seconds>600</idle-timeout-seconds>
</stateful-session-cache>
<lifecycle>
<passivation-strategy>default</passivation-strategy>
</lifecycle>
</stateful-session-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>

Start server side stack trace:
java.rmi.NoSuchObjectException: RemoteInvokable - id: '313'
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:609)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerSer
ver.java:164)
at
weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at
weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
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.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundR
equest.java:85)
at
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:134)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy2.addItem(Unknown Source)
at
no.henrik.test.PopulateShoppingCart.run(PopulateShoppingCart.java:63)

<26.nov.01 14:27:12 CET> <Error> <Dispatcher> <Error in Dispatcher
java.lang.OutOfMemoryError:
Start server side stack trace:
java.lang.OutOfMemoryError
<<no stack trace available>>
End server side stack trace

Larry Presswood

unread,

Nov 26, 2001, 12:45:32 PM11/26/01

to

I was getting simular problems and Rob's only idea was that the container
received a system exception which caused the ejb to be removed. This was
with wlserver 6.1 sp2

We have also gotten OutOfMemory as well but not at the same
time.

Jan Henrik Gundelsby

unread,

Nov 26, 2001, 3:37:35 PM11/26/01

to

Well, is there a way to verify if the container does infact receive a system
exception and did you solve your problem?

-- jan henrik

"Larry Presswood" <lpres...@charter.net> wrote in message
news:3C027FBC...@charter.net...

Larry Presswood

unread,

Nov 27, 2001, 11:17:08 AM11/27/01

to

You can turn logging up and you will see the exception in your log. No real
solution so I coded to re-try to get the remote reference on a
NoSuchObjectException. That seems to have worked but is a band aid.
Have not seen it happen again to see what system exception is being thrown.

Jan Henrik Gundelsby

unread,

Nov 28, 2001, 11:54:27 AM11/28/01

to

I solved this; my fault....

Some of the classes had been compiled with jdk130, while
I generally overall was using jdk131

--
jan henrik

"Jan Henrik Gundelsby" <j...@henrik.cc> wrote in message
news:3c0254cb$1...@newsgroups.bea.com...