ABAP Proxy timeout issue

Hi,
I have a scenario in where I provide a web service. I get called by this web service and then call a abap proxy (synch). The abap side takes time to gather the data. after 600 secs, the connection gets a timeout.
It says, "500 Connection timed out"
"Detail: Connection to partner timed out after 600s"
In smicm I increased the HTTP value to 9000. So, how do I get this error?
Parameters are like below in PI:
icm/server_port_0 = PROT=HTTP,PORT=50000,TIMEOUT=90,PROCTIMEOUT=9000
icm/keep_alive_timeout (sec.) = 50
icm/conn_timeout (msec.) = 5000
xiadapter.inbound.timeout.default = 5400000

Hi,
Check if you are getting some short dumps in ABAP side due to this timeout in ST22.
Probably the issue is the work process time out in the ABAP side as you mentioned it takes more time to gather data. the profile parameter is rdisp/max_wprun_time and it has default value of 600 seconds. if thats the case then you can increas it.
regards,
francis

Similar Messages

ABAP Proxy Timeout

Hi!
I have this scenario:
SAPR3 (A.Proxy) -> XI ->SOAP
SAP R3 sends Sync Messages to XI, through ABAP proxy, which starts a BPM, this BPM calls a WebService that sometimes takes more than one minute to give a response.
When the process reaches "Close S/A Bridge", it raises a Timeout Exception.
I have already increased HTTP_TIMEOUT in SXMB_ADM and icm/keep_alive_timeout in SMICM, in XI with no effect.
Do i need to change other parameter? Maybe in SAP R3?

Hi Jose,
go through tuning guide of XI (Once i find the link i update this thread ). The HTTP timeout property can be used for SOAP as well as the underlying transport protocol is http for SOAP messages too. That might help.
Also, the second thing you could do is that by default the Web service client socket timeout is set to 60. Try changing this parameter in the Visual Administrator: Server -> Services -> Web Services Container on the Settings tab.
Regards
joel.

ABAP Proxy Authetication issue

Hi there,
we're currently integrating a rail order portal via ABAP Proxy technology. We've installed the corresponding interfaces witch package EA-HR602.
During test in SPROXY as well as testing from application the user is promted to enter login credentials for the PI system.
Has anybody any idea, how to configure this application? We did all the setup for proxy runtime, all test reports are running well.
Please help, this issue prevents our go-live. Help is highly aprreciated and will be rewarded.
Cheers,
Matthias

Hi Kral
Check the link given by Sarvesh
Check your configurations with the blog. Moreover did you tried giving PISUPER as the user for RFC destination and test it again.
IF change of user works then you need to revisit the roles of the user you have.
Thanks
Gaurav

ABAP proxy related issue

Hi All,
Good morning,
i working with ABAP proxy to file scenario. the requirement for this scenario is we are fetching data from data base to internal table then using that table we have to write code and send data to xi. can give me past response that how to write code using internal table. i want only code related internal table not total code.
thanks for fast response.
regards
sai

Hi Sai komala,
After genrating the Proxy, you can view the calss & structures genrated by proxy.You need to create an object with refrence of Class and to be create workareas for your Message type and Data type strucutres. Create an Internal table with your desired structure and do the validations as per your mapping rules.After completion of your all validations you need to populate your final internal table data to the structure of message type and call the execute asynchronous method.
Have a look into following weblogs
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
TO debug u r proxy code, just like your normal R3 report program. put a breakpoint and execute the program , you can view the debugging of your proxy.
Hope it will helps to solve u r probolem
Cheers
Veera

Outbound Client ABAP Proxy Timeout Error

Hello everybody we have the next scenario:
R/3 Client Synchronous ABAP Proxy->XI-> Synchronous RFC
and we are having problems cause the Sender R/3 is not waiting for the RFC in the Receiver system to process so XI is in log status fot this messages, is there a parameter to increase the time for R/3 Sender to wait for the Call method sentence to complete succesfully??????, thanks in advance.
Regards,
Raul Alvarado

