tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31328] - DeltaRequest unable to handle two concurrent requests per session
Date Tue, 26 Oct 2004 18:54:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31328>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31328

DeltaRequest unable to handle two concurrent requests per session





------- Additional Comments From rainer.jung@kippdata.de  2004-10-26 18:54 -------
Filip,

I agree that distributed locking is out of reach. But please consider the following:

carefully designed clusters will use sticky session routing via mod_jk. So as
long as the primary node ist available there will be no parallel usage of
sessions via different nodes.

But even then and even without frames etc. we see every now and then
unintentional parallel usage by people e.g. using Return and afterwards the
mouse button to send a form to the server. This will result in double sending of
the form and this should not technically corrupt the session objects. Of course
there is no guarantee, that all session data still makes sense for the application.

So at least we should not corrupt the LinkedLists in the DeltaRequest.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message