[ https://issues.apache.org/jira/browse/QPID-8571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922449#comment-17922449 ]
Robert Godfrey commented on QPID-8571: -------------------------------------- I apologies that there has been no response to this in over 3 years :( Looking at the code and taking your comment that this occurs {quote}on auto-recovery using the RabbitMQ Java client{quote} - I do see an issue in the AMQP 0-x code here, that if the client provides a {{BasicConsume}} with a consumer tag (rather than relying on a server generated one), then at a later point a new consumer is created with no tag (i.e. asking the Broker to generate one) then the broker will likely create a tag that matches the tag that was used by the client based on a server generate tag in the previous iteration of the connection. On the off chance that you (or anyone else) is still running into this issue, I'll make a fix presently > 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 > Assignee: Robert Godfrey > Priority: Major > > 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