Caldarale, Charles R wrote:
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Subject: Re: ConcurrentModificationException on tomcat
cluster with SimpleTcpClusterstrategy
that is correct, we thought of this scenario and decided that we
wouldn't support it.
Not unreasonable to avoid the performance hit for the 99% usual cases.
However, I'd still like to know what triggers the session replication
across the nodes of the cluster. If it's some particular set of API
calls (e.g., closing the output stream), then it might be possible for
applications that need it to synchronize their own behavior with regards
to the session, and not run the risk of interfering with the
replication.
hey Chuck,
quite simple. Replication is triggered by the "ReplicationValve", ie
when the request is complete (complete defined/interpreted by the
servlet API as the thread backing out-in Tomcat's API this is when the
invoke method to the
next valve down the chain is complete) the changes in the session are
then extract through a diff based on setAttribute/removeAttribute events
and are propagated.
removeAttribute events are propagated as events, not serialized data, so
the same remove happens on the other nodes.
Filip
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
