[DISPATCH-802] refuse transaction coordination links if they can't be routed to a coordinator

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 1.0.0
• Assignee: Ganesh Murthy
• Reporter: Robbie Gemmell
• Created: 03/Aug/17 15:07
• Updated: 02/Oct/19 17:55
• Resolved: 24/Aug/17 14:37

Description

The router is accepting transaction coordinator links even if the support from DISPATCH-195 is not being used to link-route them somewhere that can handle coordination. If the router can't link-route to a coordinator, and knows it can't coordinate transactions itself, it shouldn't accept the links to begin with but rather refuse them so clients know they will never work and why.

Prior to 0.8.0, credit was also given on these links, allowing attempt to declare transactions. From 0.8.0 no credit is given since there is no receiver, so clients have no way to use the accepted link and no indication why.

Issue Links

• is related to: QPIDJMS-307 fix handling of tx declare rejection while creating a transacted Session
• links to: GitHub Pull Request #184
• links to: GitHub Pull Request #187
• links to: GitHub Pull Request #190