Why stuck/failed message are moved to SMQ3 automatically

[Former Member]

Dear experts,

I am facing the issue below:

message failed in PI as no receiver found(only certain values of a field, like ID = "A" from source payload will get processed, else failed in receiver determination), then it got moved to SMQ3 "automatically".

I understand that we can move a failed/stuck message to SMQ3 manually first and let other pending message go immediately, and analyse this failed/stuck message later, in this way, it won't make other message pending just because this message stucked.

But how this message get moved to SMQ3 automatically, as I don;t want it to be in SMQ3, just failed in SMQ2 is fine...

Can anyone explain me why it is moved to SMQ3, any settings for this, or any relationship with EOIO mode in sending the message or anything else.

Thanks a lot.

[former_member303666 · Accepted solution]

Hi,

It should not happen like that. the process is, once messages are failed in queues, manually we can move that failed messages to SMQ3 for processing the rest of messages. later we can investigate the SMQ3 failed message.

let's see the reply from others.

Regards,

Kesava.

[Former Member · Accepted solution]

Seems no others are replying..:(

[ambrish_mishra · Accepted solution]

Hi... I have posted a reply

[ambrish_mishra]

Hi,

Please check the thread:

http://scn.sap.com/thread/2038934

the SAP note within the thread holds the answer. 

Probably someone implemented the SAP note in your system by mistake

Cheers,

Ambrish

Message was edited by: Ambrish Mishra

[Former Member]

the links for the intended blog is not valid.. I can't open the page..

Can you please share me the link which is referred in your referring blog?

thank you so much.

[ambrish_mishra]

SAP Note 441269.

This talks about automatic reaction to a message which is stuck in a particular  queue.