[DISPATCH-1090] Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0

Environment

Version 1.3.0-SNAPSHOT
(30ff7ff1d54b8f280b36f76dc8c340cb4c88567b)

• Assignee: Ganesh Murthy
• Reporter: Keith Wall
• Created: 27/Jul/18 16:34
• Updated: 02/Oct/19 17:55
• Resolved: 10/Sep/18 13:52

Description

I have configured a single Dispatch Router instance to route messages through a broker queue (i.e. following section 7.2.5 of the docs).

The application does the following:

1. Forms a sending links to the queue, sends a single message then disconnects.
2. Forms a receiving link to the same queue, receives the message without settling then abruptly terminates the program.

Inspecting the protocol trace, I see that after the Dispatch Router has sent a Disposition state=modified for the message that was held by the application when it terminated, a Transfer/Disposition state=release loop forms between the Dispatch Router and Broker until the link credit is exhausted.

Protocol trace attached to this issue demonstrates the problem.

Dispatch Router was configured by the following commands:

qdmanage create --type org.apache.qpid.dispatch.connector host=oslo.local port=5672 name=artemis-broker role=route-container
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue direction=in connection=artemis-broker
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue direction=out connection=artemis-broker
qdmanage create --type=org.apache.qpid.dispatch.router.config.address pattern=queue waypoint=true

Issue Links

• links to: GitHub Pull Request #368
• links to: GitHub Pull Request #371