on 10-31-2007 3:29 PM
Hi,
From time to time, we get blocked queue with status RUNNING ...
When we introspect the queue, we see a bunch of transactions that has the status : Recorded but the very first one has the status : <b>"Transaction Executing ..."</b> and if we do not manually unblock the queue, it stay in that mode for ever ...
Any one has seen this situation ...
Merci A+ M.Osborne
Hi,
The reason may be your J2EE engine is not responding or down. Please check the connectivity between ABAP stack and Java stack.
Step 1: goto txn : SM59
Step 2: Check the RFC destination :AI_RUNTIME_JCOSERVER and try to do a connection test.
Step 3: Check the RFC destination :AI_DIRECTORY_JCOSERVER and try to do a connection test.
If your above tests are not successful, please ask your Basis team to fix this.
Regards,
Ananth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ananth,
At the first place we suspect the following 4 RFC
- AI_RUNTIME_JCOSERVER
- AI_DIRECTORY_JCOSERVER
- LCRSAPRFC
- SAPSLDAPI
And the are all working perfectly ;-(
(ref.:http://help.sap.com/saphelp_nw04s/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm)
We are in HA mode with the SAP Web Dispatcher. Do you think, since the AFW talk to the IS via HTTP (thus going via the SAP Web Dispatcher) that could cause the problematic? (We have check the SAP Web Dispatcher + ICM logs and we see nothing ...)
It has happens with a JMS to IDOC scenario. We have suspect that the R/3 backen system was up to its limit (WP wise), but the its running also idle.
Then it has happened with a very simple (with 4000 messages) JMS to JMS scenario.
Help help
Thank in advance !
m.Osborne A+
Try looking at this:
Program RSQIWKEX
- /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep
SM50 shown that there were enough WP available. Same in SMQR (qRFC resources). We had a look at SM66 as well. Even RZ12 is ok (we have 2 WP free all the time among 10, so 8 is use for qRFC)
SM58 shown that they were no tRFC limbo state (or waiting...). In fact, we get that jam (block) queue with a very simple MQ2MQ scenario ...
SM12 shown no particular deadlock
SM13 shown no updates ...
We are clueless ...
I suspect a timeout or something between the AFW via ICM (HTTP) and the Integration Engine ...
...... A+
User | Count |
---|---|
84 | |
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.