Posted: Thu Jul 01, 2010 5:32 am Post subject: not capable of handling a message of data type ''''
Apprentice
Joined: 26 Sep 2008 Posts: 48
I have 2 flows. The first routes the message to the 2nd. No transformation. (SET OutputRoot = InputRoot )
Both MQInput nodes specify BLOB.
However, in the 2nd flow, the message stays on the input. Trace is below. HELP
UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion o
f incoming message of length 0 bytes beginning at offset '0'.
UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of inco
ming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
UserTrace BIP6069W: The broker is not capable of handling a message of data type ''''.
The message broker received a message that requires the handling of data of type '''', but the broker does
not have the capability to handle data of this type.
Check both the message being sent to the message broker and the configuration data for the node. Reference
s to the unsupported data type must be removed if the message is to be processed by the broker.
UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of inco
ming message of length '229' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
That is the end of the trace. The message does not go to the DLQ.
Using Broker v7.
That shouldn't be the end of the trace, unless the EG died?
Are you sure that the input message to the second flow doesn't have an RFH header on it, or a JMS header that indicates that it's Message Domain should be 'XMLS'? Is the content of the second message an XML document?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum