qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rupert Smith (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-617) Transactional consume does not ack messages.
Date Tue, 02 Oct 2007 11:41:51 GMT

    [ https://issues.apache.org/jira/browse/QPID-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531757
] 

Rupert Smith commented on QPID-617:
-----------------------------------

Confirmed that this is a bug and not an error in the test.

Message 1 received and committed by consumer 1
Message 2 received and committed by consumer 2

When closing consumer 1, message 1 is redelivered to consumer 2 as broker thinks that it has
not been acked.

> Transactional consume does not ack messages.
> --------------------------------------------
>
>                 Key: QPID-617
>                 URL: https://issues.apache.org/jira/browse/QPID-617
>             Project: Qpid
>          Issue Type: Bug
>    Affects Versions: M2
>         Environment: Java client/broker.
>            Reporter: Rupert Smith
>            Assignee: Rupert Smith
>             Fix For: M2
>
>
> I ran the following test:
> ./Ping-Once-Async.sh -n strange_redelivery_test -s[10] -c[1] persistent=false pubsub=false
transacted=true commitBatchSize=1 batchSize=1000 messageSize=256 destinationCount=1 uniqueDests=false
consTransacted=true numConsumers=4 broker=tcp://10.0.0.1:9000
> Which reports:
> .Got redelivered message, ignoring.
> Got redelivered message, ignoring.
> Got redelivered message, ignoring.
> Got redelivered message, ignoring.
> The test is delivering mesages, round robin to 4 consumers (2 is enough to show the problem),
on a common queue. The sender controls the test, and does not terminate the test until all
of the consumers have received and committed all of their test messages. The consumers will
commit their transactions at the end of the test.
> Either, something strange is happening, where messages that should have been acked because
they were committed are being redelivered on connection close, or, the connection is being
closed before all of the consumers have finished committing. In the latter case, the PPP test
is at fault and needs to be fixed.
> This problem does not show up when the consumers are using auto_ack.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message