You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2019/05/03 13:06:00 UTC
[jira] [Updated] (PROTON-1893) [c] idle-timeout set in REMOTE_OPEN
does not take immediate effect.
[ https://issues.apache.org/jira/browse/PROTON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated PROTON-1893:
-----------------------------------
Fix Version/s: (was: proton-c-0.28.0)
proton-c-0.29.0
> [c] idle-timeout set in REMOTE_OPEN does not take immediate effect.
> -------------------------------------------------------------------
>
> Key: PROTON-1893
> URL: https://issues.apache.org/jira/browse/PROTON-1893
> Project: Qpid Proton
> Issue Type: Bug
> Affects Versions: proton-c-0.24.0
> Reporter: Alan Conway
> Assignee: Cliff Jansen
> Priority: Major
> Fix For: proton-c-0.29.0
>
>
> If idle-timeout is set on the server in a PN_CONNECTION_REMOTE_OPEN event, it
> is correctly sent to the peer in the OPEN frame, but the local timer is not activated until the first data is read or written on the connection. If the client never sends another frame, the server does not time out the connection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org