[Bug 36636] database write lock taken for PROPFIND operations

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=36636

Wim Lewis <***@omnigroup.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
OS|Linux |All
Hardware|PC |All

--- Comment #20 from Wim Lewis <***@omnigroup.com> ---
I can confirm this problem still exists in the 2.4.x releases and in 2.5/trunk
(r1734315).

A workaround is to use mod_buffer to buffer the entire PROPFIND response before
sending it to the client:

<If "toupper(%{REQUEST_METHOD}) == 'PROPFIND'" >
SetOutputFilter BUFFER
</If>

Of course this increases memory use and request latency, but it does prevent a
single client on a slow connection from locking up the entire DAV repository.

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=36636

Wim Lewis <***@omnigroup.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@omnigroup.com

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=36636

William A. Rowe Jr. <***@apache.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |MassUpdate
Resolution|--- |LATER
Status|NEW |RESOLVED

--- Comment #21 from William A. Rowe Jr. <***@apache.org> ---
Please help us to refine our list of open and current defects; this is a mass
update of old and inactive Bugzilla reports which reflect user error, already
resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all
development and patch review of the 2.2.x series of releases. The final release
2.2.34 was published in July 2017, and no further evaluation of bug reports or
security risks will be considered or published for 2.2.x releases. All reports
older than 2.4.x have been updated to status RESOLVED/LATER; no further action
is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd
feature, an unexpected server behavior, problems building or installing httpd,
or working with an external component (a third party module, browser etc.) we
ask you to start by bringing your question to the User Support and Discussion
mailing list, see [https://httpd.apache.org/lists.html#http-users] for details.
Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that
you retest using a modern httpd release (2.4.33 or later) released in the past
year. If it can be reproduced, please reopen this bug and change the Version
field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the
current httpd server software release is greatly appreciated.

[b***@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=36636

Christophe JAILLET <***@wanadoo.fr> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Keywords|MassUpdate |
Version|2.0.54 |2.4-HEAD
Resolution|LATER |---

--- Comment #22 from Christophe JAILLET <***@wanadoo.fr> ---
Confirmed in 2.4.x in comment 20.
So re-opening and updating the Version to 2.4-HEAD