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 19:31:46 UTC

[jira] Assigned: (QPID-1394) Client and Broker compete to register SASL plugins when run InVM

     [ https://issues.apache.org/jira/browse/QPID-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie reassigned QPID-1394:
------------------------------------

    Assignee: Rob Godfrey  (was: Martin Ritchie)

Hi Rob can you review this change please. The MultipleJCAProviderRegistration class tests that both broker and client can now register their JCAProvider and the client has been updated to print an error if it is unable to register it the custom providers as this may indicate a reason for the connection failure.

> Client and Broker compete to register SASL plugins when run InVM
> ----------------------------------------------------------------
>
>                 Key: QPID-1394
>                 URL: https://issues.apache.org/jira/browse/QPID-1394
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Rob Godfrey
>
> Summary:
> Due to the way that the multiple JCAProviders (QPID-1393) register SASL plugins it is not possible to register both broker and client components in the single VM hence InVM testing of Qpid specific SASL authentication is not possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.