[jira] Updated: (AMQ-1792) Consumer stops work when another consumer commits

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully updated AMQ-1792:
----------------------------

    Priority: Major  (was: Blocker)

reducing severity, things are working as expected I think for this particular scenario.

One other thing to play with: ack Mode Session.DUPS_OK_ACKNOWLEDGE;
This will negate the production of the DeliveryAck and only one message, the prefetch value, will be dispatched/locked by a sleeping consumer.

> Consumer stops work when another consumer commits
> -------------------------------------------------
>
>                 Key: AMQ-1792
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1792
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: Win XP, Java 1.5
>            Reporter: Kevin
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>         Attachments: Situation.zip
>
>
> Hi *,
> 5 messages are put into a queue. 3 consumer are created, all with their own transacted-sessions. They all implements MessageListener.
> 2 consumers recieve a message, wait 5 seconds and commit their messages. The other consumer sends the recieved message back to the queue (no rollback!!!) and commit. When one of the first consumer commits, the third consumer stops working and doesn't recieve any messages.
> When you starts the attached Main-class (sets first the ip-address of your broker in the config-class) you'll see some output:
> Consumer-1 work begins!
> Consumer-2 work begins!
> Consumer-3 cant work!
> Consumer-3 cant work!
> [..]
> Consumer-3 cant work!
> Consumer-3 cant work!
> Consumer-1 work ends!
> Consumer-1 work begins!
> Consumer-2 work ends!
> Consumer-2 work begins!
> Consumer-1 work ends!
> Consumer-1 work begins!
> Consumer-2 work ends!
> Consumer-1 work ends!
> "Consumer-3 cant work" means, that consumer-3 sends a message back to the broker. "Consumer1-work begins" is the first code-line in the onMessage-Method, "Consumer1-work ends" the last one.
> I also attached the configuration file of the broker, maybe I made something wrong there.
> I hope this issue will not go unheeded like my other issue posted a week ago.

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