Message struck in adapter engine with status Hold

[Former Member]

Hi,

In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)

where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?

Regards,

Krishna

[Former Member]

Hi All,

I had to cancel the messages starting from the bottom.

Regards,

Krishna

[naveen_chichili]

Krishna,

Restart java stark it will resolve your issue...

Regards,

Naveen

[Former Member]

Restart of Java Stack is required when the message is stuck in Delivering for a long time , Holding messages can be resent after clearing the messages which is blocking it.

- Muru

[former_member869100]

Hi All,

After restarting the Java system the issue is getting resolved, But after few days the issue is happening repeatedly...

Can you please suggest me the permanent solution for me instead of java system restart ?

Regards

Hari

[Former Member]

Hi Krishna,

Check is there any message corresponding this Business Service is stuck in Delivering or Failed .

If they are stuck clear them and resend these messages, they will move.

- Muru

[Former Member]

Hello,

Below is some information on how to resolve this type of issue:

1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.

2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.

3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.

4 - Sort the messages in ascending order based on the Sequence no.

5 - Check the predecessor message of the first message in status "HOLD"

Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:

a - Predecessor is in Failed State/System Error : Cancel/Resend the

first message in status HOLD after this. Then the remaining messages

can be cancelled/resent.

b - Predecessor is in DLVD state(delivered state) : First Holding

message can be resent/cancelled followed by the others.

c - Predecessor is in NDLV(Non-Delivered Status) : Check why the

predecessor message failed and correct the reason for the failure.

Then resend the predecessor message and then cancel/resend the

remaining HOLD messages. Alternatively, you can directly try

resending this NDLV predecessor message and see if it goes. If it

goes, then the remaining HOLD messages can be resent/cancelled.

Another option could be to cancel this NDLV predecessor message so

that it goes to FAILED state and then cancel/resend remaining HOLD

messages.

Regards,

Sarah

[Former Member]

chk this:

/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework