[clebertsuconic]

• QueueIDs on ACK and route information
• route-to information on clustered routes

assited-by Claude

[clebertsuconic]

using the clustered examples, clustered-topic to route a few messages and print-data, this is the decorated output:

│Add       │58  │45 (ADD_MESSAGE_PROTOCOL)     │    │0       │Message(messageID=58;userMessageID=b66274f8-cd8b-11f1-b271-d4a2cde1ec42;msg=CoreMessage[messageID=58, durable=true,     │
│          │    │                              │    │        │  userID=b66274f8-cd8b-11f1-b271-d4a2cde1ec42, priority=4, timestamp=Wed Oct 21 16:12:16 EDT 2026, expiration=0,        │
│          │    │                              │    │        │  durable=true, address=exampleTopic, size=451, properties=TypedProperties[__AMQ_CID=b5a9d34b-cd8b-11f1-b271-           │
│          │    │                              │    │        │  d4a2cde1ec42, _AMQ_ROUTE_TO$.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42=[0000 0000 0000 002E]│
│          │    │                              │    │        │  , bytesAsLongs[46], _AMQ_ROUTING_TYPE=0]]@692838068                                                                   │
│          │    │                              │    │        │  ->_AMQ_ROUTE_TO$.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42 = [46]                           │
│Update    │58  │32 (ADD_REF)                  │    │0       │QueueEncoding [queueID=15]($.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42)                       │
│Add       │59  │45 (ADD_MESSAGE_PROTOCOL)     │    │0       │Message(messageID=59;userMessageID=b6672fe9-cd8b-11f1-b271-d4a2cde1ec42;msg=CoreMessage[messageID=59, durable=true,     │
│          │    │                              │    │        │  userID=b6672fe9-cd8b-11f1-b271-d4a2cde1ec42, priority=4, timestamp=Wed Oct 21 16:12:16 EDT 2026, expiration=0,        │
│          │    │                              │    │        │  durable=true, address=exampleTopic, size=451, properties=TypedProperties[__AMQ_CID=b5a9d34b-cd8b-11f1-b271-           │
│          │    │                              │    │        │  d4a2cde1ec42, _AMQ_ROUTE_TO$.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42=[0000 0000 0000 002E]│
│          │    │                              │    │        │  , bytesAsLongs[46], _AMQ_ROUTING_TYPE=0]]@1392570698                                                                  │
│          │    │                              │    │        │  ->_AMQ_ROUTE_TO$.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42 = [46]                           │
│Update    │59  │32 (ADD_REF)                  │    │0       │QueueEncoding [queueID=15]($.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42)                       │
│Update    │57  │33 (ACKNOWLEDGE_REF)          │    │0       │ACK;QueueEncoding [queueID=15]($.artemis.internal.sf.my-cluster.b4e10570-cd8b-11f1-888d-d4a2cde1ec42)                   │

[brusdev]

Nice improvement, surfacing the message address and queue makes inspecting the message journal records much easier!

[brusdev]

Remote binding IDs may not match local binding IDs, so we should not decorate HDR_ROUTE_TO_IDS with local queue names.