[jira] [Updated] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout
[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-610: - Attachment: (was: 0001-ensure-messenger-honours-remote-idle-timeout.patch) proton-c: messenger doesn't honour an advertised remote idle timeout Key: PROTON-610 URL: https://issues.apache.org/jira/browse/PROTON-610 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Reporter: Dominic Evans Attachments: 0001-ensure-messenger-honours-remote-idle-timeout.patch 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. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (PROTON-646) Perl message does not have the correct type when the body is a boolean with a FALSE value
[ https://issues.apache.org/jira/browse/PROTON-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-646. - Resolution: Fixed Perl message does not have the correct type when the body is a boolean with a FALSE value - Key: PROTON-646 URL: https://issues.apache.org/jira/browse/PROTON-646 Project: Qpid Proton Issue Type: Bug Components: perl-binding Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Priority: Minor Fix For: 0.8 In using the send.pl and recv.pl examples to test other changes, I found that whenever a message's body is a boolean value the body type is undefined. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout
[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097153#comment-14097153 ] Andrew Stitcher commented on PROTON-610: [~dnwe] If you could add a unit test (that currently fails, but succeeds after your patch) it would save significant work in applying your patch. The relevant tests can probably be found in tests/python/proton_tests/messenger.py. There are also engine level idle timeout tests to use as a reference in tests/python/proton_tests/engine.py proton-c: messenger doesn't honour an advertised remote idle timeout Key: PROTON-610 URL: https://issues.apache.org/jira/browse/PROTON-610 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Reporter: Dominic Evans Attachments: 0001-ensure-messenger-honours-remote-idle-timeout.patch 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. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout
[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097597#comment-14097597 ] Dominic Evans commented on PROTON-610: -- [~astitcher] thanks for looking at this issue. Sure, I can take a look at knocking up a unit test for this. proton-c: messenger doesn't honour an advertised remote idle timeout Key: PROTON-610 URL: https://issues.apache.org/jira/browse/PROTON-610 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Reporter: Dominic Evans Attachments: 0001-ensure-messenger-honours-remote-idle-timeout.patch 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. -- This message was sent by Atlassian JIRA (v6.2#6252)
