[
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
