Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Correlation ID is coming as byte in service JMS



Correlation ID is coming as byte in service JMS

Error Messages

Correlation ID is coming as byte in service JMS

Steps to Reproduce

Correlation ID is coming as byte in service JMS

Root Cause

The root cause of this problem is a defect in customer application code/rules.

The correlation id is from the weblogic. MQ is giving in the bytes and which is getting changed at the weblogic level to hex. .

if (oLog.isDebugEnabled())

oLog.debug("Reading JMSCorrelationID header from JMS message");

headerName = "correlationid";

headerVal = aMessage.getJMSCorrelationID();


We are just displaying the same we are getting from the API.


Nothing much can be done from our side as we are using standard jar to get the correlation Id from the JMS.
The limitation can be overcome from the custom java code but the catch is, it should have fixed correlation id length.

Untested work around:

Edit BrowseMQServerMessages activity which is in available mode and replace
// converts the byte[] to hex string
hexMsgID           = utils.toHexString(message.messageId); with
//converts byte[] to String
hexMsgID           = new String(message.messageId);
and check the hexMsgID with the incoming Correlation ID from JMS Listener.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us