Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
proton-c-0.21.0
-
None
Description
The container does not wake up to service transport ticks, which means heartbeat frames are not sent to respect the idle_timeout settings.
All the heartbeat and idle timeout logic is already implemented by the C library, the ruby Container only needs to ensure it wakes up often enough to service connections on time.
Attachments
Issue Links
- is duplicated by
-
PROTON-1793 [ruby] not sending heartbeat frames to respect idle-timeout
- Closed