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

Connect MQ issue



User reported that they were seeing special characters being appended in XML messages which was placed in MQ queue using Connect-MQ rule.

Error Messages

2016-02-24 06:07:50,319 [5956] ERROR Drs.Queue.ConnectQueue - GetMQMessage <> System.Xml.XmlException: Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 1, position 2.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos)

Checked the messages available in MQ queue using MQ monitor
<!-- Hold --> Client for Java<<InvestOneDataRequest xmlns:xsi=""> <MessageId>FFD-DRV-99498-03032016-014725</MessageId> <Requests> </Requests> </InvestOneDataRequest>
Not sure how '<' character gets amended at the start of the XML message.

Steps to Reproduce

Post the XML message to MQ using Connect MQ

Root Cause

When sending message to MQ it is appending special character to the request - ''Client for Java<" which is resulting in message being rejected.


Suggested below change by Engineering team to resolve the issue.
  1. Search for invokemqconnector
  2. Open the InvokeMQConnector
  3. Search for the line reqMsg.writeInt(stringVal.length());
  4. Comment the line. Append // to the line
  5. Save the activity. And execute the activity.
User tested the changes in dev environment and confirmed the solution in dev environment.


Published April 1, 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