[QPID-4513] [Java Client] can erroneously log "Unable to load custom SASL providers." when loaded with multiple class loaders

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.18, 0.20
• Fix Version/s: 0.21
• Component/s: JMS AMQP 0-x
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 19/Dec/12 15:14
• Updated: 20/Dec/12 23:40
• Resolved: 20/Dec/12 23:40

Description

An ERROR log "Unable to load custom SASL providers." is produced by the java client when CallbackHandlerRegistry is loaded by multiple class loaders. In this case the first class loader successfully registers the SASL providers on opening of the first connection and uses of other class loaders causes the error message because they are enable to register SASL providers because they are already registered.

The registration process should be updated to detect that all required providers are already registered and only log an error if they are not.