[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()
[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated JCR-3495: - Fix Version/s: 2.4.5 > Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout() > -- > > Key: JCR-3495 > URL: https://issues.apache.org/jira/browse/JCR-3495 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: nodetype, security >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 2.4.5, 2.6.1, 2.7 > > Attachments: JCR-3495.patch > > > PrivilegeRegistry and NodeTypeRegistry contains weak references to a session > even if the session is explicitly logged out. While PrivilegeRegistry is > designed that way and currently does not allow a client to unregister a > listener, the NodeTypeRegistry does have a method to unregister, but it is > not used by NodeTypeManagerImpl. > This puts extra load on the finalizer and should be avoided. -- 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
[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()
[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated JCR-3495: - Fix Version/s: 2.6.1 backported to 2.6 with rev 1479817. > Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout() > -- > > Key: JCR-3495 > URL: https://issues.apache.org/jira/browse/JCR-3495 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: nodetype, security >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 2.6.1, 2.7 > > Attachments: JCR-3495.patch > > > PrivilegeRegistry and NodeTypeRegistry contains weak references to a session > even if the session is explicitly logged out. While PrivilegeRegistry is > designed that way and currently does not allow a client to unregister a > listener, the NodeTypeRegistry does have a method to unregister, but it is > not used by NodeTypeManagerImpl. > This puts extra load on the finalizer and should be avoided. -- 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
[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()
[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3495: -- Resolution: Fixed Fix Version/s: 2.7 Status: Resolved (was: Patch Available) Committed patch in revision: 1445122. > Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout() > -- > > Key: JCR-3495 > URL: https://issues.apache.org/jira/browse/JCR-3495 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: nodetype, security >Reporter: Marcel Reutegger >Priority: Minor > Fix For: 2.7 > > Attachments: JCR-3495.patch > > > PrivilegeRegistry and NodeTypeRegistry contains weak references to a session > even if the session is explicitly logged out. While PrivilegeRegistry is > designed that way and currently does not allow a client to unregister a > listener, the NodeTypeRegistry does have a method to unregister, but it is > not used by NodeTypeManagerImpl. > This puts extra load on the finalizer and should be avoided. -- 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
[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()
[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3495: -- Status: Patch Available (was: Open) > Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout() > -- > > Key: JCR-3495 > URL: https://issues.apache.org/jira/browse/JCR-3495 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: nodetype, security >Reporter: Marcel Reutegger >Priority: Minor > Attachments: JCR-3495.patch > > > PrivilegeRegistry and NodeTypeRegistry contains weak references to a session > even if the session is explicitly logged out. While PrivilegeRegistry is > designed that way and currently does not allow a client to unregister a > listener, the NodeTypeRegistry does have a method to unregister, but it is > not used by NodeTypeManagerImpl. > This puts extra load on the finalizer and should be avoided. -- 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
[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()
[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3495: -- Attachment: JCR-3495.patch Proposed changes. > Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout() > -- > > Key: JCR-3495 > URL: https://issues.apache.org/jira/browse/JCR-3495 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: nodetype, security >Reporter: Marcel Reutegger >Priority: Minor > Attachments: JCR-3495.patch > > > PrivilegeRegistry and NodeTypeRegistry contains weak references to a session > even if the session is explicitly logged out. While PrivilegeRegistry is > designed that way and currently does not allow a client to unregister a > listener, the NodeTypeRegistry does have a method to unregister, but it is > not used by NodeTypeManagerImpl. > This puts extra load on the finalizer and should be avoided. -- 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
