kill -9 my friend :)
Andrew Hole wrote:
The valueUnbound is NOT being propagated from the TC instance shutting
down across the cluster. The valueunbound is executed when I do the shutdown
of an TC instance (session logout tracking was done - database record
inserted). After that I still work
Hi!
Why is session unbound called after cluster failover?
Two more questions:
-- In a scenario with two nodes, if I shutdown one, the other is instantly
ready to receive and respond to requests, or it is necessary to wait a
while?
In a procuction scenario we cannot wait, because requests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| Why is session unbound called after cluster failover?
What value is being unbound?
| Two more questions: -- In a scenario with two nodes, if I shutdown
| one, the other is instantly ready to receive and respond
PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| Why is session unbound called after cluster failover?
What value is being unbound?
| Two more questions: -- In a scenario with two nodes, if I shutdown
| one, the other is instantly ready to receive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| Well, our class USER implements HttpSessionBindingListener,
| Serializable and when failover happens valueUnbound is executed(public
| void valueUnbound(HttpSessionBindingEvent event)) - valueUnbound is a
| method of
It happens on both. Valueunbound is executed on old server when tomcat
is stopped, and is executed on new server when I execute logout (or if
I shutdown tomcat). We only want that new server executes
valueunbound.
Could you help?
Thanks a lot
A
On 2/25/08, Christopher Schultz [EMAIL PROTECTED]
the stack trace idea is a good idea, and you can post it here
Filip
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| Well, our class USER implements HttpSessionBindingListener,
| Serializable and when failover happens valueUnbound is
Stack trace of old server:
java.lang.Exception
at mni.core.sessions.User.valueUnbound(User.java:95)
at
org.apache.catalina.cluster.session.DeltaSession.removeAttributeInternal(DeltaSession.java:1589)
at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| It happens on both. Valueunbound is executed on old server when
| tomcat is stopped, and is executed on new server when I execute
| logout (or if I shutdown tomcat).
That behavior seems entirely consistent with what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| I think you need to manage your events in a way that takes into account
| the fact that valueUnbound will can be called by other members in the
| cluster.
| It is not a easy task, rigth?
| Could you be more specific in
I think you need to manage your events in a way that takes into account
the fact that valueUnbound will can be called by other members in the
cluster.
It is not a easy task, rigth?
Could you be more specific in the way of developing it?
Thanks
On Mon, Feb 25, 2008 at 7:27 PM, Christopher Schultz
Well, valueunbound is executed on both TC.
we are doing session replication, lets say we have a 5 (for example) node
cluster. When a user logs on, his/her session will be replicated on 5
tomcats. When he/she logs out, you only want track that the user has logged
out once, not 5 times (our logout
Not sure if I followed this thread closely enough. It looks like
sometimes you are talking about node shutdown (your example stack), and
sometimes about user logout (your last message).
Concerning user logout (resp. session expiration/invalidation): the
attribute notifyListenersOnReplication
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew,
Andrew Hole wrote:
| Well, valueUnbound is executed on both TC.
You mentioned that. The valueUnbound is being propagated from the TC
instance shutting down across the cluster, right? I can't seem to get a
straight answer to that question.
Christopher Schultz schrieb:
Of course, bringing down one container in a cluster will have the effect
of logging everyone out at once, even if they are on other servers as well.
No, unless you set expireSessionsOnShutdown which is false by default,
shutdown of a node should not expire the
The valueUnbound is NOT being propagated from the TC instance shutting
down across the cluster. The valueunbound is executed when I do the shutdown
of an TC instance (session logout tracking was done - database record
inserted). After that I still work with this session on the active node ...
Hi!
Why is session unbound called after cluster failover?
Two more questions:
-- In a scenario with two nodes, if I shutdown one, the other is instantly
ready to receive and respond to requests, or it is necessary to wait a
while?
In a procuction scenario we cannot wait, because requests
17 matches
Mail list logo
