[
https://issues.apache.org/jira/browse/PROTON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1893:
--------------------------------
Summary: [c] idle-timeout set in REMOTE_OPEN does not take immediate effect
(was: [c] idle-timeout set in REMOTE_OPEN does not take immediate effect.)
> [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
> Components: proton-c
> Affects Versions: proton-c-0.24.0
> Reporter: Alan Conway
> Assignee: Clifford Jansen
> Priority: Major
> Fix For: proton-c-future
>
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
