cancel
Showing results for 
Search instead for 
Did you mean: 

Could not acquire EOIO sequence ID lock with timeout period of 5 minutes

Former Member
0 Kudos

We are having an issue with Messages blocked in the Queue for Asynchronous RFC adapter.

The issue started with ICM_HTTP_TIMEOUT and then upon trying to force a retry, The error message changed to Could not acquire EOIO sequence ID Lock. But as a side effect one another Queue also started behaving the same now..

The whole system is not down, Just two of the message types. We still have about 5 other Messages flowing thru the RFC adapter..

We are at a loss now.. and have no clue what we have to look for and where.... Any suggestions would help ?

-Shree

Accepted Solutions (1)

Accepted Solutions (1)

prabhu_s2
Active Contributor
0 Kudos

register the que in q'adminstration and check out the message flow

Former Member
0 Kudos

Queue's are regiestered.. and there is no flow. The Queues are in SYSFAIL Status.. on repeated ReStart's of Messages. The message would go to Technical routing and stop there for a couple of miniutes, before turning into Error and stopping the Queue again.

Former Member
0 Kudos

delete those queues with error from the queue monitor and send the same messages again and check

Former Member
0 Kudos

Yep did that (Delete the entries in the Queue), next message would come and wait in the same error state.... Currently I have 15 Messages in the Queue,

prateek
Active Contributor
0 Kudos

Have u seen this

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Regards,

Prateek

Former Member
0 Kudos

Thx for the message,, But yes, Thats the process, we are using to restart messages since this morning... No luck.. Everytime we are struck at the same message...EOIO sequence ID Lock

Former Member
0 Kudos

Hi Shree !

We have the same issue. Did you solve it ? How?

Regards,

Matias.

Answers (0)