Caldarale, Charles R wrote:
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Subject: Re: ConcurrentModificationException on tomcat
cluster with SimpleTcpClusterstrategy
given that the session should represent a client state,
and by the time the cluster tries to serialize it, the
request is over.
That ignores the situation where multiple requests from the same client
are being processed concurrently. What are the conditions that provoke
replication (and therefore serialization)? What mechanism is provided
for request processors to synchronize with the replicator?
that is correct, we thought of this scenario and decided that we
wouldn't support it.
the problem with the scenario above is not only that the same client can
have multiple requests, it can have multiple requests hitting different
nodes in the cluster.
this would require implement distributed locking and there is no way of
doing that without suffering too much of a performance degradation.
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]
