[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348969#comment-16348969 ] Keith Wall commented on QPID-8067: -- Changes look reasonable, ported to the 7.0.x branch. > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348966#comment-16348966 ] ASF subversion and git services commented on QPID-8067: --- Commit e5dce3c10fc96278a89661d490cdff9e506fbd01 in qpid-broker-j's branch refs/heads/7.0.x from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=e5dce3c ] QPID-8067: [Broker-J] Fix an evaluation of start time for queue default arrival time filter > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348967#comment-16348967 ] ASF subversion and git services commented on QPID-8067: --- Commit 0d6b0897d8691f16434dce171977ea69c86ffaac in qpid-broker-j's branch refs/heads/7.0.x from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=0d6b089 ] QPID-8067: [Broker-J] Improve exception if x-qpid-replay-period does not contain a parseable long > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348943#comment-16348943 ] ASF subversion and git services commented on QPID-8067: --- Commit f877df1065c3dff7f20a30c22322938c054ade92 in qpid-broker-j's branch refs/heads/master from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=f877df1 ] QPID-8067: [Broker-J] Improve exception if x-qpid-replay-period does not contain a parseable long > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348722#comment-16348722 ] ASF subversion and git services commented on QPID-8067: --- Commit 424614770c10a5ec4ac90ba7fc3abf33bffad70f in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=4246147 ] QPID-8067: [Broker-J] Remove annotation '@Ignore' for the JMS test testing queue arrival time filter > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348389#comment-16348389 ] ASF subversion and git services commented on QPID-8067: --- Commit 5e1ae2dd6e059cf464cb7e7fa3373d656102bd37 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=5e1ae2d ] QPID-8067: [Broker-J] Fix an evaluation of start time for queue default arrival time filter > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8067) [Broker-J] Default queue filter for arrival time with non-zero replay period does not filter messages as documented
[ https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318628#comment-16318628 ] Keith Wall commented on QPID-8067: -- Alex - I agree with your analysis. I think this should be fixed on master and 7.0.1. > [Broker-J] Default queue filter for arrival time with non-zero replay period > does not filter messages as documented > --- > > Key: QPID-8067 > URL: https://issues.apache.org/jira/browse/QPID-8067 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5 >Reporter: Alex Rudyy > Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0 > > > As per Broker documentation the replay period in arrival filter determines a > time interval ( in seconds) for which the arriving messages enqueued into > queue within given interval before consumer attach have to be delivered to > the consumer. Thus, all message on the queue with arrival time greater than > ({{consumer attach time}} - {{replay period}}) should be delivered to the > consumer. If filter is specified on consumer attach, the delivery works as > expected. However, if arrival filter is specified as default queue filter, > the broker behaviour is not documentation compliant: > * the broker delivers to consumer only messages with arrival time greater > than ({{consumer attach time}} + {{replay period}}) > * the {{replay period}} is treated as being set in milliseconds rather than > in seconds > The issue only impacts use cases when arrival filter with non-zero {{replay > period}} is set as queue default filter. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org