[jira] [Comment Edited] (AMQ-4223) Messages being distributed to exclusive consumers!

["David Johle (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612760#comment-13612760 ] 

David Johle edited comment on AMQ-4223 at 3/25/13 4:00 PM:
-----------------------------------------------------------

FWIW I am still seeing this issue on occasion.  I have not made any changes to the system (optimizeAcknowledge has remained false) since opening this issue.  It runs fine for a while (as in months on end) and then just decides one day to start violating the exclusive consumer logic.

Restarting my application doesn't really help at all.
Deleting the activemq datastore doesn't really help much either.

So now I have to keep it limping along until it randomly decides to stop stumbling on this issue and run smooth for a while again.
                
      was (Author: djohle):
    FWIW I am still seeing this issue on occasion.  I have not made any changes to the system (optimizeAcknowledge has remained false) since opening this issue.  It runs fine for a while (as in months on end) and the just decides one day to start violating the exclusive consumer logic.

Restarting my application doesn't really help at all.
Deleting the activemq datastore doesn't really help much either.

So now I have to keep it limping along until it randomly decides to stop stumbling on this issue and run smooth for a while again.
                  
> Messages being distributed to exclusive consumers!
> --------------------------------------------------
>
>                 Key: AMQ-4223
>                 URL: https://issues.apache.org/jira/browse/AMQ-4223
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.7.0
>         Environment: RHEL5, Java 1.6
>            Reporter: David Johle
>            Priority: Minor
>
> Now that AMQ-3664 is out of the way I thought I could turn on optimizeAcknowledge back on as long as I gave it some decent timeOut & scheduledAckInterval values.
> Well, it turns out the behavior I was seeing still happens, and I think now it's clearer that it is something else, just was partially masked by that other issue.
> My configuration is a "network of brokers" two brokers with a producer on each one, and a consumer on each one.  The consumers are set up with exclusive=true as their part of my application is an "aggregation" step.  I'm using the exclusive mode to ensure that only one of them receives all the messages, and the other is essentially a standby/backup in case the first one is offline.
> When I have optimizeAcknowlege enabled, I see a situation where it is distributing (fairly equally, in fact) the messages to both of the consumers.  When I set that to false, all the messages funnel into the currently active consumer as expected.
> I cannot find anything that says these are incompatible features, and cannot figure out what it is that causes this behavior.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira