Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Troubleshooting: "Check length prefix" error from service MQ rules

Updated on October 28, 2020

Symptom

Service MQ Rules allow external systems to access your application data using the WebSphere MQ middleware messaging standard.

At runtime, an MQ listener, linked to a service MQ rule, waits and listens for incoming messages on a specified WebSphere MQ queue. You can configure MQ Listener to access text from an external system and place it in a clipboard property as follows:

  1. Create an MQ Service rule.
  2. Create an MQ Listener rule.
  3. Place the desired text in the queue.

When you run this configuration, the following error may appear in the log file:

com.pega.pegarules.pub.PRRuntimeException: Attempting to read string from MQ > 1M in length. Check length prefix on string data.

This error is caused by an incorrect setting in the Data Type field on the Request tab of the Connect MQ rule form:

 

Solution

To resolve this issue, select All Chars from the Data Type drop-down menu and save the updated rule. This allows Process Commander to read the text in the queue as ASCII characters and manages the data correctly:

After making the rule change, stop and re-start any MQ Listeners that were running when you made the change.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us