on 01-04-2009 5:32 PM
i have a file2mq scenario (Exactly Once In Order as service quality). for some reason the messages are now jammed in the EOIO queue. I get this feedback via the RWB message monitoring; there i can see some of the scenario's messages are at "Holding" status (Unknown reason). when i try to delete or re-send messages (i mark them all) i get Err (in case of deletion) or "green light" in case of re-send; yet, few seconds later messages are back in "Holding" state.
How can i delete/re-send all messages in queue?
why is it hapening? how can i avoid it next time?
additional observation:
when i count "all" messages i get 92 (e.g.).
when i count "successful" messages i get 92 (e.g.).
when i count "Holding" messages i get 22 (e.g.).
isn't that weird?
BTW,
can any one point a usefull link so i'll be able to understand the differnt between "Holding" && "Waiting".
Regards
Uri
in our case we experienced "black magic". the only way it was eventually solved was by useing "brute force" (i.e. delete and re-org db by basis guy).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. If you used any Message split in XI it will turn yiour messages QOS from EO into EOIO.
2.also possible is that your interface is waiting for acknowledgement from the target system.
Please check.
Edited by: Nimrod Gisis on Jan 6, 2009 3:46 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
This blog should help answer your query and even solve it,
[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
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The holding status could be understood here
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Waiting status occurs when the adapter engine tries to post the message to the receiver system but due to some problem (unable to connect or receiver down etc..) it is unable to send it, so message goes into waiting status. It retries sending data after particular interval (default 3 retries at interval of 5 mins). After this the message goes into System Error status.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey,
Stefan weblog will help
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Cheers
Agasthuri Doss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.