qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-228) Connection close can use wrong timeout value and stall
Date Thu, 01 Dec 2016 16:18:58 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712381#comment-15712381

ASF subversion and git services commented on QPIDJMS-228:

Commit 87708cefa5f1860708e911ff72008af0b5a1eb27 in qpid-jms's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=87708ce ]

QPIDJMS-228 Extend the default close timeout

Use a longer close timeout to account for cases where large messages etc
might be inflight

> 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message