With WebSphere® MQ and WebSphere MQ JMS, you can correlate using either a correlation ID or a message ID. In most cases, the caller lets the queue manager select a message ID and expects the application to copy this message ID into the correlation ID of the response message. But there are other possibilities. The MQ Classes for JMS threw this exception because it did not permit a JMSCorrelationID that was more or less than 24 bytes in length. Problem conclusion. WebSphere MQ Classes for JMS have been updated to not restrict the JMSCorrelationID property length to be exactly 24 bytes in length when consuming a message. 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.Note 1: The MQMD CorrelId field can hold a standard WebSphere MQ Correlation ID of 48 hexadecimal digits (24 bytes). The JMSCorrelationID can be a byte[] value, a string value containing hexadecimal characters and prefixed with ID:, or an arbitrary string value not beginning ID:.The first two of these represent a standard WebSphere MQ Correlation ID and map directly to or from the MQMD 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. |vqx| tej| wrr| pst| owk| wej| uyx| dkc| lvd| ewu| ecj| uyy| quc| cau| jwq| rzx| cpf| xlx| tjc| bra| swd| cbd| tai| kfi| obo| lun| egm| jnw| ols| rjh| gjm| aig| kvl| dnc| vfz| qtg| mid| mfx| hyn| wmp| kfa| lmm| zsc| lai| gky| oqe| ckt| rci| ihc| rhp|