Hi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna.

ABAP Proxy authorization issue when sending message.

Hi
We have an interface which uses ABAP proxies. This is used to send a message with attachment, but when i send the message I am getting a 401 error message which says unauthorized.
I checked all the configs on the sending side and i cant fine anythin wrong. I tried SLDCHECK and all looks fine there as well. I have done the configuration in the Integration engine on the sending side as mentioned in the BLOG - Activating ABAP Proxies.
We have 3 XI systems Dev, QA and Prod sharing the same SLD. The configs that we have on the sending system (App Sys.) is given below.
SM59
HTTP connection : SAPISU_XID
Host : XI Dev hostname Service Number 8080 (80 <sys number>)
Path Prefix : /sap/xi/engine?type=entry
USER : XIAPPLUSER
The TCP/IP connections LCRSAPRFC and SAPSLDAPI are also setup on the system which connects to our SLD.
The TCP/IP connections works fine and i am able to test it succesfully, but the HTTP connection fails with an authorization error (401) when i test it. Now the wierd thing is if I use XIAFUSER instead of appuser it works fine, but if i make a copy of XIAFUSER and try that... It fails again.. I know it sounds strange. So i was wondering if there is any setting on XI which restricts HTTP connections to a particular user??
I would really aprpeaciate if you could please give me your thought on this issue...
Cheers
Prav

Hi Manish
Thanks for the input again.
I checked SICF on the XI system and its not set to any user.
The HTTP connection on out prod environment is working fine without any issues and its uses a user which is a copy of XIAPPLUSER. SICF in prod also does not have any user configured for service SAP\XI\Engine.
Thanks for the link, had a look at it, but It looks like these users mentioned are only available with XI7. Our server was upgraded from 3 to 7 and I am not able to find these users on the system.
I tried testing the HTTP connection in prod using a diffrent user and found its the same story there. If i use any use other than the cutom one.. it fails.. could there be any setting in the exchage profile that can affect this??
Thanks for your time and help.
Prav

Abap Proxy = Web Service - Connection timeout

