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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-10-26 14:57 ------- As mentioned a long long long time ago :) If you have two threads per session, consider the following scenario: Thread A goes to server S1 and Thread B goes to server S2, your session replication will now be faulty since there is no distributed locking. Adding in synchronization here, would mean that we are letting the user think that concurrent access is ok, which it isn't. What I do agree with is that the readExternal/writeExternal methods could be synchronized, to avoid corrupted methods. You must still realize, that you have two concurrent requests, there is nothing that guarantees the order of them. Hence synchronizing the entire class does not resolve anything really. Your fundamental problem is still that you have more than one thread modifying the session. I am marking the bug invalid, cause we are not supporting distributed locking hence could never put in a complete fix. A synchronized workaround Filip --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]