[QPID-4131] Broker should close connection on transaction timeout rather than close session for better compatibility with Java clients

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12, 0.14, 0.16
• Fix Version/s: 0.18, 0.19
• Component/s: Broker-J
• Assignee: Phil Harvey
• Reporter: Keith Wall
• Created: 12/Jul/12 10:09
• Updated: 11/Feb/15 20:07
• Resolved: 12/Jul/12 16:21

Description

Older versions of the Java Broker (0.5) used to close the connection in the event of transaction time (on detection of open or idle transaction) rather than close the session. When the transaction timeout feature was forward ported to 0.11, the decision was made to close the session for both 0-10 and 0-8...0-9-1. Unfortunately the Java client does not handle the session close correctly and this results in a connection leak.

This change will revert the 0-8...0-9-1 code paths within the Java Broker to use connection close rather than session close. This will ensure that the Java Broker remains compatibility with Java Clients that suffer this problem..

Issue Links

• relates to: QPID-4121 ConcurrentModificationException reported by HouseKeepingTask while closing session