[jboss-jira] [JBoss JIRA] (WFLY-11143) Message sent to JMSReplyTo from old client does not find correct binding

[Miroslav Novak (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646643#comment-13646643 ] 

Miroslav Novak edited comment on WFLY-11143 at 10/11/18 9:49 AM:
-----------------------------------------------------------------

[~martyn-taylor] Even [~ehugonnet]] has fixed the prefixes then I think workaround cannot help in this case. MDB is consuming message from InQueue and it does not know if it was sent by old/new client. Thus when it processes the message and sends response to reply queue then it does not know if prefix should be used or not. 


was (Author: mnovak):
[~martyn-taylor] Even [~eeshet] has fixed the prefixes then I think workaround cannot help in this case. MDB is consuming message from InQueue and it does not know if it was sent by old/new client. Thus when it processes the message and sends response to reply queue then it does not know if prefix should be used or not. 

> Message sent to JMSReplyTo from old client does not find correct binding
> ------------------------------------------------------------------------
>
>                 Key: WFLY-11143
>                 URL: https://issues.jboss.org/browse/WFLY-11143
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Miroslav Novak
>            Assignee: Martyn Taylor
>            Priority: Blocker
>
> 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.
> Test Scenario:
> * 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
> Result:
> No message is received from OutQueue. There is debug message in server log:
> {code}
> 11:36:09,565 DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-25 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5 at 22848193)) Message CoreMessage[m
> essageID=214,durable=true,userID=c0de8bd0-cba6-11e8-840f-f496342f6705,priority=4, timestamp=Tue Oct 09 11:36:09 CEST 2018,expiration=0, durable=true, address=jms.queue.OutQueue,size=580,properties=TypedPropertie
> s[inMessageId=ID:c0383a39-cba6-11e8-95ad-f496342f6705,__AMQ_CID=c0d9349a-cba6-11e8-840f-f496342f6705,_AMQ_DUPL_ID=90d1e80e-116d-4eef-9513-84c6085549db,_AMQ_ROUTING_TYPE=0]]@1680840457 is not going anywhere as it
>  didn't have a binding on address:jms.queue.OutQueue
> {code}
> 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.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)