on 07-29-2009 7:38 PM
Dear Experts,
this is my Scenario...
Legacy System SAP ECC
============ =======
Web Service synchronous -
> Proxy synchronous.
sometimes I have this error (NOT Always): in SAP PI:
"Error during proxy processing Message E MC 601 cannot be processed in plugin mode HTTP"...
MC 601 = mc(601) -> "Object requested is currently locked by user &"..........
the same error in the Runtimer Workbench:
Error Category : ABAP
Error Code : DYNAMIC_CALL_FAILURE
Message Type : S
User : PIAFUSER
this error occurs sometimes... not always..
when I get this error, resend the message and it WORKS fine...
I can't recreate the error, I don't know the cause of this.. and less how to repair.
Thanks in advance.
Regards.
Hi Guillermo,
I would suggest you to put "wait" in ABAP coding after every posting via BAPI in code.
This would help the abap code coming after bapi execution to see the data in the tables .
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Santosh,
I'm using one WAIT UP TO 3 SECONDS after the bapi_transaction_commit MF.. but, the entry process take 7 seconds per line in my message... so if I put more WAITs, my interface will fall down by Time Out Exception.
put many external break points... and could see than, the error was by this cause:
I was blocking one order:
CALL FUNCTION 'ENQUEUE_ESORDER'
EXPORTING
aufnr = w_aufnr.
I have commented this code lines... and the interface is working fine...
Q: Why commit work doesn't works fine??? when we call a BAPI???
A: i don't understand... 😛 it's no logic.
well... thx..
Regards.
>>Object requested is currently locked by user &
This error is due to resource allocation.whenever the error happens,please check the user which is locking the object and also try to see which object is locked.
Please check ST22 and see if you get any dump for it as well.
Thanks
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have checked the ST22, and there is nothing....
executed the web service with the SOAPUI... and this is the error...
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>RecoverableException</code>
<text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:DYNAMIC_CALL_FAILURE:
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:456)
at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
</s:SystemError>
may br it could help..
thanks.
Hi Guillermo,
Performance running needs to be done at both end ABAP proxy code level as well at Interface level .
Issue is very much clear : Background ABAP Proxy Code Execution is faster than the SAP data base updation .
So locking situation coming up intermittently .
Regards,
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 | |
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.