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

Similar Messages

  • 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

  • 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.

  • 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

  • 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 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

  • 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

  • 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.

  • Problem with Synchronous abap proxy time out

    Hi there.
    I have the following scenario:
                      sync                   sync
    3rd party <-->  PI    <--
    >  ERP
                       http                    abap proxy
    In the implementing class on the abap proxy i'm calling an standard BAPI, followed by a commit and returning the result.
    The 3rd party app has a mechanism that when a message fails, he'll retry each 5 mins until it gets the response.
    Last night there where some delays on ERP that cause the sync mesages to timeout, the 3rd party retried about 10 times to send the message until it finally went off. This morning i check and i have the same message 11 times on ERP!!, to my understanding if the sync comm timed out the process will abort and  the message will not be processed on ERP, does anybody knows if im missing some configuration for this to work this way??.
    Kind Regards,
    Roberto.

    Hi Roberto.
    There are a lot of time out configures in PI .
    Follow the link that explain about this:
    How to Investigate Timeouts In Synchronous XI PI Scenarios
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747
    I hope to help you.
    If you still keep this problem, you can ask me more about it.
    Regards..
    Bruno.

  • Error with ABAP proxy

    Hi all,
    I have an ABAP proxy - XI - Webservice scenario, in the XI side we are getting error saying input data not coming in. How to check weather proxy is triggering the actual payload or data?
    There has been a change in the WSDL from the Webservices side, they have changed the data type, so we too updated the mapping in XI. So do we need to change anything in the ABAP program which triggers the proxy,
    how do I check weather proxy is triggering data or not?
    I want to see weather its problem with the ABAP trigger program.
    Thanks,
    Srinivas

    Hi ramakrishna,
    Does R/3 side SXMB_MONI give successful chequered flag when the message is processed?
    Because for correctly processed message, the data is being updated in the table, but I can't see the chequered flag on the R/3 side.
    But for the wrongly processed ones its showing PL_TIMEOUT error and showing red flag on R/3 side, this is what I see on the R/3 side:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Integration Server
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Pipeline timeout condition satisfied</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • How to handle exceptions in sender ABAP Proxy

    Hi Experts,
       I have a synchronous scenario.
       SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
       In system 'A', a function module calls the ABAP Proxy method.
       My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
    For example:
    Exception in PI:
      <SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:P1/><SAP:P2/>
    <SAP:P3/><SAP:P4/>
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace=""/>
    <SAP:Stack/>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    In the calling function module:
    Try
    Call to proxy-> method
    Catch cx_ai_system_fault INTO v_o_fault.
           v_err_msg1 = v_o_fault->GET_TEXT( ).
           v_err_msg2 = v_o_fault->errortext.
           v_err_msg3 = v_o_fault->code.
    Endtry.
    Here I get value "MESSAGE.GENERAL" for  v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
    I want to capture the info available under <SAP:AdditionalText>. How to get that?
    Please help!
    Thanks & Regards
    Gopal

    >
    gopalkrishna baliga wrote:
    > Hi Experts,
    >
    >    I have a synchronous scenario.
    >
    >    SAP R/3 System A -ABAP Proxy <-> PI <-----> SOAP< ---> Webservice
    >
    >    In system 'A', a function module calls the ABAP Proxy method.
    >
    >    My requirement is that if there is an exception in PI ( for example: timeout or ABAP engine error) then I want to get the exception details in the calling function module.
    >
    >  For example:
    >
    > Exception in PI:
    >
    >   <SAP:Error xmlns:SAP="XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    > <SAP:Category>XIAdapterFramework</SAP:Category>
    > <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    > <SAP:P1/><SAP:P2/>
    > <SAP:P3/><SAP:P4/>
    > <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
    > <SAP:ApplicationFaultMessage namespace=""/>
    > <SAP:Stack/>
    > <SAP:Retry>M</SAP:Retry>
    > </SAP:Error>
    >
    > In the calling function module:
    > Try
    >  Call to proxy-> method
    >
    >  Catch cx_ai_system_fault INTO v_o_fault.
    >        v_err_msg1 = v_o_fault->GET_TEXT( ).
    >        v_err_msg2 = v_o_fault->errortext.
    >        v_err_msg3 = v_o_fault->code.
    > Endtry.
    >
    > Here I get value "MESSAGE.GENERAL" for  v_err_msg1 and v_err_msg3. v_err_msg2 is blank.
    >
    > I want to capture the info available under <SAP:AdditionalText>. How to get that?
    >
    > Please help!
    >
    > Thanks & Regards
    > Gopal
    Hi Gopal,
    Maybe the exception is CX_SY_APPLICATION_FAULT, or you can catch by BPM in PI and send back to proxy like a message response.

  • Data packets in abap proxy

    Hi
    I am sending a data from R/3 to XI using abap proxy. Here if the data packets are waiting in the queue for some time
    am getting an error " Time Limit Exceeded" and user is cancelling the job for processing in R/3
    pls advice me how do i find the queue name and solve this issue.
    Thanks
    Ganesh

    Hi,
    These HTTP calls can sometimes be disrupted by timeout errors:
    - ICM_HTTP_TIMEOUT
    - ICM_HTTP_CONNECTION_FAILED.
    How you can try to deal with those errors:
    1. you can try increasing the HTTP_TIMEOUT of the Integration Engine:
    a) go to TCODE - SXMB_ADM
    b) Integration Engine Configuration
    c) Change specific configuration
    d) Increase the HTTP_TIMEOUT parameter value - this value depends on your specific needs.
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8b-c935e444b0ad
    Regards,
    Nithiyanandam

  • ABAP Proxy does not send data to XI system.

    I have a very simple program to test an ABAP Proxy:
    REPORT  Z_TEST_PERSON_OB.
    DATA prxy TYPE REF TO Z996CO_PERSON_OB2.
    CREATE OBJECT prxy.
    DATA person TYPE Z996PERSON_MT  .
    *TRY.
    person-person_mt-first_name = 'Ken and Kenneth'.
    person-person_mt-Series = 'The Fast Show'.
    person-person_mt-motto = 'Ooh, suit you Sir!'.
    CALL METHOD prxy->execute_asynchronous
    EXPORTING
    output = person.
    commit work.
    I removed any exception handling to see if it would dump. Nothing. Seems to work fine, but no data appears in the XI Integration Engine monitor. I checked the scenario in XI and tested it; again, seems to work fine.
    Could I have missed something in setting up the system? Any pointers highly appreciated.
    BR,
    Tony.

    Try the Message Monitoring -> Messages from component 'Proxy Runtime <...>'.
    That's where I found my Messages back (Status: To Be Delivered...)
    If this is the case, probably your Proxy Runtime does send the messages to the Integration Engine.
    Check the queues:
    Transaction SXMB_ADM on the Business system (the system that sends the Proxy)
    Integration Engine > Administration > Manage Queues
    All queues should be checked
    Click ‘Register Queues’. Status bar should display a ‘Success message’.
    Click ‘Activate Queues’. Status bar should display a ‘Success message’.
    If it still does not work, maybe the is no connection between Integration Builder and Runtime Workbench.
    Check SM59 on your ECC-business system (the system that sends the Proxy). It should have the Connection INTEGRATION_DIRECTORY_HMI (type H). If not, this is the problem.
    Create a new connection INTEGRATION_DIRECTORY_HMI, type H.
    Tab Technical settings:
    Target Host is your XI-host
    Service No. 5xx00 (xx is the instance number of your XI-system)
    Path Prefix is "/dir/hmi_cache_refresh_service/ext" (without quotes)
    Tab Logon & Security
    Logon Procedure is "Basic Authentication"
    Logon using XIISUSER (or PIISUSER)
    Tab special Options
    Specify timeout: set to 900 msec.
    Compression Status should be 'inactive'
    Compressed response: No
    Accept Cookies: Yes (all)
    Save configuration and test connection. Popup about cookies appears. Check the "Accept All Further Cookies"option.
    The response should have HTTP/1.1 200 OK in the first line of the response header.
    Now your Proxy Runtime should be able to connect the Integration Engine.
    Greetings,  Frank

  • Timeout on Client Proxy

    Hi
    When running an ABAP client proxy in an ECC system I get the following error message:
    HTTP Response Contains status code 500 with the description of Timeout.
    I have increased the HTTP timeout parameters to according to the blog (Points 1 & 2):
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    but with no success. Can anyone please advise further ?.
    A point to note that this does not happen with all messages only larger ones.
    Thanks in advance ...

    hi,
    >>the timeouts were increased by basis team on the R/3 backend and there was a restart following this.
    I'd stay with my initial answer - it's http timeout parameter
    maybe it was not done in a proper way by your basis
    HTTP timeout is HTTP timeout - unless there is some more errors
    which you did not see
    BTW - about packages
    I've never heard about anything like abap proxy packages
    I don't think he meant any XI functionality
    Regards,
    Michal Krawczyk

  • Error while activating ABAP proxy object

    Hello,
    I can see all the interfaces of PI7.0 in my ECC6.0 system.
    I am able to create abap proxy object of a interface.
    But when I try to activate that I am getting error as
    "RFC system error for destination GTADIR_SERVER".
    Pl can you suggest. appreciate quick help in this.
    thanks in advance,
    Sharada

    Hi,
    For more details take a look at note:  [1063482 - Creating Dictionary objects - RFC error GTADIR_SERVER|https://service.sap.com/sap/support/notes/1063482]
    It is written that: Message SGSUB 104 is not an error message, but is merely irrelevant information for customers. You can continue to create objects nevertheless.
    To get rid of this annoying error you have to implement the corresponding  support package.
    Regards,
    Jakub

Maybe you are looking for