[PROTON-610] proton-c: messenger doesn't honour an advertised remote idle timeout

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.7
• Fix Version/s: proton-0.8
• Component/s: proton-c
• Assignee: Andrew Stitcher
• Reporter: Dominic Evans
• Created: 16/Jun/14 11:41
• Updated: 10/Oct/14 12:42
• Resolved: 04/Sep/14 19:28

Description

The changes under PROTON-111 added support to the underlying proton engine for honouring a remote idle timeout (as per the AMQP 1.0 spec) and sending empty null frames on a heartbeat interval to prevent the idle timeout expiring (and hence causing the client to be disconnect), However, the Messenger API doesn't currently drive the same behaviour and so will be disconnected from any broker that has implemented such a timeout.