• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Paul Clapham
  • Devaka Cooray
  • Bear Bibeault
Sheriffs:
  • Junilu Lacar
  • Knute Snortum
  • Liutauras Vilda
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Piet Souris
Bartenders:
  • salvin francis
  • Carey Brown
  • Frits Walraven

Statful Session bean and its life

 
Ranch Hand
Posts: 560
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know how long a Stateful session bean lives in the memory. What keeps the stateful bean around?
I do have a Stateful session bean in my application creating some problem. When the user first uses the stateful session bean, the bean remote reference is stored in the user session object. Even though the user session is active and not invalidated, stateful session bean is getting timed-out. I am using weblogic 6.1 with SP2. Please help. Thanks.
Below is the exception stack trace:
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hai,
The timeout of the statefull sessin bean (passivation) is container specific.
I think if the beans method is not called for specfic time, say 30 min (again container specific) the bean will become inactive whether r not the client is having the reference
If i am wrong plz correct me
 
I'm sure glad that he's gone. Now I can read this tiny ad in peace!
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
    Bookmark Topic Watch Topic
  • New Topic