[jira] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
[
https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8098:
-
Status: Reviewable (was: In Progress)
> [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
> --
>
> Key: QPID-8098
> URL: https://issues.apache.org/jira/browse/QPID-8098
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1,
> qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.2, qpid-java-broker-7.1.0
>
>
> On the AMQP 0-10 protocol path within the Broker, deliveries to queue
> browsers erroneously increase the {{MessageInstance#deliveryCount}}. This
> should not happen. The purpose of the delivery count is to count deliveries
> to (destructive) consumers - not browsers. The problem is restricted to AMQP
> 0-10 implementation. Neither AMQP 0-x nor AMQP 1.0 are affected by this
> defect.
> The defect could mean that messages are spuriously routed to a DLQ (if
> configured). For this to happen, there would need to be additional
> destructive consumers on the queue that cause the message to be 'released'.
> Releasing occurs during transaction rollback and client disconnection (when
> messages are prefetched). The message would be prematurely routed to the
> DLQ in this case.
> The defect is longstanding. I tested as far back as 0.30.
> https://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3c1518546115789-0.p...@n2.nabble.com%3e
--
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] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
[
https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8098:
-
Fix Version/s: qpid-java-broker-7.1.0
qpid-java-broker-7.0.2
> [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
> --
>
> Key: QPID-8098
> URL: https://issues.apache.org/jira/browse/QPID-8098
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1,
> qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.0.2, qpid-java-broker-7.1.0
>
>
> On the AMQP 0-10 protocol path within the Broker, deliveries to queue
> browsers erroneously increase the {{MessageInstance#deliveryCount}}. This
> should not happen. The purpose of the delivery count is to count deliveries
> to (destructive) consumers - not browsers. The problem is restricted to AMQP
> 0-10 implementation. Neither AMQP 0-x nor AMQP 1.0 are affected by this
> defect.
> The defect could mean that messages are spuriously routed to a DLQ (if
> configured). For this to happen, there would need to be additional
> destructive consumers on the queue that cause the message to be 'released'.
> Releasing occurs during transaction rollback and client disconnection (when
> messages are prefetched). The message would be prematurely routed to the
> DLQ in this case.
> The defect is longstanding. I tested as far back as 0.30.
> https://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3c1518546115789-0.p...@n2.nabble.com%3e
--
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] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
[
https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8098:
-
Description:
On the AMQP 0-10 protocol path within the Broker, deliveries to queue browsers
erroneously increase the {{MessageInstance#deliveryCount}}. This should not
happen. The purpose of the delivery count is to count deliveries to
(destructive) consumers - not browsers. The problem is restricted to AMQP 0-10
implementation. Neither AMQP 0-x nor AMQP 1.0 are affected by this defect.
The defect could mean that messages are spuriously routed to a DLQ (if
configured). For this to happen, there would need to be additional destructive
consumers on the queue that cause the message to be 'released'. Releasing
occurs during transaction rollback and client disconnection (when messages are
prefetched). The message would be prematurely routed to the DLQ in this case.
The defect is longstanding. I tested as far back as 0.30.
https://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3c1518546115789-0.p...@n2.nabble.com%3e
was:
On the AMQP 0-10 protocol path within the Broker, deliveries to queue browsers
erroneously increase the {{MessageInstance#deliveryCount}}. This should not
happen. The purpose of the delivery count is to count deliveries to
(destructive) consumers - not browsers. The problem is restricted to AMQP 0-10
implementation. Neither AMQP 0-x nor AMQP 1.0 are affected by this defect.
The defect could mean that messages are spuriously routed to a DLQ (if
configured). For this to happen, there would need to be additional destructive
consumers on the queue that cause the message to be 'released'. Releasing
occurs during transaction rollback and client disconnection (when messages are
prefetched). The message would be prematurely routed to the DLQ in this case.
https://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3c1518546115789-0.p...@n2.nabble.com%3e
> [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
> --
>
> Key: QPID-8098
> URL: https://issues.apache.org/jira/browse/QPID-8098
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1,
> qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Priority: Major
>
> On the AMQP 0-10 protocol path within the Broker, deliveries to queue
> browsers erroneously increase the {{MessageInstance#deliveryCount}}. This
> should not happen. The purpose of the delivery count is to count deliveries
> to (destructive) consumers - not browsers. The problem is restricted to AMQP
> 0-10 implementation. Neither AMQP 0-x nor AMQP 1.0 are affected by this
> defect.
> The defect could mean that messages are spuriously routed to a DLQ (if
> configured). For this to happen, there would need to be additional
> destructive consumers on the queue that cause the message to be 'released'.
> Releasing occurs during transaction rollback and client disconnection (when
> messages are prefetched). The message would be prematurely routed to the
> DLQ in this case.
> The defect is longstanding. I tested as far back as 0.30.
> https://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3c1518546115789-0.p...@n2.nabble.com%3e
--
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] [Updated] (QPID-8098) [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
[
https://issues.apache.org/jira/browse/QPID-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8098:
-
Summary: [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the
delivery count (was: [AMQP 0-10] Queue browsers increment the delivery count)
> [Broker-J] [AMQP 0-10] Queue browsers erroneously increment the delivery count
> --
>
> Key: QPID-8098
> URL: https://issues.apache.org/jira/browse/QPID-8098
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1,
> qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Priority: Major
>
> On the AMQP 0-10 protocol path within the Broker, deliveries to queue
> browsers erroneously increase the {{MessageInstance#deliveryCount}}. This
> should not happen. The purpose of the delivery count is to count deliveries
> to (destructive) consumers - not browsers. The problem is restricted to AMQP
> 0-10 implementation. Neither AMQP 0-x nor AMQP 1.0 are affected by this
> defect.
> The defect could mean that messages are spuriously routed to a DLQ (if
> configured). For this to happen, there would need to be additional
> destructive consumers on the queue that cause the message to be 'released'.
> Releasing occurs during transaction rollback and client disconnection (when
> messages are prefetched). The message would be prematurely routed to the
> DLQ in this case.
> https://mail-archives.apache.org/mod_mbox/qpid-users/201802.mbox/%3c1518546115789-0.p...@n2.nabble.com%3e
--
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
