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=36636>. 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=36636 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-14 12:43 ------- Regarding the other behaviour, I am still investigating that. There are more readlocks now, but it does acquire a writelock for the DavLockDB somewhere in the code, I'm trying to find the place right now. You are right, it decreases chances that the behaviour will reoccur as described, but for one, there are additional writelocks on the DB (which might not be necessary either) and also, shouldn't writev_it_all _not block_ no matter how much data you push in? As I see it, fixing mod_dav will reduce the chances that the problem will come about (ideally only blocking one child instead of all of them if no write locks are required), but do you think it is possible to stop this one child from blocking? -- 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]
