You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by bu...@apache.org on 2004/09/17 17:59:03 UTC
DO NOT REPLY [Bug 31156] -
Lock on null resources does not clean on timeout
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=31156>.
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=31156
Lock on null resources does not clean on timeout
luetzkendorf@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From luetzkendorf@apache.org 2004-09-17 15:59 -------
I agree that expired lock null resources must disappear after timeout.
I think I have fixed this issure. The problem was at first, that
AbstractWebdavMethod checks each resource for expired locks and removes
null locks .... but the executeRequest method exits with an WebdavException
(as expected - Not Found) and so the changes regarding the expired locks
are not commited. Thats why they are lost and the removed null resource
reappears.
The second point was: the formerly described check for expired locks only
happens for the requested resource not for its descendants. So propfind lists
expired locks as member.
For both problems I added a testcases which now are passing successfully and
the other still too(:-). So I think I can close this.
Stefan
For the test cases see
functional/lock/null-resources/lockNullFile_Timeout.xml
functional/lock/null-resources/lockNullFile_Timeout2.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org