[
https://issues.apache.org/jira/browse/QPID-8571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8571.
--------------------------------
Assignee: (was: Robert Godfrey)
> [Broker-J] Non-unique consumer tags created for AMPQ 0-9-1
> ----------------------------------------------------------
>
> Key: QPID-8571
> URL: https://issues.apache.org/jira/browse/QPID-8571
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-8.0.2
> Reporter: Thorsten Meinl
> Priority: Major
> Fix For: qpid-java-broker-9.2.1
>
>
> The AMQP 0-9-1 specification states that the broker creates a unique consumer
> tag upon {{consume}} when the client provides an empty consumer tag. The tags
> are unique per channel.
> However, Qpid creates non-unique tags when consumers target different queues.
> In our case two consumers created via the same channel for two different
> queues both have the same auto-generated tag {_}sgen_1{_}. This becomes an
> issue during auto-recovery using the RabbitMQ Java client. It has an internal
> map with consumer tags as keys that is used during auto-recovery. Now, if two
> consumers get the same tag from the broker the second consumer will override
> the first consumer and thus will not get restored.
> Looking at the management console it seems that internally the consumer tags
> are unique, e.g. _0|1|sgen_1_ but the reply to {{consume}} sent to the client
> only contains {_}sgen_1{_}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
