• 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown


Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I have two different WAR's in my web Application that is deployed on IBM WebSphere Server 6.1. Currently I maintain shared session between the two WAR's based upon a db value set as the user logs in the application; User can login from either of the WAR's. I have a sessionListnere in place to destroy session as the session time out value is reached if the suer is inactive for the timeout value set in web.xml

When I select the option of "Shared Session Context" in the application descriptor to share between two WAR's I can login to the application but as the session timeout is reached my Listener code does not work, the sessionDestroyed() method is not called, thus the sesion are not invalidated.

Can some one help on how to ensure that sessionDEstroyed() method is called when I check the "Shared Session Context " option in application descriptor setting in Websphere6.1.

Can you shoot lasers out of your eyes? Don't look at this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic