On 17/11/2009 11:31, Imad Hachem wrote:

Dear Pid,

Thanks for your reply.
>
But can you specify exactly which Servlets API method to use?

The link I sent had some code in it, did you read it?

Note that Tomat-5.5.12 is deployed on Production environment and we are not 
facing major issues.

But you might be facing some security ones.

I will appreciate if you can adivse to which Tomcat Stable version we should 
Migrate taking in consideration that Tomcat Cluster is used in our environment 
as well.

The latest: Tomcat 5.5.28. Same app, many bugfixes. Your version was released September 2005, over 4 years ago (that's 28 internet years).

It's not good practice to avoid upgrading for that long.


p








Best Regards,
Imad Hachem

System Engineer




Date: Tue, 17 Nov 2009 10:15:58 +0000
From: p...@pidster.com
To: users@tomcat.apache.org
Subject: Re: MISC; Tomcat-5.5.12; After one Tomcat Cluster node shutdown, 
sessionDestroyed been called before contextDestroyed

On 17/11/2009 04:14, Imad Hachem wrote:

Dear all,

I am using Tomcat-5.5.12 as Clustering nodes, and after one node
shutdown sessionDestroyed is called before contextDestroyed.

Are you still using 5.5.12? Hasn't anyone advised you to upgrade to a
newer version yet?

I think it's perfectly reasonably to call sessionDestroyed() before
contextDestroyed().

How can I know if sessionDestroyed is called from session.invalidate()
from the real expiration of the session or shutdown of one cluster node?

You can't know this directly from the Servlet API methods.

Note that on sessionDestroyed event, I am using a Logout behavior to
logout my users from the DATABASE.

I have tried to set a KEY on the context (or application scope) to check
on it during the sessionDestroyed event, but it seems the context is
destroyed after the session destroy event.

This comes up not infrequently on the list, the archives have more
information:

http://old.nabble.com/Re%3A-sessionListener.sessionDestroyed-is-called-on-shutdown-of-a-node-in-the-cluster-p16746969.html

Is there any event listener that I can use before the sessionDestroyed to 
differentiate if one cluster node has been shutdown or my session has been 
expired?

Or is how to configure the contextDestroy to be called before the sessions 
destroy?

No, contextDestroyed() means that the web application itself has been
stopped, this is mandated by the Servlet Spec.


p


Thanks in advance for your help.

Best Regards,
Imad Hachem

System Engineer



_________________________________________________________________
Windows Live: Make it easier for your friends to see what you’re up to on 
Facebook.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

                                        
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to