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=43163>. 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=43163 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-24 04:09 ------- (In reply to comment #0) > A wild guess: The workflow overview makes it possible to fire a new request > before the previous request is finished. This results in a new thread and for > each thread a new session. These sessions can block one another (????) Yes, I think this is the case. Unfortunately I don't see how this can be changed. In a multi-threaded environment which allows to modify the same resources by different threads you'll always run into locking issues. Did you end up with a corrupted repository? Otherwise I'd say this is a limitation of the architecture and we can't do anything about it in the short term. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
