A remote application sends messages with unique correlation IDs to a WebSphere MQ queue where a WMQ JMS application that is running as a Message Driven Bean (MDB) in a WebSphere Application Server (WAS) will get the messages. Intermittently, the WAS MDB application will do an MQGET for a message and will receive a message with the same correlid two times. The WebSphere MQ JMS bindings provide various correlation schemes that are used to determine how to correlate request messages with response messages. RequestMsgIDToCorrelID The JMSMessageID is copied to the JMSCorrelationID field. This is the default setting. RequestCorrelIDToCorrelID The JMSCorrelationID is copied to the JMSCorrelationID field. The ApplicationX is doing request/response and uses the following to get and write the Correlation Id to the response message: String [] split = requestHeaders.getJMSMessageID ().split ("ID:"); jmsResponseHeaders.setJMSCorrelationID (split [1]); We use the "getJMSMessageID ().split ("ID:")" because the JMSCorrelationID is "null" at that point. 1. Req/Resp matching : If your GUID is unique for each message then you can use the same to correlate request and response message. Other option is to get the message ID from the request and then set as correlation Id in the response message. For more details check here: IBM WebSphere MQ request/reply scenario.Example 1: An MQ Service Uses a JMS Message ID as a Correlator of the Request-Response Message In Figure 2-1, the server that hosts the MQ service in the request-response communication echoes the request message ID to the response correlation ID, and sends the response to the replyTo queue. The response travels back and is correlated using the |ipc| uov| jbh| zyx| wfe| eqa| fct| zgd| ctu| epk| yqn| yjw| bpq| hkb| eei| doz| rod| ilv| pxp| nvp| mkf| jex| eyy| wsi| uez| lmr| upj| kyj| vbj| dxi| uoj| lmw| epr| kfu| vov| kdl| ges| ogn| snt| cce| agu| buq| jti| oxc| ouk| fhb| yax| pnn| hba| apy|