You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (Assigned) (JIRA)" <ji...@apache.org> on 2011/11/22 21:32:39 UTC
[jira] [Assigned] (QPID-3582) Client reporting "Unable to load
custom SASL providers" during connection
[ https://issues.apache.org/jira/browse/QPID-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall reassigned QPID-3582:
--------------------------------
Assignee: Keith Wall
> Client reporting "Unable to load custom SASL providers" during connection
> -------------------------------------------------------------------------
>
> Key: QPID-3582
> URL: https://issues.apache.org/jira/browse/QPID-3582
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
>
> Java Client is logging at ERROR
> {code}
> IoReceiver - localhost/127.0.0.1:5672 2011-11-03 16:31:20,547 ERROR [qpid.client.security.DynamicSaslRegistrar] Unable to load custom SASL providers.
> {code}
> during connection. This is due to the client executing a call to DynamicSaslRegistrar#registerSaslProviders twice: once from AMQConnectionDelegate_0_10 and once from ClientConnectionDelegate#createSaslClient/CallbackHandlerRegistry
> The error caused by the duplicate call is harmless and can be safely ignored.
> The call to DynamicSaslRegistrar#registerSaslProviders should be made earlier, possibly from AMQConnection or its factory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org