Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Won't Fix or Usage Issue
-
Affects Version/s: 3.1.0
-
Fix Version/s: None
-
Component/s: Core: Deployment, Transport: JMS
-
Labels:None
-
Environment:
windows, ActiveMQ 5.4.2 JDK 6
-
User impact:High
-
Configuration:
-
Similar Issues:None
Description
steps to reproduce:
1. start activemq 5.4.2, start mule 3.1.0
2. deploy testjms.zip
3. goto Http://localhost:8161/admin/queues.jsp, verify that there are 4 consumers on testjms.queue
4. click "send to" link to send a message to Queue testjms.queue, verify that message get consumed.
5. touch mule-config.xml, save it. testjms app is hot deployed with a bunch of Exceptions
6. refresh Http://localhost:8161/admin/queues.jsp now there are 8 consumers on testjms.queue
7. click "send to" link to send another message. this time, the message forever stuck in the queue
Any progress on this, or does someone have a workaround? , cause it makes redployment pretty much useless at this point.
As most of my services have JMS connections.