Under specific conditions a HornetQ Message producer sends a message to a wrong queue. To reproduce the issues follow the steps: - configure a queue (Q1) with address-full-policy = FAIL - fail the queue with messages - create a JMS client which does following - creates connection - creates session - creates message producer(Q1) - sends a message to the queue (Q1) that is full - after receiving an error closes message producer - creates message producer that points at different queue (Q2) - send few messages to that queue (Q2) - at this point the first queue (Q1) gets drained - create message producer that points at original queue (Q1) - send message to Q1 but the message gets delivered to Q2.
Miroslav Sochurek <msochure> updated the status of jira HORNETQ-1522 to Resolved
Verified with EAP 6.4.9.CP.CR2
Bartosz Baranowski <bbaranow> updated the status of jira JBEAP-4721 to Resolved
Peter Mačkay <pmackay> updated the status of jira JBEAP-4721 to Reopened
Peter Mačkay <pmackay> updated the status of jira JBEAP-4721 to Resolved
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.