[
https://issues.apache.org/jira/browse/ARTEMIS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628091#comment-14628091
]
Ted Ross commented on ARTEMIS-155:
----------------------------------
The only way I've been able to reproduce this symptom is using qpid-dispatch
(from trunk) and the proton 0.10 alpha (or master).
The Dispatch configuration has the following snippet:
{noformat}
connector {
addr: 127.0.0.1
port: 5672
role: on-demand
saslMechanisms: ANONYMOUS
name: artemis
}
linkRoutePattern {
prefix: queue.
connector: artemis
}
{noformat}
When run against Artemis (default config), the open frame never comes back from
the broker and dispatch does not activate the link-route-pattern as a result.
> Incoming AMQP connection using "cut-through" ANONYMOUS SASL fails
> -----------------------------------------------------------------
>
> Key: ARTEMIS-155
> URL: https://issues.apache.org/jira/browse/ARTEMIS-155
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 1.0.0
> Reporter: Ted Ross
>
> When connecting an AMQP 1.0 connection to the broker using SASL ANONYMOUS,
> the following exchange occurs:
> {noformat}
> Client Broker
> init(SASL) ->
> sasl.init (ANON) ->
> init(AMQP) ->
> open ->
> <- init(SASL)
> <- sasl.mechanisms
> <- sasl.outcome(OK)
> <- init(AMQP)
> socket closed by broker after timeout
> {noformat}
> It appears the the broker doesn't process the open frame.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