Hi Experts,
I request your help on some issue we encounter actually on our Web services interfaces.
We have sceanario in which from SAP, we are sending a message to PI via Abap proxy.
PI then, send the message to the external system via a Web Service (we have configured the URL and authentification values).
When we want to test the scenario we have an issue.
- We see in SXMB_MONI message has status sent succesfully
- When we check the external system, we see that no message is received (no trace of message from PI).
- Then we check on PI runtime workbench, we see in the receiver communication channel error saying "Connextion Timeout"
(in detail: SOAP: call failed: java.net.ConnectException: Connection timed out")
We would like to investigate the issue.
Have you already encountered this kind of issues ? And how we could investigate the root cause here ?
And thanks for ur help,
S.N

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

How to check for Web Srvice Timeout in ABAP Proxy call

I am calling a web service in my ABAP program using ABAP proxy. The code is as under:
TRY.
      y_v_request-mt_request-yaskkey   = y_l_matnr.
      y_v_request-mt_request-maktx      = y_l_maktx.
      y_v_request-mt_request-ymtart     = y_l_mtart.
      CALL METHOD y_v_prxy->execute_synchronous
        EXPORTING
          output = y_v_request
        IMPORTING
          input = y_v_response.
    CATCH cx_ai_system_fault INTO y_v_fault.
      y_v_message = y_v_fault->errortext.
ENDTRY.
y_l_ycod = y_v_response-mt_response-answer.
1. Is there is any way to know that the called web service has timed out ?
2. Is it possible to check for the time spent in the call if it is more then say 500 sec then it should be considered as timeout?
Any help will be appreciated.
Thanks in advance

Hi Subbu,
you can catch CX_AI_SYSTEM_FAULT.
DATA:   lo_sys_exception TYPE REF TO cx_ai_system_fault,
l_error_text type string.
CALL METHOD ...
CATCH cx_ai_system_fault INTO lo_sys_exception.
l_error_text = lo_sys_exception->errortext.
You can configure XI timeout parameter (for shure in SMICM / Parameter and, if i remeber right, as profile parameter in XI administration).
Regards,
Udo
Message was edited by: Udo Martens

Bapi call in abap proxy reaching dialog timeout in async scenario

Hi all,
We have an XI interface to create sales orders. Legacy app sends a soap message async to XI with a group of orders. XI sends this group of orders to an Abap proxy async on ECC side. Into this Abap proxy we have a loop to process each order received in the group with BAPI_SALESORDER_CREATEFROMDAT2. Ending the loop, abap proxy start another async process to send the response to XI with an outbound abap proxy, and the response is redirected by XI to Legacy app.
The problem is, this group of orders can have two or two thousand orders... so, the async process guarantee that no timeout limit will be reached. This is working for the whole process. But when this BAPI is creating an order, the time out of BAPIs execution seems to be the same as the timeout of dialog processes (now set to 10 minutes). This is our problem. Some orders spend more than 10 minutes to process (orders with five hundreds items, for example)... when this occurs, BAPI throws a time out reached error and the async process stops on the inbound queue with status sysfail.
We are now trying to understand why this timeout is been triggered by the BAPI. As it is running into an Async process, it should execute without any kind of timeout limits...
If anybody has any idea, please, help us.
Thank you.
regards.
roberti

May be I was not so clear... the total spent time in the process can be many many hours, days, etc... no timeout is reached. I can post 10.000 orders, no timeout is reached. The problem is that if the processing of only one order with BAPI_SALESORDER_CREATEFROMDAT2 takes longer than 10 minutes, then the timeout is reached. This is the strange part. The processing of the bapi seems to get the same timeout of dialog processes, we already tested increasing the dialog process timeout and the timeout of bapi execution was the same...
We already monitor on SE66 to see if it opens a dialog process to execute the bapi call function, but it does not.
If anyone has any tip, please, provide us.
Thanks!
roberti

Timeout in ABAP Proxy

Hi!
In my scenario messages on CRM are created by a BADI calling an ABAP proxy class on the local Integraton Engine which then forwards the messages to the XI Integration Server and vice versa.
We recently had the problem that the SAPSLDAPI SM59 destinations on XI and CRM ran into a timeout because the SAPSLDAPI service in the JCo RFC Provider Service of the J2EE Admin Tool was not working properly.
While we experienced the SAPSLDAPI timeout problem in the XI Integration Server all messages which XI was supposed to forward to CRM failed in the Call Adapter step in SXMB_MONI with error status 500 (timeout).
I would have assumed that the same happens also on the CRM side when the local Integration Engine was supposed to send messages to XI. However, there was a timeout when pressing the save button in the IC Web Client. The XML messages were not created at all and not visible in SXMB_MONI. Thus in production a call center agent would have not been able to update any customer or product information.
If such a problem arises in my opinion the messages should always be created and queued up by the Integration Engine so that they can be reprocessed once the problem is solved. Does anybody have any idea why this did not happen on the CRM side and do you have any feedback how this problem could be resolved?
Regards, Tanja

Hi!
> Please can you check in the SXMB_MONI of the CRM
> system if there are any messages stcuk there if you
> cannot see the same in the XI SXMB_MONI.
There was a timeout when pressing the save button in the IC Web Client. Thus the XML messages were not created at all and not visible in SXMB_MONI on CRM.
Regards, Tanja

Issue with inbound abap proxy

I have an Inbound ABAP proxy scenario , the ABAP code inserts data into a ZTable.
I am having an issue in the runtime where
1. I see transaction data in SXI_MONITOR of both XI & application system.
2. if tried to debug with the report SPRX_TEST_INBOUND (as the application system WebAS is 6.20) the proxy code works just fine, and records are inserted in the ZTable.
records are not getting inserted into the table when run end to end..anybody faced this situation ?
Appreciate genuine replies....

Hi,
but this just has to work
if this doesn't work then "something realy strange is going around here"
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Consume WSDL in ABAP proxy : Issue with name space

Hi,
I was trying to consume a WSDL in ABAP and I have created ABAP proxy using wizard in SE80 and also did the LPCONFIG.
While calling the proxy methods it is throughing the "authrization failed" error because of the following issue.I have successfully executed same WSDL from some third party tools with out error.only difference I have observed in SOAP request is, Third party tools passing all name spaces at envelope level but in ABAP proxy it is not passing all name spaces at envelope level.
1. SOAP genarated from WSDL in third party tool.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.xxxxx.com ">
<soap:Body>
 <tns:GetKMContent>
 <tns:request>
 <tns:clientID>1</tns:clientID>
 <tns:employeeID>307478</tns:employeeID>
 <tns:languageCountryCode>en-US</tns:languageCountryCode>
 <tns:wscVariables>
 <tns:empcountry>US</tns:empcountry>
 </tns:wscVariables>
 </tns:request>
 </tns:GetKMContent>
</soap:Body>
</soap:Envelope>
SOAP genarated from WSDL in ABAP proxy.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
<n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/">
<TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/">Full</TraceLevel>
</n0:Trace></soap-env:Header>
<soap-env:Body>
 <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com ">
 <nr1:request>
 <nr1:clientID>1</nr1:clientID>
 <nr1:employeeID>307478</nr1:employeeID>
 <nr1:languageCountryCode>en-US</nr1:languageCountryCode>
 <nr1:wscVariables>
 <nr1:empcountry>US</nr1:empcountry>
 </nr1:wscVariables>
 </nr1:request>
 </nr1:GetKMContent>
</soap-env:Body>
</soap-env:Envelope>
I was trying to use the SOAP genarated in ABAP proxy in thrid party tool and end up with same "authrization failed " error. If I move the name space nr1 from <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com "> GetKMContent node to soap-env:Envelope <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nr1="http://schemas.xxxxx.com "> then it is working fine.
Question :Is there any way in ABAP proxy to pass name space at soap-env:Envelope level or is there any way to change the SOAP request once it is genarated from ABAP Proxy?. Is there any API to change SOAP information?
Thanks,

Hi Kavitha,
I am also facing the same issue.
Could you please share the solution if you have solved this.
Thanks,
Arun

Issues with ABAP Proxy in XI 3.0

Hi,
We are on XI 3.0. We are doing a scenario of file >XI> R/3 (ABAP Proxy).
The XML message is going to R/3 with no errors as indicated in the monitors on both XI and R/3. The XML messages has the status of 'Message Processed'. But, the proxy never gets executed. Is there a step I must perform to execute the Proxy? My understanding is that if the Receiver Communication Channel is of XI type, it will automatically execute the Proxy on the R/3 (receiving) system.
We tested the proxy using the report SPRX_TEST_INBOUND, and it works as expected.
Please advise.
Thanks in advance.
Best Regards,
Doo

Hi Doo,
how do you know, that the proxy was not called?
If you are missing database updates, check if you have a commit work in the code.
Regards
Stefan

Timeout Error in Call Transaction on Asynchronous Abap Proxy

Hi Gurus!!
We have a problem with a Call Transaction on Asynchronous Abap Proxy. When the process of Call Transaction (transaction CO02) takes more than 10 minutes, the process is cancelled with sy-subrc 1001 and the Abap Proxy continues with the execution. Strangely, there is a short dump in ST22 on transaction CO02, although on the ABAP Proxy we don't get any dump.
When this process is called from a Background Job no dumps are get.
Somebody knows if there is a problem with the Asynchronous ABAP Proxy executing CALL TRANSACTION statementent?
Thanks and regards,
Manuel.

and the message after recording is
Number               1
Transaction          F-22
SY-SUBRC             0
Messages
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0330WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
S F5 312                   Document 100001677 was posted in company code 3100

ABAP Proxy timeout issue

Similar Messages

Maybe you are looking for