It's not a secret anymore!
The moose likes Servlets and the fly likes sessionDestroyed() not called Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "sessionDestroyed() not called" Watch "sessionDestroyed() not called" New topic

sessionDestroyed() not called

spratap singh

Joined: Aug 27, 2004
Posts: 5

I have a web application.
The sessionDestroyed() is not called even after session timeout.
I have following settings in my web.xml and weblgic.xml :
web.xml :

weblogic.xml :

I am in a Cluster environment.
Please help why the function has not been called as ideally it shuould be called.

Please help me.

Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33125

You need to add something like the following in your web.xml

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
spratap singh

Joined: Aug 27, 2004
Posts: 5

Thanks a lot for you suggestion.
Actually I am already using that .
What is surprising is sessionCreated() is called from the same listener but
sessionDestroyed() is not called.

Please help.

Srinivasa Raghavan
Ranch Hand

Joined: Sep 28, 2004
Posts: 1228
I'm facing the same problem when the application gets undeployed, but it works well when session timed out or session gets invalidated ..
[ October 06, 2004: Message edited by: srini vasan ]

Thanks & regards, Srini
MCP, SCJP-1.4, NCFM (Financial Markets), Oracle 9i - SQL ( 1Z0-007 ), ITIL Certified
Rahul kapoor

Joined: Sep 21, 2004
Posts: 16

Please check. These two statements are made by two different people.

Let clarity prevail.
Adeel Ansari
Ranch Hand

Joined: Aug 15, 2004
Posts: 2874
yeah thanks rahul deleted my post.

Hey Spratap,
Have you tried to invalidate the session inside sessionCreated()? just give it a try.

Hey Srini,
Are you too in a clustered environment? if yes then you can help him, because it is working with you on sessionTimeOut and even with session.invalidate().
[ October 07, 2004: Message edited by: adeel ansari ]
I agree. Here's the link:
subject: sessionDestroyed() not called
It's not a secret anymore!