[QPID-4503] [Java broker] Producer transaction timeout detection feature may log spurious open/idle alerts and close client connections/sessions without good cause

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12, 0.14, 0.16, 0.18, 0.20
• Fix Version/s: 0.20
• Component/s: Broker-J
• Assignee: Phil Harvey
• Reporter: Keith Wall
• Created: 13/Dec/12 13:33
• Updated: 11/Feb/15 20:06
• Resolved: 20/Dec/12 13:29

Description

There is a race condition in AMQChannel#checkTransactionStatus (and ServerSession#checkTransactionStatus) which can lead to spurious open/idle alerts and needlessly closed client connections (0-8..0-9-1) or client sessions (0-10).

When the defect manifests, the alert generated incorrectly identifies the transaction as being open since Jan 1, 1970. eg. 1,355,281,641,112 ms

e.g.

[con:11(guest@/127.0.0.1:47276/test)/ch:2] CHN-1007 : Open Transaction : 1,355,281,641,112 ms

This defect affects only users who have configured the transaction timeout feature (as described http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Producer-Transaction-Timeout.html).