I have an app that will hold a reference to a Stateful SessionBean for an extended period of time(hopefully forever). I've noticed that after a period of time, the reference becomes invalid. I assume that it's timing out.
Is there a was to tell that the remote reference has become stale other than calling a method on it and having it throw an Exception?
Thanks in advance.
-
Stale SessionBean Reference (4 messages)
- Posted by: Brett Fieber
- Posted on: June 20 2000 11:26 EDT
Threaded Messages (4)
- exceptions by Ed Roman on June 22 2000 11:28 EDT
- exceptions by Brett Fieber on June 23 2000 17:30 EDT
- Stale SessionBean Reference by Akash Bansal on July 14 2000 10:59 EDT
- Stale SessionBean Reference by T J on May 23 2001 17:02 EDT
-
exceptions[ Go to top ]
- Posted by: Ed Roman
- Posted on: June 22 2000 11:28 EDT
- in response to Brett Fieber
I've always relied on the exceptions (I believe the exception is a NoSuchObjectException). The only other way I can think of is if there was perhaps a vendor-specific stub method that the Stub class exposed but was not part of the remote interface, but I've never used anything like this. -
exceptions[ Go to top ]
- Posted by: Brett Fieber
- Posted on: June 23 2000 17:30 EDT
- in response to Ed Roman
Thanks for your response.
That's pretty much what I expected, but was hoping I'd missed something. -
Stale SessionBean Reference[ Go to top ]
- Posted by: Akash Bansal
- Posted on: July 14 2000 10:59 EDT
- in response to Brett Fieber
Hi,
If you are using a Weblogic Server. You should set the value of idle-timeout-seconds (as per requirements) in the weblogic-ejb-jar.xml file. I think that would solve your problem.
Akash.
-
Stale SessionBean Reference[ Go to top ]
- Posted by: T J
- Posted on: May 23 2001 17:02 EDT
- in response to Brett Fieber
What happens when it does become stale? I'm storing a rference to a OrderEntry ejb and, after a while, it disappears form the session and, when I go to pull the reference, it is null. Thanks