SXMB_MONI message fail causing Queue struck at SMQ2

[Former Member]

Hi All,

If mapping error occured in SXMB_MONI, corresponding entry will be struck up in SMQ2 and saying that SYSFAIL.

When i drill down this into further, it is saying that Mapping error.

Because of this all messages coming later also getting strucked in this queue.

Why is this happening and what to do for not to get struck further messages

Regards

[Former Member · Accepted solution]

Hello Vamsi,

In PI its process in order kind of thing. So if first message is stuck in one queue, other messages will get stuck in that queue.

You can apply this solution.

Create a job which will restart message after some time if it is stuck because of connection problem or something, then queue will be clear.

Second:

If you know that one of your interface is giving this type of error, then you can define special queue for that interface so it failior in that perticular interface will not stop your other messages.

Thanks,

Hetal

[Former Member · Accepted solution]

Hi Vamsi,

Looks like data serialisation has been implemented in your interface.

PI makes sure that all the messages for that interface are processed in sequence (EOIO). Incase of any message failure or error, the message will be stuck in the queue until its processed successfully.

Could you check the QoS for the following entry in SXMB_MONI? Is it EOIO ?

Regards,

Prajeet

[Former Member · Accepted solution]

Hi Hetal,

>>Create a job which will restart message after some time if it is stuck because of connection problem or something, then queue will be clear.

It's because of Mapping problem, even though we schedule a job to restart, it won't resolve. again it comes into same error.

@Prateej:

>>Could you check the QoS for the following entry in SXMB_MONI? Is it EOIO ?

QOS is Exactly Once

@Madu:

>>This is the standard behavior of PI. When some message will fail in Integration Engine(either because of Receiver not found or mapping error),some of remaining message(not all messages) which will come in the same queue of failed message will stuck.

You can not predict which messages will stuck and which messages will not stuck.

YES, you are right.

>>If you are having some important interface, which you want to divert the messages in other queue. You apply exactly once in order in sender channel for other interfaces so that these messages will not stuck in SMQ2.

For me all are Important Interfaces only. I can't prioritize

I think the better solution is Monitor failed messages in MONI every day and if it is failed because of Mapping error means, we can delete that entry from SMQ2.because for mapping related errors we don't require that message to restart again.

so that nothing will be queued after wards.

Regards

[madhusudana_reddy2]

Hi Vamsi,

This is the standard behavior of PI. When some message will fail in Integration Engine(either because of Receiver not found or mapping error),some of remaining message(not all messages) which will come in the same queue of failed message will stuck.

You can not predict which messages will stuck and which messages will not stuck. If you are having some important interaface, which you want to divert the messages in other queue. You apply exactly once in order in sender channel for other interfaces so that these messages will not stuck in SMQ2.

thanks,

madhu

[Former Member]

Hi,

Check the root cause of the error ...if possible correct it and then reprocess the message..so that all the messages stuck in queue can get cleared...

or else delete the message from the queue so that other messages cannot get stuck in queue...

HTH

Rajesh

[Former Member]

Hi Rajesh,

>>Check the root cause of the error ...if possible correct it and then reprocess the message..so that all the messages stuck in queue can get cleared...

Root cause is mapping failed in MONI, we can't correct it and not possible to restart at that stage.

>>or else delete the message from the queue so that other messages cannot get stuck in queue...

Deleting the caused entry and unlocking is working and getting free

In general is there any way get it done automatically ??

Because each and every time it's not possible to go and check the root cause and then deleting.

Regards