Message status "Holding" - Message monitoring adapter framework

[Former Member]

Hello,

We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.

Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.

I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"

The blog does not mention what to do when the first message (sequential number) is not available anymore.

Is it possible to restart the messages in the queue in that case?

Thanks

Kind regards

Frank

[Former Member]

Hi Frank,

Find the sequential number and serialization context of the holding message and then

go to the messaging system of the adapter i.e http://host:port/MessagingSystem/monitor/monitor.jsp and select tab

EOIO sequence monitor there you can find all the EOIO messages stuck along with its predecessor and respective state of the same

Set the state of the same to the Failed or try redeliver if it works and resend the next hold message

HTH

Rajesh

[abhijitbolakhe]

Hi

The messages usually goes in 'Holding' Status for Quality of service EOIO.

Generally this happens in case of Multimapping where multiple files are generated from one source message.

To avoid message 'Hold' status

go to Interface determination ...... and uncheck the check box 'Maintain Order at Runtime' under Quality of Service.

After this change the messages will not go into 'Holding' Status.

This change will solve your issue....

Regards

Abhijit

[former_member200962]

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.

I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed

From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and 
resend or cancel the message to release the queue.

Regards,

Abhishek.

[Former Member]

You can't restart that message,just delete it.

for future use alert for stucked message and schedule the report RSQIWKEX/RSQOWKEX for restart the stucked/failed messages.