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=26913>. 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=26913 Lack of non-transactional history counter. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2004-03-30 13:48 ------- Both double URIs and deadlocks causing conflicts are now eliminated. After the changes I could no longer reproduce the observed symptoms. - Double URIs: Fixed by a HACK. Caching for history is selectively switched off in ExtendedStore. This causes read locks to be propagated to the physical stores - Deadlocks: When caching for history is switched off deadlocks can occur when two transaction first read the history counter before one has written it. In this case none of them can augment to write lock. Fixed by having read and incremented write in a synchronized block --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
