Resolution: Duplicate Issue
Affects Version/s: AMQ 7.2.1.GA
Fix Version/s: AMQ 7.2.2.GA
Sprint:AMQ Sprint 3219, AMQ Broker 1119
Steps to Reproduce:Steps to reproduce: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout master groovy -DEAP_ZIP_URL=http: //download.eng.brq.redhat.com/devel/candidates/JBEAP/JBEAP-7.2.0.CD14.CR2/jboss-eap-7.2.0.CD14.CR2.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=JcaTestCase#testReplyTo -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.CD13.CR2 | tee log
There is regression in backward compatibility of messaging client. JMSReplyTo destination set by older client contains incorrect address which causes that reply message does not have correct binding and such message is lost.
Impact: Applications will stop work after upgrade to WF14/EAP 7.2.0.CD14.
- Start EAP 7.2.0.CD14/WF14 server (Artemis 2.x) with deployed InQueue and OutQueue
- Send message to InQueue from older EAP 7.2.0.CD13/WF13/Artemis 1.5.5 client to InQueue. Message has JMSReplyTo header set to OutQueue. Client got "OutQueue" queue from JNDI lookup from EAP7.2.0.CD14/WF14
- Deploy MDB to server
- MDB consumes message from InQueue and sends new message to destination defined in JMSReplyTo header (so to OutQueue)
- Receive message from OutQueue
No message is received from OutQueue. There is debug message in server log:
which indicates that jms.queue.OutQueue address does not have a binding.
The same happesn if older EAP/WF server (with Artemis 1.5.5x) is used and new EAP 7.2.0.CD14/WF14(Artemis 2.x) client is used.