on 07-19-2007 5:24 PM
Hi All:
I just would like to know in what conditions the message <b>got stucked in EOIO queue in Adapter Engine?</b>Thanks in advance..
<b>Regards,</b>
Farooq.
If it's EOIO processing, then failure of one causes everything behind it to go into Holding status...
Potential causes:
- Communication error between Java and ABAP - e.g. http error encountered while Adapter is calling IE
- Communication error between the specific adapter and external system
- Content/validation error on the adapter - e.g. invalid data passed back from JDBC adapter - you can usually see this from Visual Admin.
Basically anything that will prevent the AE from passing the information in or out (e.g. in to the IS or out to the Target system).
sincerely,
--NM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
If you use EOIO, if any one of the predecessor message has got stuck then all the other following messages will be stucked. As in this case Queue names are given and it will use only that queue. This is the disadantage of EOIO
But if you use EO, then if one of the message has got queue problem, it may not be true for other messages. Because for next message it may pick some other queue.
The reason for messages being stucked are many
1) Huge Message size
2) Receiver is not active
3) Communication failure
etc
Hope this helps,
Rgds,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
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.