You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kim van der Riet (JIRA)" <ji...@apache.org> on 2016/11/28 18:25:58 UTC

[jira] [Assigned] (QPIDIT-51) Method needed to skip sensing broker type

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

Kim van der Riet reassigned QPIDIT-51:
--------------------------------------

    Assignee: Kim van der Riet

> Method needed to skip sensing broker type
> -----------------------------------------
>
>                 Key: QPIDIT-51
>                 URL: https://issues.apache.org/jira/browse/QPIDIT-51
>             Project: Apache QPID IT
>          Issue Type: Bug
>            Reporter: Chuck Rolke
>            Assignee: Kim van der Riet
>
> I'm running a test broker from [Amqp.NET Lite|https://github.com/Azure/amqpnetlite]. This broker has no claims of being fit to run in production but it is an excellent non-qpid-proton test bed for interoperability tests.
> The Lite broker has a restriction that if it is configured to use SASL then it always uses SASL regardless of how the client connects and negotiates AMQP security layers. This causes a connection problem with the current setup of QPIDIT. Although the QPIDIT tests proper do not use SASL the broker-type sensing code does. The net result is that the test can't connect to the broker.
> This issue tracks a solution for this problem. Possible resolutions at the CLI level are:
> * CLI switch to inhibit sensing the broker type.
> * CLI switch to force the test to assume a given broker type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org