Closed chandan84 closed 2 years ago
Do these concerns relate to the AMQP client or to IBM MQ ?
I see that you also raised this as a question on stackoverflow - https://stackoverflow.com/questions/69270996/apache-qpid-client-to-ibm-mq-broker-v-9-1-0-6-request-reply-pattern-with-que
Where it has been answered.
Below is a summary of the AMQP client we have trying to build to evaluate request / response message pattern with IBM MQ. The end of the mail contains the concerns am still facing. Could you help create an IBM ticket on the issue to get their feedback. Typically how many days do we have to wait before we get a response ?
AMQP channel setup with the below properties, and is available at wmqt0041:5672. Properties of the channel are below.
To access an existing queue via the channel, a subscription was setup - /comet/interim/claim. The subscription was mapped to queue endpoint – COMET.INTERIM_CLAIMQ. The below client is configured to
a. Send a message and pickup the message using jms correlation id from the same queue endpoint. b. Set the JMS Message Type to MQSTR c. Set reply to end point as /comet/interim/claim – subscription created to access COMET.INTERIM_CLAIMQ.
Client code is below
The message that was received at queue COMET.INTERIM_CLAIMQ is a put below
Concerns – a. Format still shows MQHRF2 instead of MQSTR. b. ReplyToQ property shows blank. [First to concerns are high priority] c. The message body contains tag To as -/comet/interim/claim , What does this indicate ?
d. It also contains tag topic:///comet/interim/claim . The relyTo destination we are setting in the code is a Queue, Why does it get translated into a topic:///?