Bug 1336341

Summary: [GSS](6.4.z) In rare circumstances HornetQ MessageProducer can send a message to wrong queue.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tom Ross <tom.ross>
Component: JMSAssignee: Tom Ross <tom.ross>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.6CC: bmaxwell, chaowan, egonzale, jmesnil, jtruhlar, msochure, pmackay, rnetuka, sappleto, tom.ross
Target Milestone: CR1   
Target Release: EAP 6.4.9   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1336413 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1324262, 1325387, 1336413, 1344286    

Description Tom Ross 2016-05-16 08:37:41 UTC 
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.
Comment 5 JBoss JIRA Server 2016-05-31 07:59:40 UTC 
Miroslav Sochurek <msochure> updated the status of jira HORNETQ-1522 to Resolved
Comment 7 Peter Mackay 2016-06-28 10:37:04 UTC 
Verified with EAP 6.4.9.CP.CR2
Comment 8 JBoss JIRA Server 2016-07-18 07:19:32 UTC 
Bartosz Baranowski <bbaranow> updated the status of jira JBEAP-4721 to Resolved
Comment 9 JBoss JIRA Server 2016-08-24 10:51:48 UTC 
Peter Mačkay <pmackay> updated the status of jira JBEAP-4721 to Reopened
Comment 10 JBoss JIRA Server 2016-09-01 07:57:21 UTC 
Bartosz Baranowski <bbaranow> updated the status of jira JBEAP-4721 to Resolved
Comment 11 JBoss JIRA Server 2016-09-07 12:35:43 UTC 
Peter Mačkay <pmackay> updated the status of jira JBEAP-4721 to Reopened
Comment 12 JBoss JIRA Server 2016-09-19 13:38:18 UTC 
Peter Mačkay <pmackay> updated the status of jira JBEAP-4721 to Resolved
Comment 13 Petr Penicka 2017-01-17 12:59:51 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 14 Petr Penicka 2017-01-17 13:02:41 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.