You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/12/12 18:02:44 UTC

[jira] Commented: (QPID-1533) PrincipalDatabase should have an interface has no reload()

    [ https://issues.apache.org/jira/browse/QPID-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656066#action_12656066 ] 

Martin Ritchie commented on QPID-1533:
--------------------------------------

I would suggest that adding a reload to PrincipalDatabase.
The Plain implementation would no op as it doesn't cache the data
The Base64 implementation would just need to reload the file from disk.

AMQUserManagementMBean would then just need to call PD.reload() from the reloadData() method.


> PrincipalDatabase should have an interface has no reload()
> ----------------------------------------------------------
>
>                 Key: QPID-1533
>                 URL: https://issues.apache.org/jira/browse/QPID-1533
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Management : JMX Console, Starter
>    Affects Versions: M3, M4
>            Reporter: Martin Ritchie
>
> Summary:
> The management console has a reload function which is described as 'Reloading all user data'
> Currently it only reloads the JMX Rights file 'jmxremote.access'. 
> This reload method should be updated to reload the user credentials stored in the PrincipalDatabase if they are loaded and cached at startup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.