[
https://issues.apache.org/jira/browse/QPIDJMS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved QPIDJMS-228.
----------------------------------
Resolution: Fixed
> Connection close can use wrong timeout value and stall
> ------------------------------------------------------
>
> Key: QPIDJMS-228
> URL: https://issues.apache.org/jira/browse/QPIDJMS-228
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.11.1
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.20.0
>
>
> When closing the JMS Connection the closeTimeout value should be used to
> control how long to wait before failing the close request and continue the
> shutdown procedure. There is a code path that will instead use the
> requestTimeout value which defaults to infinite wait and can lead to a
> close() call that is hung waiting on server response which might in some
> cases never come.
> Close on other resources such as Session, Producer and Consumer are also
> using requestTimeout and should really be using the closeTimeout to be
> consistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
