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 13:01 ------- OK, well that sounds like the expected behaviour. To mitigate this you can reduce the Timeout setting to e.g. 10 or 20 seconds. It would also be useful to add checking in more places (e.g. core_output_filter) for c->aborted to prevent repeated write timeouts. Also it's possible that using a different database library for the lockdb might help - you could expirement with using apr_dbm_open_ex instead of apr_dbm_open in dav/fs/lock.c and specifying the database type. But essentially this is a design limitation of the mod_dav_fs backend; everything has to serialize through a single lock database. Other mod_dav backends might not have this limitation, e.g. catacomb. (http://www.webdav.org/catacomb/) -- 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]
