cancel
Showing results for 
Search instead for 
Did you mean: 

Messages are in Holding state in AE

Former Member
0 Kudos

Hi All:

I created one <b>JDBC to JDBC</b> scenario. XI pick data successfully but I am seeing messages are in

<b>Holding</b> state in Message Monitoring.

I am sure we cannot check the status of the queue's in AE, please let me know if I am not correct.

If anyone faced the same issue/problem please let me know what is the reason behind it and how we can resolve it.

Thanks in advance.

Farooq.

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

Check this

How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework

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

Regards,

Prateek

Former Member
0 Kudos

Hi prateek,

Really the great Blog !!

I tried the same approach...and I found one message with "System Error". I cancelled that message but what I observer that other messages was still

in the Holding state. So what I did I cancelled all the messages that were in

Holding state...and it solved my problem.

Really appreciate for the right answer

Thanks

Farooq.

Answers (3)

Answers (3)

Former Member
0 Kudos

From RWB --> message monitoring, choose Adapter Engine Messages and do a search for any messages that are in status "Error".

Your messages will be in holding if there is a message processed prior that is in status error and there is some sort of forced serialization....

Did you try this already?

If so, can you explain your JDBC to JDBC scenario a bit better in order to understand possible breakage points.

sincerely,

--NM

Former Member
0 Kudos

check whether yours message are stucked up in XI internal queues...

if yes unlock the queue using smq2/smq1 and release all the message from the queues...

Ranjeet

Former Member
0 Kudos

> check whether yours message are stucked up in XI

> internal queues...

I already mention I did JDBC 2 JDBC, so the queues got stucked in AE not in IE

> if yes unlock the queue using smq2/smq1 and release

> all the message from the queues...

That is not IS queue, messages are in success state in MONI..

Thanks

Farooq.

Former Member
0 Kudos

Hi Farooq,

Some times messages are in Holding state why because if any job is pending for that scenarios . So try to cancel the first job manually then otherjobs will process suggessfully. I have done the same for my problem also.

Warm Regards,

Vijay