activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-4353) Behavior of "Exclusive Consumer" configured for queues on AMQ : Behavior of Master Slave Topology
Date Tue, 07 May 2013 23:21:17 GMT

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

Timothy Bish closed AMQ-4353.
-----------------------------

    Resolution: Incomplete

Not test case to reproduce the issue.  
                
> Behavior of "Exclusive Consumer" configured for queues on AMQ : Behavior of Master Slave
Topology 
> --------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4353
>                 URL: https://issues.apache.org/jira/browse/AMQ-4353
>             Project: ActiveMQ
>          Issue Type: Task
>          Components: activemq-leveldb-store, Broker
>    Affects Versions: 5.5.1
>         Environment: Linux,AMQ 5.5.1
>            Reporter: Jessy
>
> I noticed the following behavior when I set “Exclusive consumer” property for a queue
configured on AMQ 5.5.1 installation
> If say for Queue A, there were 2 consumers : con1 and con2 , both consumers are up all
the time .
> Say, one of them con1 becomes the master and consumes the message
> Successive message are not consumed by  con1, where-in con2 is also found to consume
the message..
> There is alternative consumption ,once by con1 and con2.
> Master is not the master all the time ..even if  master is up,slave consumes the message
in alternative fashion.
> Is this the intended behavior for “Master-Slave” paradigm?
> Is there any API exposed to identify which is the master and slave ,which would help
us in our logging to identify which is the current consumer of the message.

--
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

Mime
View raw message