on 12-20-2006 4:18 PM
Experts - I am processing around 300 messages at a time for ABAP Proxy to XI to JDBC(SQL stored procedure) scenario.
Initial around 10 messages got processed successfully but rest all 290 got stuck in Adapter engine. Out of 290 stuck messages , I see 4-5 with DELIVEZRING status and rest all are with TO BE DELIVERED status.
The message with DELIVERING status is not processing and not even Erroring out. Adapter is not even making connection to SQL when I monitor the activities in SQL. This message is just stuck in there and here is the MDT tool's Audit log about this message:
*********************************************************************************************
2006-12-19 13:27:53 Success The message was successfully received by the messaging system. Profile: XI URL: <URL details>
2006-12-19 13:27:53 Success Using connection AFW. Trying to put the message into the receive queue.
2006-12-19 13:27:53 Success Message successfully put into the queue.
2006-12-19 13:28:39 Success The message was successfully retrieved from the receive queue.
2006-12-19 13:28:39 Success The message status set to DLNG.
2006-12-19 13:28:39 Success Delivering to channel: RECEIVER_JDBC_MRI_OUTBOUND_PR1
2006-12-19 13:28:39 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2006-12-19 13:28:53 Success JDBC adapter receiver channel RECEIVER_JDBC_MRI_OUTBOUND_PR1: processing started; party , service MRI
*********************************************************************************************
Any clue ?? pls advice.
Cheers,
Amrish.
Hi Amrish,
I have exactly the same problem. Messages are getting stucked in Adapter Engine. Is this problem solved? How was it solved?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check in SMQ1 and SMQ2 to see if there is anything holding up the queue.
Also check this blog:
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thankfs Wojciech, but how do I resolve this ? Where I can check this setting ?
I do not see anything in Receiver JDBC adapter for this type of thing . I have put Conflict resolution = Redo
Number of retries of database transaction on SQL error = 0
Transaction Isolation level = Default
Databse Auto-Commit-Enabled=Checked
Disconnect from Database after processing each message=Checked (since, if Unchecked then it was causing deadlocks at SQL Db stored procedure while running)
Pls advice.
Cheers,
Amrish.
User | Count |
---|---|
86 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.