• 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

Session Termination

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I have deployed an application on tomcat in which i have a class for session tracking that implements ServletContextListener,
HttpSessionAttributeListener,HttpSessionListener i m overwriting following functions
sessionCreated
sessionDestroyed
contextInitialized
attributeRemoved
and others.
on contextInitialized i have done some work and on attributeRemoved i look if any specific attribute is removed code add a record in database.
this is all happening while using tomcat 4 but as i have deployed the appllication on websphere 5 contextInitialized is working fine but attributeRemoved function is not calling on sesssion termination by webserver himself if we explicitly distroy the session then it calls but with session distroyed by server it hasn't been called.
i want to know why. Is there any configuration to set in deployment descriptor
But if i haven't configured well then why it is calling that function when we distroy the session through code. by writing sesssion.removeAttribute("attname")

Regards,
Junaid Saeed Baig
Software Engineer
Standard Chartered Bank
reply
    Bookmark Topic Watch Topic
  • New Topic