[
https://issues.apache.org/jira/browse/QPID-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy closed QPID-4513.
----------------------------
> [Java Client] can erroneously log "Unable to load custom SASL providers."
> when loaded with multiple class loaders
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4513
> URL: https://issues.apache.org/jira/browse/QPID-4513
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.18, 0.20
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: 0.21
>
> Attachments:
> 0001-QPID-4513-Add-check-to-detect-registered-SASL-provid.patch,
> 0001-QPID-4513-improve-client-handling-of-discovery-that-.patch,
> MyClassLoader.java
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
