[
https://issues.apache.org/jira/browse/OAK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732019#comment-13732019
]
Michael Dürig commented on OAK-938:
-----------------------------------
bq. why does the tentative fix contain modifications to the UserManagerImpl in
oak-core?
Refactoring accident. I could revert but as we all tend to have different
settings of how imports are ordered this wont hold for long.
bq. anonymous inner class
See my previous comment. I'll follow up with that.
> UserManager does not honour session refresh settings
> ----------------------------------------------------
>
> Key: OAK-938
> URL: https://issues.apache.org/jira/browse/OAK-938
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Antonio Sanso
> Assignee: Michael Dürig
> 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
