Reported by pieterh (1217239954|%O ago)
The current implementation of the client session layer stores method fields in the session object. So, when messages arrive as Basic.deliver methods, fields like consumer-tag, exchange, and routing-key are stored in the session. This works fine when message rates are low, but when messages arrive rapidly, the session values are over-written before the client application has a chance to pick up the arrived contents.
These fields should be stored in the content itself. Putting method fields in the session is fine for other cases, since other AMQP dialogues are synchronous, but not for delivered messages.
No files attached to this page.