[ 
https://issues.apache.org/jira/browse/AMQ-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved AMQ-5763.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 5.12.0
         Assignee: Robbie Gemmell  (was: Timothy Bish)

Ok, I need to take that back, I figured out the reason and whilst the client 
isn't handling it particularly well the core problem is on the broker, which 
isn't replenishing the transaction controllers link credit. As a result it is 
unable to begin the 501st transaction due to using the given initial 1000 
credits to declare and discharge the previous 500 transactions.

Fixed in commit 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=fa81c1ff732fd50312ba349c8226c2d84345ad1d

> Consume messages in transactions with AMQP stop after 500 messages
> ------------------------------------------------------------------
>
>                 Key: AMQ-5763
>                 URL: https://issues.apache.org/jira/browse/AMQ-5763
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.11.1
>            Reporter: Jiří Dudek
>            Assignee: Robbie Gemmell
>             Fix For: 5.12.0
>
>         Attachments: amqptxerror.zip
>
>
> I try to consume messages via AMQP in transactions (1 message per 
> transaction),  The consumption is stopped exactly after 500 messages. I am 
> using qpid-jms AMQP client, but i have also reproduced this issue using 
> SwiftMQ AMQP client. This issue happen only with ActiveMQ (my version is 
> 5.11.1). For example on Qpid Java Broker(version 0.32) it is working 
> correctly.
> I have created sample test which may be used for issue reproduction. For 
> reproduction please use following instructions: 
> # Download amqptxerror.zip
> # Unzip.
> # Import pom.xml to your favorite IDE.
> # Start your ActiveMQ broker or run maven with "-p broker".
> # Run src/test/java/AMQPTxTest.java.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to