qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QPID-3582) Client reporting "Unable to load custom SASL providers" during connection
Date Thu, 03 Nov 2011 16:41:32 GMT
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
            Priority: Minor

Java Client is logging at ERROR

IoReceiver - localhost/ 2011-11-03 16:31:20,547 ERROR [qpid.client.security.DynamicSaslRegistrar]
Unable to load custom SASL providers.

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

View raw message