-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
None
If a consumer subscribes to a wildcard address `test.*.A` a new address is auto-created `test.*.A` when the consumer connects.
This causes a problem because messages published to 'test.foo.A' will be sent to the `test.*.A` address rather than `test.foo.A`. When paging is started on the destination, the message 'destination' header is now `test.*.A` in stead of `test.foo.A`. If consumers rely on the 'destination' header for processing, the original destination is lost.
- clones
-
ENTMQBR-3880 destination header replaced for wildcard address during paging
- Closed
- relates to
-
ENTMQBR-4426 [LTS] Inconsistent and negative address size
- Closed