Block queue in sync/Async Bridge HTTP -> PI -> SOAP scenario

[Former Member]

Hi Everyone

I'm handling a BPM sync/Async Bridge HTTP -> PI -> SOAP scenario

Normally, the scenario works OK, but when a malformed message arrives to PI, it blocks the queue that receives it. We have to go to the transaction SMQ2 to delete the bad message and manually unlock the queue so it can continue processing the messages. This is not optimal because the client is not willing to handle this manually.

What can I do so, when it receives a malformed message, it deletes it automatically so the queue doesn't gets blocked?

Some images from transaction SMQ2 are attached.

Thanks a lot.

PD: The error showed to the sending system is:

<SAP:Code>INTERNAL.PL_TIMEOUT</SAP:Code><SAP:Stack>Timeout condition of pipeline reached</SAP:Stack

[Former Member]

Hi Christina,

You can set the following parameters in the Integration Engine TUNING category.

EO_RETRY_AUTOMATIC = 0

EO_RETRY_AUT_COUNT = <N>

With these settings in place, when a message errors out in a regular queue, it is automatically moved to a different queue (error queue) so as to keep the regular queue from being blocked.

After "N" number of messages in the error queue, all errored messages in the error queue are re-executed.

No sure, in your case, if you needed the errored messages re-processed or just deleted.

Hope this helps!

Regards,

Goverdhan Madipadiga

[arunneerolil]

Hi Cristina,

A workaround would be to use Java Http Adapter at the sender side and XML payload validation at the sender adapter side so that the malformed messages won't reach the ABAP stack queue.

regards,

Arun