Re: Heartbeat
Hi Ken, I have just opened a new JIRA as you suggested. https://issues.apache.org/jira/browse/PROTON-512 My idea is that there would be one global idle timeout for whole messenger and this timeout will be used for all connections. Regards, Tomas 2013-11-11 Ken Giusti kgiu...@redhat.com: Hi Tomas, - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Monday, November 11, 2013 6:43:06 AM Subject: Re: Heartbeat Hi Ken, thanks for your answer. And is there a way how to set it for pn_messenger_t No - not at present. Messenger doesn't give the application access to the transport since Messenger hides all that connection-related stuff. I'd recommend opening a JIRA requesting this feature so we won't forget about it. https://issues.apache.org/jira/browse/PROTON thanks. -K Thanks, Tomas 2013/11/8 Ken Giusti kgiu...@redhat.com Hi Tomas, The C implementation of proton allows you to set an idle time out for a connection as described in the AMQP 1.0 spec. This value is used to generate null frames (ie. frames with no bodies) on idle connections as to not expire the timeout. The connection will be dropped if the local side does not receive any traffic for it's configured timeout period. The C api is available on the transport object - see engine.h: /* timeout of zero means no timeout */ PN_EXTERN pn_millis_t pn_transport_get_idle_timeout(pn_transport_t *transport); PN_EXTERN void pn_transport_set_idle_timeout(pn_transport_t *transport, pn_millis_t timeout); PN_EXTERN pn_millis_t pn_transport_get_remote_idle_timeout(pn_transport_t *transport); I don't think the java implementation has this - yet. See https://issues.apache.org/jira/browse/PROTON-111 - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Friday, November 8, 2013 6:06:15 AM Subject: Heartbeat Hi, I am looking for a way how to manually specify heartbeat for a connection. Is there a way how to do it using proton? Thanks, Tomas Soltys -- -K -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663 -- -K -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663
Re: Proton port to OpenVMS
Hi, You could start by filing a JIRA and attaching the changes as a patch: https://issues.apache.org/jira/browse/PROTON --Rafael On Fri, Feb 7, 2014 at 5:34 AM, Tomáš Šoltys tomas.sol...@gmail.com wrote: Hi, I have made some changes to proton-c so it can be used on OpenVMS. http://en.wikipedia.org/wiki/Openvms I would like to make these changes public and to be included in next release. How should I proceed? Thanks, Tomáš Šoltys
[jira] [Commented] (PROTON-512) Possibility to set idle timeout for messenger
[ https://issues.apache.org/jira/browse/PROTON-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894504#comment-13894504 ] Ken Giusti commented on PROTON-512: --- As suggested by Tomas, I agree that it would make sense to provide a single timeout per Messenger instance that would apply to all connections managed by that Messenger. The more interesting question: what should Messenger do on timeout of a connection? Retry with backoff? Since Messenger hides all the connection management from the application, there would be no notification of the event to the application - should there be? Thoughts? Possibility to set idle timeout for messenger - Key: PROTON-512 URL: https://issues.apache.org/jira/browse/PROTON-512 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.6 Reporter: Tomas Soltys Labels: features, patch Fix For: 0.7 I would like to specify an idle timeout for a messenger which would be then used for all created connections. I see that there is an interface for pn_transport_t which is allowing it but it is not accessible from outside. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Heartbeat
Would that force an app to use blocking operations if it desires idle timeout? IOW, should the need for idle monitoring determine the choice of blocking vs non-blocking? I probably don't fully grasp the implications -K - Original Message - From: Rafael Schloming r...@alum.mit.edu To: proton@qpid.apache.org Sent: Friday, February 7, 2014 9:23:20 AM Subject: Re: Heartbeat There is already a single per messenger timeout for blocking operations. It should be a pretty trivial patch to set that same value as the idle timeout on each connection. --Rafael On Fri, Feb 7, 2014 at 8:26 AM, Ken Giusti kgiu...@redhat.com wrote: Thanks Tomáš - I agree with a single per-messenger timeout approach. - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Friday, February 7, 2014 3:04:34 AM Subject: Re: Heartbeat Hi Ken, I have just opened a new JIRA as you suggested. https://issues.apache.org/jira/browse/PROTON-512 My idea is that there would be one global idle timeout for whole messenger and this timeout will be used for all connections. Regards, Tomas 2013-11-11 Ken Giusti kgiu...@redhat.com: Hi Tomas, - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Monday, November 11, 2013 6:43:06 AM Subject: Re: Heartbeat Hi Ken, thanks for your answer. And is there a way how to set it for pn_messenger_t No - not at present. Messenger doesn't give the application access to the transport since Messenger hides all that connection-related stuff. I'd recommend opening a JIRA requesting this feature so we won't forget about it. https://issues.apache.org/jira/browse/PROTON thanks. -K Thanks, Tomas 2013/11/8 Ken Giusti kgiu...@redhat.com Hi Tomas, The C implementation of proton allows you to set an idle time out for a connection as described in the AMQP 1.0 spec. This value is used to generate null frames (ie. frames with no bodies) on idle connections as to not expire the timeout. The connection will be dropped if the local side does not receive any traffic for it's configured timeout period. The C api is available on the transport object - see engine.h: /* timeout of zero means no timeout */ PN_EXTERN pn_millis_t pn_transport_get_idle_timeout(pn_transport_t *transport); PN_EXTERN void pn_transport_set_idle_timeout(pn_transport_t *transport, pn_millis_t timeout); PN_EXTERN pn_millis_t pn_transport_get_remote_idle_timeout(pn_transport_t *transport); I don't think the java implementation has this - yet. See https://issues.apache.org/jira/browse/PROTON-111 - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Friday, November 8, 2013 6:06:15 AM Subject: Heartbeat Hi, I am looking for a way how to manually specify heartbeat for a connection. Is there a way how to do it using proton? Thanks, Tomas Soltys -- -K -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663 -- -K -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663 -- -K -- -K
[jira] [Resolved] (PROTON-498) Set VALGRIND environment variable to be compatible with the QPID build
[ https://issues.apache.org/jira/browse/PROTON-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-498. --- Resolution: Fixed Set VALGRIND environment variable to be compatible with the QPID build -- Key: PROTON-498 URL: https://issues.apache.org/jira/browse/PROTON-498 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.6 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Trivial Fix For: 0.7 The proton build system detects if valgrind is installed, and exports the VALGRIND environment variable for use by the tests. However the proton build system sets this environment variable to 1. The QPID build system also sets the VALGRIND environment variable, but it sets it to the path to the valgrind executable (eg. /usr/bin/valgrind, or equivalent). The QPID test bed assumes $VALGRIND is the path to the executable. Modify the proton build system to use the same convention as the QPID build system. This prevents problems when switching from one build system to the other. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (PROTON-500) [proton-c] Enable valgrind on C unit tests
[ https://issues.apache.org/jira/browse/PROTON-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-500. --- Resolution: Fixed Assignee: Ken Giusti [proton-c] Enable valgrind on C unit tests -- Key: PROTON-500 URL: https://issues.apache.org/jira/browse/PROTON-500 Project: Qpid Proton Issue Type: Test Components: proton-c Affects Versions: 0.6 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Trivial Fix For: 0.7 Enable valgrind to run over the C unit tests if it is installed. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Heartbeat
No, Messenger.setBlocking(True/False) is independent of Messenger.setTimeout(...). --Rafael On Fri, Feb 7, 2014 at 10:29 AM, Ken Giusti kgiu...@redhat.com wrote: Would that force an app to use blocking operations if it desires idle timeout? IOW, should the need for idle monitoring determine the choice of blocking vs non-blocking? I probably don't fully grasp the implications -K - Original Message - From: Rafael Schloming r...@alum.mit.edu To: proton@qpid.apache.org Sent: Friday, February 7, 2014 9:23:20 AM Subject: Re: Heartbeat There is already a single per messenger timeout for blocking operations. It should be a pretty trivial patch to set that same value as the idle timeout on each connection. --Rafael On Fri, Feb 7, 2014 at 8:26 AM, Ken Giusti kgiu...@redhat.com wrote: Thanks Tomáš - I agree with a single per-messenger timeout approach. - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Friday, February 7, 2014 3:04:34 AM Subject: Re: Heartbeat Hi Ken, I have just opened a new JIRA as you suggested. https://issues.apache.org/jira/browse/PROTON-512 My idea is that there would be one global idle timeout for whole messenger and this timeout will be used for all connections. Regards, Tomas 2013-11-11 Ken Giusti kgiu...@redhat.com: Hi Tomas, - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Monday, November 11, 2013 6:43:06 AM Subject: Re: Heartbeat Hi Ken, thanks for your answer. And is there a way how to set it for pn_messenger_t No - not at present. Messenger doesn't give the application access to the transport since Messenger hides all that connection-related stuff. I'd recommend opening a JIRA requesting this feature so we won't forget about it. https://issues.apache.org/jira/browse/PROTON thanks. -K Thanks, Tomas 2013/11/8 Ken Giusti kgiu...@redhat.com Hi Tomas, The C implementation of proton allows you to set an idle time out for a connection as described in the AMQP 1.0 spec. This value is used to generate null frames (ie. frames with no bodies) on idle connections as to not expire the timeout. The connection will be dropped if the local side does not receive any traffic for it's configured timeout period. The C api is available on the transport object - see engine.h: /* timeout of zero means no timeout */ PN_EXTERN pn_millis_t pn_transport_get_idle_timeout(pn_transport_t *transport); PN_EXTERN void pn_transport_set_idle_timeout(pn_transport_t *transport, pn_millis_t timeout); PN_EXTERN pn_millis_t pn_transport_get_remote_idle_timeout(pn_transport_t *transport); I don't think the java implementation has this - yet. See https://issues.apache.org/jira/browse/PROTON-111 - Original Message - From: Tomáš Šoltys tomas.sol...@gmail.com To: proton@qpid.apache.org Sent: Friday, November 8, 2013 6:06:15 AM Subject: Heartbeat Hi, I am looking for a way how to manually specify heartbeat for a connection. Is there a way how to do it using proton? Thanks, Tomas Soltys -- -K -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663 -- -K -- Tomáš Šoltys tomas.sol...@gmail.com http://www.range-software.com (+420) 776-843-663 -- -K -- -K
