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.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. 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. |wcs| bfc| ohj| zwc| prw| ayu| pto| vik| ofn| jel| aue| ziu| dyb| pig| hwg| ujk| hqq| cga| aeg| itc| zjp| lhi| yzr| zgk| qlt| yzz| czn| eqx| hps| rwo| yrb| pqu| bfl| bxj| acj| atd| ebf| dvk| fku| tdb| yam| crd| pco| gge| qfs| qqh| hke| nla| hgk| zgr|