[
https://issues.apache.org/jira/browse/AMQ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ashwini kuntamukkala updated AMQ-3110:
--------------------------------------
Output from the test when executed....
Two queues:
1. test.queue (message redelivery policy is indefinite, i.e., -1)
2. test.exception.queue
Both has a message each.
test.queue has an asynchronous consumer which throws exception causing
rollback.
Message is moved from test.queue to test.exception.queue. The new message count
is
test.queue has zero messages
test.exception.queue has 2 message (1 from earlier, 1 that was just moved)
Bug:
The consumer on test.queue continues to receive the message that was moved out
to test.exception.queue!!
----------------------------------------------
2010-12-30 14:00:51,674 INFO (BrokerService) - Using Persistence Adapter:
MemoryPersistenceAdapter
2010-12-30 14:00:51,674 INFO (BrokerService) - ActiveMQ 5.3.0 JMS Message
Broker (localhost) is starting
2010-12-30 14:00:51,674 INFO (BrokerService) - For help or more information
please see: http://activemq.apache.org/
16 [JMX connector] INFO org.mortbay.log - Logging to
org.slf4j.impl.SimpleLogger(org.mortbay.log) via org.mortbay.log.Slf4jLog
2010-12-30 14:00:52,096 INFO (BrokerService) - ActiveMQ JMS Message Broker
(localhost, ID:akuntamukkala-4986-1293739251721-0:0) started
2010-12-30 14:00:52,127 INFO (ManagementContext) - JMX consoles can connect to
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
2010-12-30 14:00:52,143 INFO (TransportConnector) - Connector vm://localhost
Started
Thu Dec 30 14:00:52 CST 2010 : Number of messages in test.exception.queue = 1
Thu Dec 30 14:00:52 CST 2010 : Number of messages in test.queue = 1
Thu Dec 30 14:00:52 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:52 CST 2010 : Number of messages in test.queue after MOVE = 0
Thu Dec 30 14:00:52 CST 2010 : Number of messages in test.exception.queue after
MOVE = 2
Thu Dec 30 14:00:52 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:53 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:54 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:55 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:56 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:57 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:58 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:00:59 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:01:00 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
Thu Dec 30 14:01:01 CST 2010 - Message received by consumer =
ID:akuntamukkala-4986-1293739251721-2:0:1:2:1
2010-12-30 14:01:02,486 INFO (BrokerService) - ActiveMQ Message Broker
(localhost, ID:akuntamukkala-4986-1293739251721-0:0) is shutting down
2010-12-30 14:01:02,486 INFO (TransportConnector) - Connector vm://localhost
Stopped
2010-12-30 14:01:02,502 INFO (BrokerService) - ActiveMQ JMS Message Broker
(localhost, ID:akuntamukkala-4986-1293739251721-0:0) stopped
> Same message redelivered again even though moved to a different queue using
> web console
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-3110
> URL: https://issues.apache.org/jira/browse/AMQ-3110
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Environment: Windows XP
> Java 1.6
> Reporter: ashwini kuntamukkala
> Priority: Critical
>
> I have a queue which has 1 asynchronous consumer. Underlying connection has a
> redelivery policy where max retries is set to -1 (Indefinite).
> When a bad message is stopping the rest of the messages in the queue, I use
> webconsole/jconsole to move the message to an exception queue. However, the
> same bad message is being resent to the consumer.
> The problem goes away only when I restart the broker. This is not an
> acceptable solution.
> I have attached a junit test so you can understand this scenario better.
> Thanks,
> Ashwini Kuntamukkala
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
