Re: API and terms: idle-time-out and heartbeat intervals.

On 28 September 2016 at 21:36, Alan Conway wrote: > On Wed, 2016-09-28 at 13:26 -0700, Justin Ross wrote: >> IMO, the overall picture is simpler, and easier to explain to third >> parties, if we go the way Ken suggested. When a remote peer sends >> you an >> idle timeout

[jira] [Commented] (QPID-7433) Add minimal maven module to invoke TCK

[ https://issues.apache.org/jira/browse/QPID-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530962#comment-15530962 ] ASF subversion and git services commented on QPID-7433: --- Commit 1762717 from

[jira] [Commented] (QPID-7433) Add minimal maven module to invoke TCK

[ https://issues.apache.org/jira/browse/QPID-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530942#comment-15530942 ] ASF subversion and git services commented on QPID-7433: --- Commit 1762716 from

Re: API and terms: idle-time-out and heartbeat intervals.

The spec unfortunately says what it says, and even if there were scope to update it, I'm not sure there is a way to change it to address the main issue (which regardless of any other clarity issues, is I think just that it only says you SHOULD advertise half your 'actual timeout') that wouldn't

[jira] [Commented] (QPIDJMS-207) Implement the JMS 2.0 API

[ https://issues.apache.org/jira/browse/QPIDJMS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530932#comment-15530932 ] ASF subversion and git services commented on QPIDJMS-207: - Commit

[jira] [Resolved] (PROTON-1308) Support Idle Timeout setting in electron Transport

[ https://issues.apache.org/jira/browse/PROTON-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1308. - Resolution: Fixed Fix Version/s: 0.15.0 There is some ongoing debate about ambiguity in

[jira] [Commented] (PROTON-1308) Support Idle Timeout setting in electron Transport

[ https://issues.apache.org/jira/browse/PROTON-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530815#comment-15530815 ] ASF subversion and git services commented on PROTON-1308: - Commit

[jira] [Commented] (PROTON-1308) Support Idle Timeout setting in electron Transport

[ https://issues.apache.org/jira/browse/PROTON-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530816#comment-15530816 ] ASF subversion and git services commented on PROTON-1308: - Commit

Re: API and terms: idle-time-out and heartbeat intervals.

In case it was unclear I'm fine with it doing what it does here given the spec wording, pessimistic was just a word choice (though I'd say it fits the situation as well as conservative). I was mainly just noting that as every time this comes up (this is at least the third time I'd say I've had

Re: API and terms: idle-time-out and heartbeat intervals.

On Wed, 2016-09-28 at 13:26 -0700, Justin Ross wrote: > IMO, the overall picture is simpler, and easier to explain to third > parties, if we go the way Ken suggested.  When a remote peer sends > you an > idle timeout value, it is an expression of an (actual, not simply > "advertised") guarantee -

Re: API and terms: idle-time-out and heartbeat intervals.

IMO, the overall picture is simpler, and easier to explain to third parties, if we go the way Ken suggested. When a remote peer sends you an idle timeout value, it is an expression of an (actual, not simply "advertised") guarantee - "I will expire the connection after X time without receiving a

Re: API and terms: idle-time-out and heartbeat intervals.

Seems there's some dispute over the meaning of idle-time-out in the AMQP spec, not just how proton treats it. Let me try to convince you. Forget proton for a moment, here's the spec text with my comments. Remember: the spec defines the AMQP *protocol*, the important text is where it talks

[jira] [Resolved] (DISPATCH-160) Dispatch router does not propagate custom message annotations

[ https://issues.apache.org/jira/browse/DISPATCH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-160. --- Resolution: Fixed > Dispatch router does not propagate custom message annotations >

[jira] [Commented] (DISPATCH-160) Dispatch router does not propagate custom message annotations

[ https://issues.apache.org/jira/browse/DISPATCH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530695#comment-15530695 ] ASF GitHub Bot commented on DISPATCH-160: - Github user asfgit closed the pull request at:

[jira] [Commented] (DISPATCH-160) Dispatch router does not propagate custom message annotations

[ https://issues.apache.org/jira/browse/DISPATCH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530693#comment-15530693 ] ASF subversion and git services commented on DISPATCH-160: -- Commit

[GitHub] qpid-dispatch pull request #101: DISPATCH-160 - Modified code to allow propa...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/101 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

[ https://issues.apache.org/jira/browse/QPID-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530678#comment-15530678 ] Gordon Sim commented on QPID-6868: -- Fix proposed for QPID-7415 has now been committed to master and will

Re: API and terms: idle-time-out and heartbeat intervals.

On Wed, 2016-09-28 at 10:13 -0400, Ken Giusti wrote: > I've had a hand in the way Proton/C interprets the meaning of 'idle- > timeout' and I've never liked the solution.  I think Proton/C's > behavior is not 'pessimistic' as much as it is 'conservative' for the > sake of interoperability.  This,

[jira] [Resolved] (QPID-7415) [AMQP 1.0]: reject, release & modified ignored by qpid::messaging

[ https://issues.apache.org/jira/browse/QPID-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7415. -- Resolution: Fixed > [AMQP 1.0]: reject, release & modified ignored by qpid::messaging >

[jira] [Closed] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

[ https://issues.apache.org/jira/browse/QPID-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-6868. Resolution: Duplicate > [AMQP 1.0 C++ Client] No errors for rejected messages. >

[jira] [Commented] (QPID-7415) [AMQP 1.0]: reject, release & modified ignored by qpid::messaging

[ https://issues.apache.org/jira/browse/QPID-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530669#comment-15530669 ] ASF subversion and git services commented on QPID-7415: --- Commit

[jira] [Updated] (DISPATCH-357) Address field is empty for link routed links in the qdstat "links" output

[ https://issues.apache.org/jira/browse/DISPATCH-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-357: -- Fix Version/s: (was: 0.7.0) 0.8.0 > Address field is empty for link routed

[jira] [Resolved] (QPIDJMS-211) make the JNDI connection factory property handling more flexible

[ https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-211. Resolution: Fixed > make the JNDI connection factory property handling more flexible >

[jira] [Updated] (QPIDJMS-211) make the JNDI connection factory property handling more flexible

[ https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-211: --- Description: Currently the connection factory property handling in the JNDI bits use

[jira] [Commented] (QPIDJMS-211) make the JNDI connection factory property handling more flexible

[ https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530224#comment-15530224 ] ASF subversion and git services commented on QPIDJMS-211: - Commit

[jira] [Updated] (QPIDJMS-211) make the JNDI connection factory property handling more flexible

[ https://issues.apache.org/jira/browse/QPIDJMS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-211: --- Description: Currently the connection factory property handling in the JNDI bits uses

[jira] [Created] (QPIDJMS-211) make the JNDI connection factory property handling more flexible

Robbie Gemmell created QPIDJMS-211: -- Summary: make the JNDI connection factory property handling more flexible Key: QPIDJMS-211 URL: https://issues.apache.org/jira/browse/QPIDJMS-211 Project: Qpid

[jira] [Commented] (QPID-7438) ACL provider and AutoGeneratedSelfSignedKeyStore modify configured state without using the configuration task executor

[ https://issues.apache.org/jira/browse/QPID-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530012#comment-15530012 ] Lorenz Quack commented on QPID-7438: The first commit adds the {{changesConfiguredObjectState}}

[jira] [Commented] (QPID-7438) ACL provider and AutoGeneratedSelfSignedKeyStore modify configured state without using the configuration task executor

[ https://issues.apache.org/jira/browse/QPID-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529968#comment-15529968 ] ASF subversion and git services commented on QPID-7438: --- Commit 1762682 from

[jira] [Commented] (QPID-7438) ACL provider and AutoGeneratedSelfSignedKeyStore modify configured state without using the configuration task executor

[ https://issues.apache.org/jira/browse/QPID-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529967#comment-15529967 ] ASF subversion and git services commented on QPID-7438: --- Commit 1762681 from

[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost

[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529815#comment-15529815 ] Lorenz Quack commented on QPID-7379: Looks good! I like the change of passing the serialiser into the

[jira] [Comment Edited] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529429#comment-15529429 ] Robbie Gemmell edited comment on QPID-7431 at 9/28/16 12:17 PM: [~gsim]

[jira] [Commented] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529429#comment-15529429 ] Robbie Gemmell commented on QPID-7431: -- @gsim thanks for clarifying, sorry for the premature close

[jira] [Reopened] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reopened QPID-7431: -- Assignee: Gordon Sim > Support for message-annotations > --- > >

[jira] [Comment Edited] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529411#comment-15529411 ] Gordon Sim edited comment on QPID-7431 at 9/28/16 12:14 PM: Messages with

[jira] [Commented] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529411#comment-15529411 ] Gordon Sim commented on QPID-7431: -- Messages with annotations can be received through qpid::messaging (and

[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost

[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529203#comment-15529203 ] ASF subversion and git services commented on QPID-7379: --- Commit 1762630 from

Re: API and terms: idle-time-out and heartbeat intervals.

I agree that specifying that the communicated figure should be "half" the "actual" timeout was a mistake. What the spec should have tried to communicate is that the sender should communicate a value somewhat less than the period it uses to determine that the connection has actually timed-out to

[jira] [Commented] (QPID-7366) [Java Broker] Add Management operation to VirtualHost to allow publishing of messages through management

[ https://issues.apache.org/jira/browse/QPID-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529154#comment-15529154 ] Rob Godfrey commented on QPID-7366: --- It seems a little strange to me to do checks on the headers in

Re: API and terms: idle-time-out and heartbeat intervals.

On 27 September 2016 at 22:24, Alan Conway wrote: > On Tue, 2016-09-27 at 15:37 -0400, Alan Conway wrote: >> I want to clarify and document the meaning of these terms for our >> APIs, >> presently I can't find anywhere where they are documented clearly. >> >> The AMQP spec

[jira] [Commented] (QPID-7379) [Java Broker] Provide a mechanism to extract messages from a vhost message store and replay them into a new vhost

[ https://issues.apache.org/jira/browse/QPID-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528975#comment-15528975 ] ASF subversion and git services commented on QPID-7379: --- Commit 1762621 from

[jira] [Updated] (QPID-6803) ByteBuffer slices/duplicates contribute significantly to garbage overhead in busy Brokers

[ https://issues.apache.org/jira/browse/QPID-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6803: - Fix Version/s: qpid-java-6.1 > ByteBuffer slices/duplicates contribute significantly to garbage overhead

[jira] [Assigned] (QPID-6803) ByteBuffer slices/duplicates contribute significantly to garbage overhead in busy Brokers

[ https://issues.apache.org/jira/browse/QPID-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-6803: Assignee: Keith Wall > ByteBuffer slices/duplicates contribute significantly to garbage overhead in