On Fri Apr 18 15:29:16 CEST 2008 Christopher Schultz <[EMAIL PROTECTED]> wrote:
Ronald,
Ronald Klop wrote:
> But why does the client still have the same session after one node
> shuts down. The session doesn't live on one node. It lives as long as
> the cluster lives.
That's a good point.
>
On Fri Apr 18 14:16:33 CEST 2008 Christopher Schultz <[EMAIL PROTECTED]> wrote:
Ronald,
Ronald Klop wrote:
> Yes, I know how to work around the problem. But I don't like
> workarounds. All implementations I can think of are very fragile. What
> if somebody stops my Tomcat with kill one day?
Yes, I know how to work around the problem. But I don't like workarounds. All
implementations I can think of are very fragile. What if somebody stops my
Tomcat with kill one day?
My session isn't destroyed, so I don't understand why the event is thrown.
Ronald.
On Thu Apr 17 15:49:49 CEST 200
]
Sent: Thursday, April 17, 2008 9:50 AM
To: Tomcat Users List
Cc: Filip Hanik - Dev Lists
Subject: Re: sessionListener.sessionDestroyed is called on shutdown of a node
in the cluster
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald,
Ronald Klop wrote:
| In sessionDestroyed I register the user as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronald,
Ronald Klop wrote:
| In sessionDestroyed I register the user as logged out.
|
| How can I know if sessionDestroyed is called from session.invalidate()
| from the real expiration of the session or shutdown of one cluster node?
Are your shutdo
> >
>> > No virus found in this incoming message.
>> > Checked by AVG.
>> > Version: 7.5.519 / Virus Database: 269.21.7/1334 - Release Date:
>> 3/18/2008 8:52 PM
>> >
>>
>>
>> -------------------
gt; > No virus found in this incoming message.
>> > Checked by AVG.
>> > Version: 7.5.519 / Virus Database: 269.21.7/1334 - Release Date:
>> 3/18/2008 8:52 PM
>> >
>>
>>
>> ---------------------
>
In sessionDestroyed I register the user as logged out.
How can I know if sessionDestroyed is called from session.invalidate() from the
real expiration of the session or shutdown of one cluster node?
Ronald.
On Thu Mar 20 17:40:26 CET 2008 Tomcat Users List
wrote:
It's expected behavior, ses
It's expected behavior, sessions will always expire on the local node
during a graceful shutdown.
expireSessionsOnShutdown="false" simply means that we don't expire
sessions in the remote nodes
Filip
Ronald Klop wrote:
Hello,
When I shutdown a node in my cluster (tomcat 5.5.26) sessionDes
Hello,
When I shutdown a node in my cluster (tomcat 5.5.26) sessionDestroyed is called
on all SessionListeners on that node.
But I'm running a cluster, so one node stopping doesn't mean the session is
destroyed.
My understanding is that expireSessionsOnShutdown="false" by default and I
don't
10 matches
Mail list logo
