Skip to Content
0
Former Member
Feb 16, 2009 at 12:22 PM

Error 'Unable to determine receiver'

57 Views

Hi Gurus!!

I have a scenario where a third-party send a message using the JMS Adatper.

There are several receivers, depending if exists a tag on the XML.

I have added a receiver, with a rule of this type: (/MT_HOST/D35_DIR EX).

This tag exits on the XML, but this receiver is not taken.

This scenario runs perfectly with other receivers (the XML has another tag like D34_CODIGO9).

I see on the trace this:

<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/MT_HOST/D35_DIR")% EX</Trace>

<Trace level="2" type="T">......extracting (new) for Extractor: XP /MT_HOST/D35_DIR</Trace>

<Trace level="2" type="T">......new reader had problems - try old one</Trace>

<Trace level="2" type="T">...invalid Receiver: - IP_BPM_DIR</Trace>

<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>

<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/MT_HOST/D34_CODIGO9")% EX</Trace>

<Trace level="2" type="T">......extracting (new) for Extractor: XP /MT_HOST/D34_CODIGO9</Trace>

<Trace level="2" type="T">......new reader had problems - try old one</Trace>

<Trace level="2" type="T">...invalid Receiver: - IP_BPM_PetCodigo</Trace>

<Trace level="2" type="T">Check conditions for rule line no. 3</Trace>

<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET

Somebody knows waht could be the cause of this?

Thanks and regards,

Manuel.