2 - Client Basic.Deliver fields get lost

Reported by pieterhpieterh (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.

Attachments:

No files attached to this page.

Comments

Add a New Comment

Edit | Files | Tags | Print

rating: +1+x

Who's following this issue?

pieterhpieterh
martin_sustrikmartin_sustrik
CybariteCybarite
Watch: site | category | page

Submitted by pieterhpieterh

Use one of these tags to say what kind of issue it is:

  • issue - a fault in the software or the packaging or the documentation.
  • change - a change or feature request.

Use one of these tags to say what state the issue is in:

  • open - a new, open issue.
  • closed - issue has been closed.
  • rejected - the issue has been rejected.

Use one of these tags to say how urgent the issue is:

  • fatal - the issue is stopping all work.
  • urgent - it's urgent.

All open

Most recent

Page tags: closed issue