You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "David Buchmann (Created) (JIRA)" <ji...@apache.org> on 2012/01/20 15:30:41 UTC
[jira] [Created] (JCR-3214) [Lock] weird number for "infinite"
[Lock] weird number for "infinite"
----------------------------------
Key: JCR-3214
URL: https://issues.apache.org/jira/browse/JCR-3214
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-jcr-server, locks
Reporter: David Buchmann
(this is a follow-up of JCR-3205)
i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
<D:timeout>Second-2147483</D:timeout>
this number is
2^21+50331
which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189843#comment-13189843 ]
Julian Reschke commented on JCR-3214:
-------------------------------------
DomUtil.timeoutToXml:
* Note, that {@link DavConstants#INFINITE_TIMEOUT} is not represented by the String
* {@link DavConstants#TIMEOUT_INFINITE 'Infinite'} defined by RFC 2518, due to a known
* issue with Microsoft Office that opens the document "read only" and
* never unlocks the resource if the timeout is missing or 'Infinite'.
So what happens is that the servlet internall uses MAX_INT as infinite, but then doesn't treat is as a special value, and also divides by 1000 (ms -> s).
Not sure what's the best fix here; do we know whether Office still has this problem?
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3214:
-------------------------------
Fix Version/s: (was: 2.6)
2.4
Merged to the 2.4 branch in revision 1235746.
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
> Fix For: 2.4
>
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Julian Reschke (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3214.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.6
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
> Fix For: 2.6
>
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Julian Reschke (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke reassigned JCR-3214:
-----------------------------------
Assignee: Julian Reschke
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191291#comment-13191291 ]
Julian Reschke commented on JCR-3214:
-------------------------------------
OK; part of the problem are different code paths: DavResourceImpl vs DefaultItemCollection.
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189844#comment-13189844 ]
Julian Reschke commented on JCR-3214:
-------------------------------------
Speaking of which, as far as I recall Office uses a lock time out of 300s, and just was confused when the server did not respect the timeout.
Now that the server *does* respect timeouts, the workaround may not be needed anymore.
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3214) [Lock] weird number for "infinite"
Posted by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191215#comment-13191215 ]
Julian Reschke commented on JCR-3214:
-------------------------------------
I just tried editing with word, and despite it sends a request with "Timeout: Second-3600", the same time out as above is returned; will have a look.
> [Lock] weird number for "infinite"
> ----------------------------------
>
> Key: JCR-3214
> URL: https://issues.apache.org/jira/browse/JCR-3214
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, locks
> Reporter: David Buchmann
> Assignee: Julian Reschke
>
> (this is a follow-up of JCR-3205)
> i am surprised by the davex reply to a lock request with infinite timeout (before and after the fix from JCR-3205):
> <D:timeout>Second-2147483</D:timeout>
> this number is
> 2^21+50331
> which seems pretty random to me. coincidally, this number is exactly 2^31 - 1 (2147483647) without the last 3 digits. can it be that there are some weird string operations happening on server side?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira