• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

statefull session bean

 
Ranch Hand
Posts: 1491
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In the statefull session beans deployment descriptor, i mentioned session timeout 20 secs. But my Transaction is running more than 20 secs.. Whether it throws System exception / Application exception ?
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Your bean is not going to time out while it is active. The container only removes inactive session beans after the specified time out period.
 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is just an extension to Paul message.

If bean is in Transaction, Container does not persist the bean or remove bean from pool, even you set timeout. Use web containter maintain the session invalidation to solve this problem.

Or you can keep the wait time in session bean, you can know when the session begins transaction by checking afterBegin() method of SessionSynchronization interface (In case of CMP only). Wait for certain time and roll back transaction EJBContext.setRollbackOnly().


In case of BMT you can roolback your tranasaction by explicitly calling rollback after certain time.

Using session management at webcontainer level is better stretegy.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic