StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I believe the middleware people are wrong:</p> <blockquote> <h3>JMSMessageID from MQMD MessageID</h3> <p>All messages sent from JMS have unique message identifiers assigned by WebSphere® MQ. The value assigned is returned in the MQMD messageId field after the MQPUT call, and is passed back to the application in the JMSMessageID field. The WebSphere MQ messageId is a 24-byte binary value, whereas the JMSMessageID is a string. The JMSMessageID is composed of the binary messageId value converted to a sequence of 48 hexadecimal characters, <strong>prefixed with the characters ID:</strong>. JMS provides a hint that can be set to disable the production of message identifiers. This hint is ignored, and a unique identifier is assigned in all cases. Any value that is set into the JMSMessageId field before a send() is overwritten.</p> </blockquote> <p>From: <a href="http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fuj25470_.htm" rel="nofollow">Mapping JMS header fields at send() or publish()</a>.</p> <p>Also I remember noticing that prefix while working with JMS-WebsphereMQ bridge. But actually - why do you care? <del>This is a <code>String</code> id, the specification doesn't say anything about its structure, except that it has to be unique.</del></p> <p>UPDATE: Actually, as mentioned by <em>@skaffman</em>, the <code>ID:</code> prefix is required by <a href="http://download.oracle.com/otndocs/jcp/jms-2_0-edr-spec/index.html" rel="nofollow">JMS specification</a>:</p> <blockquote> <h3>3.4.3. JMSMessageID</h3> <p>All <code>JMSMessageID</code> values must start with the prefix ‘<code>ID:</code>’. Uniqueness of message ID values across different providers is not required.</p> </blockquote> <p>This means that WebsphereMQ bridge is adding <code>ID:</code> prefix only to be compliant with JMS spec. And, as also noted by <em>@skaffman</em>, ActiveMQ is not compliant with it...</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload