[
https://issues.apache.org/jira/browse/OAK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731984#comment-13731984
]
Michael Dürig commented on OAK-938:
-----------------------------------
Tentative fix at revision 1511302. [~anchela], [~jukkaz] please review whether
this is what you had in mind when we discussed this. I will then follow up with
further tweaks:
* pass the refreshed root through {{SessionOperation.perform()}} instead of
relying on side effects,
* leverage the precondition check facility of {{SessionOperation}} for
replacing {{UserManager.checkLive()}},
* promote the anonymous {{UserManager}} implementation in {{SessionContext}} to
a top level class and make {{UserManagerImpl}} the delegate,
* apply similar transformations to other affected areas (potential candidates:
PrincipalManager, VersionManager, ACManager, PermissionProvider,
ObservationManager, and PrivilegeManager)
> 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
