Queued messages from other sessions now report why they are still being held.
What's wrong with this entry?
Re-running the inbound policy over queued cross-session messages now reports why each still-held message is held.
- the hold cause, which may have changed since the message arrived, is passed to a listener along with the current queue depth
- refused messages additionally fire a drop callback
[cross-session-inbound] dropped
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross