AppD agent header singularityheader caused the message flow in IBM Integration Bus v10 failing to parse XML message body

[Liping.Zhang]

We had some message-parsing issue in IBM Integration Bus message flow after enabling the exit of AppD agent. The AppD header singularityheader injected in the message header caused the error "An invalid XML character (Unicode: 0x73) was found in the prolog of the document" when SOAPRequestNode parses the XML message body . 0x73 is the first letter of header name "singularityheader".  So the flow counted the header singularityheader as beginning part of the message content, which makes the content as invalid XML format.  This happened in the message flows that have SOAP Request node.  Is there anyone had the similar issue? Any advice will be appreciated. 

[Ryan.Paredez]

Hi @Liping.Zhang,

I did some digging around and found this. I hope it's able to lead you to some further investigation.

In this case it is almost certainly the singularityheader injected by the agent which is at fault (Unicode: 0x73 is lowercase 's')