AMQ broker does not honour consumer priority setting on queue
-------------------------------------------------------------
Key: AMQ-1939
URL: https://issues.apache.org/activemq/browse/AMQ-1939
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.1.0
Environment: WinXP, SLES9, WinNT4
Reporter: Bonny Rais
Priority: Blocker
We have a simple setup where an AMQ broker is connected to from one producer
and two consumers. The producer tends to be colocated on the broker's host so
comms is never an issue there. However, consumers can come and go because the
underlying comms may not be reliable.
The consumers are connected with differing priorities so that the broker
directs all messages to a single consumer normally and switches over to the
other consumer when the primary consumer disconnects for whatever reason.
This arrangement seems to work fine most of the time, but sometimes (and we
cannot identify the cause), upon a comms error
or a consumer error (that may mean messages are not acknowledged within some
time period), the broker switches over to the
secondary consumer. That in itself if good, of course. However, when the
primary consumer reconnects back to the queue as
primary, messages are not being delivered to it at all - the only way to fix
this seems to be to restart the broker.
We cannot even force the broker to drop the connections (we're limited in the
way we can use jconsole with those brokers, particularly with the WinNT ones).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
