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/10/24 18:07:44 UTC
[jira] Updated: (QPID-1390) Authentication Manager does not
correctly unregister custom SASL providers on shutdown
[ https://issues.apache.org/jira/browse/QPID-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1390:
---------------------------------
Status: Ready To Review (was: In Progress)
> Authentication Manager does not correctly unregister custom SASL providers on shutdown
> --------------------------------------------------------------------------------------
>
> Key: QPID-1390
> URL: https://issues.apache.org/jira/browse/QPID-1390
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M3
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M4
>
>
> Summary:
> The AuthenticationManger (PrincipalDatabaseAuthenticationManager) registers custom SASL servers on startup. However, on shutdown of the ApplicationRegistry it does not remove these. This could be a cause of the curious SASL related failures in SimpleACLTest.
> On ApplicationRegistry close all the managers should get a notification so that they may perform any additional clean up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.