[
https://issues.apache.org/jira/browse/PROTON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543512#comment-16543512
]
Alan Conway commented on PROTON-1893:
-------------------------------------
Partial fix at:
[https://github.com/alanconway/qpid-proton/tree/cpp-idle-timeout-next]
Works for epoll but windows IOCP tests are failing.
This sets the tick_pending flag in batch_next to make sure there's a tick check
after each CONNECTION_*_OPEN event has been handled. It generates only 2 extra
ticks per connection, and I believe it is sufficient - LOCAL_OPEN is the last
chance to change your local time-out before you've published it to the peer and
is a local event so there's no danger of hanging if the remote is unresponsive.
REMOTE_OPEN is the only time that the remote time-out can be set.
> [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.25.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: [email protected]
For additional commands, e-mail: [email protected]
