[
https://issues.apache.org/jira/browse/QPID-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey resolved QPID-4131.
---------------------------------
Resolution: Fixed
Looks good to me. I tested this by repeatedly causing transactions to time out,
and used JConsole to observe the corresponding connections disappearing.
> Broker should close connection on transaction timeout rather than close
> session for better compatibility with Java clients
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4131
> URL: https://issues.apache.org/jira/browse/QPID-4131
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.12, 0.14, 0.16, 0.18
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Fix For: 0.19
>
>
> 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..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
