7 - Topic Exchange Wildcard Routing

Reported by mjeungmjeung (1221003830|%O ago)

Experimenting with the topic exchange, I ran into some routing behavior that seemed wrong:

  1. I have a queue bound to a topic exchange with the binding key of "test.#".
  2. I then send a message to the topic exchange with a routing key of "abcd.efgh".
  3. Even though the routing key doesn't look like it should match the binding key, the message still ends up in the arrived queue.

Easy to reproduce with the im_sender and im_receiver tutorials.

Attachments:

No files attached to this page.

Comments

Add a New Comment

Edit | Files | Tags | Print

rating: 0+x

Who's following this issue?

pieterhpieterh
martin_sustrikmartin_sustrik
mjeungmjeung
CybariteCybarite
Watch: site | category | page

Submitted by mjeungmjeung

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