[
https://issues.apache.org/jira/browse/OAK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729579#comment-13729579
]
Michael Dürig commented on OAK-938:
-----------------------------------
The root cause of this is the {{IdentifierManger}} being tied to the {{Root}}
(and its associated revision of the repository) that was passed to its
constructor. That {{Root}} instance doesn't honour the refresh setting passed
to the session in the first place. Not sure yet how to best proceed here since
the session refresh setting is applied at {{NodeDelegate}} level an has no
meaning at {{Root}} level.
> Issue with UserManager#getAuthorizable with multiple sessions
> -------------------------------------------------------------
>
> Key: OAK-938
> URL: https://issues.apache.org/jira/browse/OAK-938
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Antonio Sanso
> Attachments: OAK-938-patch, OAK-938-test-patch.txt
>
>
> When UserManager#getAuthorizable is used in a multiple sessions environment
> where a session creates an user and the other (already acquired) session
> tries to get the authorizable null is returned (even if the other session
> uses refresh-interval to 0)
> unit test to follow
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
