cancel
Showing results for 
Search instead for 
Did you mean: 

QRFC_SYSTEM_DUMP- Timeout limit exceeded

former_member235717
Participant
0 Kudos

Hi All,

I have a Proxy to File scenario which runs daily once in background in ECC.

Now a days I'm facing a timeout issue and the message is getting failed.

In ECC , messages is getting successfully delivered, but after coming into PI the message getting failed with short dump in abap stack.

Following is the error in PI

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">QRFC_SYSTEM_DUMP</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>A short dump occurred while executing a message in qRFC queue XBTL: Date/Time , User, Runtime Error: Time limit exceeded.</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

Please help me how to correct the issue

Thank you!!

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member184720
Active Contributor
0 Kudos

Hi Swetha - Execute ST22 transaction in PI system. It'll give you more details on the dump and what has to be done.

Please share the screenshot of ST22.

Also what is the message size?

former_member235717
Participant
0 Kudos

Here is the screen shot of ST22

  following measures:

  - Endless loop: Correct program;

  - Dataset resulting from database access is too large:

    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table

    (for example);

  - Database has unsuitable index: Check index generation.

  You may able to find an interim solution to the problem

  in the SAP note system. If you have access to the note system yourself,

  please use the following search criteria:

      "TIME_OUT" " "

      "CL_RD_VALUE_EXTRACTOR=========CP" bzw.

   "CL_RD_VALUE_EXTRACTOR=========CM008"

      "GET_VALUES_XPATH"

  If you cannot solve the problem yourself, please send the

  following documents to SAP:

  1. A hard copy print describing the problem (short dump).

     To obtain this, select "System->List->Save->Local File (unconverted)"

     on the current screen.

  2. A suitable hardcopy printout of the system log.

     To obtain this, call the system log with Transaction SM21

     and set the time interval to 10 minutes before and 5 minutes after

     the short dump. In the display choose "System->List->Save->

     Local File (unconverted)"

  3. If the programs are your own programs or modified SAP programs,

     supply the source code.

     To do this, choose "More Utilities->Upload/Download->Download" in the

The size of the message is 41MB

former_member235717
Participant
0 Kudos

ST22 dump analysis:

Error analysis

    The system profile contains the maximum runtime of a program.

    When this time limit has been exceeded, the program is terminated

    to make way for other users who may be waiting.

    In the case of a work area, this means that

    - endless loops (DO, WHILE, ...),

    - database accesses producing an excessively large result set,

    - database accesses without a suitable index (full table scan)

    do not block the processing for too long.

    The maximum runtime of a program is limited by the system profile

    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. After

     this limit has

    been exceeded an attempt is made to interrupt the SQL statement running

    or to tell the ABAP processor to interrupt the current program. A

    maximum of 60 seconds is then waited. If after this time the program is

    still active then the work process is restarted.

How to correct the error

    Long running programs should generally be run as batch jobs.

    If that is not possible, the system profile parameter "rdisp/max_wprun_time"

     can be

    enlarged.

    Depending on the cause of the error, you may have to take one of the

    following measures:

    - Endless loop: Correct program;

  - Dataset resulting from database access is too large:

    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table

    (for example);

  - Database has unsuitable index: Check index generation.

  You may able to find an interim solution to the problem

  in the SAP note system. If you have access to the note system yourself,

  please use the following search criteria:

      "TIME_OUT" " "

      "CL_RD_VALUE_EXTRACTOR=========CP" bzw.

   "CL_RD_VALUE_EXTRACTOR=========CM008"

      "GET_VALUES_XPATH"

  If you cannot solve the problem yourself, please send the

  following documents to SAP:

  1. A hard copy print describing the problem (short dump).

     To obtain this, select "System->List->Save->Local File (unconverted)"

     on the current screen.

  2. A suitable hardcopy printout of the system log.

     To obtain this, call the system log with Transaction SM21

     and set the time interval to 10 minutes before and 5 minutes after

     the short dump. In the display choose "System->List->Save->

     Local File (unconverted)"

  3. If the programs are your own programs or modified SAP programs,

     supply the source code.

     To do this, choose "More Utilities->Upload/Download->Download" in the

     Editor.

former_member184720
Active Contributor
0 Kudos

Please check if the note is applicable to you.

1536717 - XI Runtime: Dump during analysis of XPATH expressions

former_member184720
Active Contributor
0 Kudos

Did you try increasing the timeout parameter?

former_member235717
Participant
0 Kudos

But if I reprocess the message manually, it is getting successful.

Does this really mean to increase the timeout?

former_member184720
Active Contributor
0 Kudos

It could be the possible reason. You can try increasing the paramter as i don't think 45-50mb is a normal size .

At the same time, try to analyze which pipeline step is taking more time to execute. Is it the mapping/receiver split?

You can find the details under PerformanceHeader in SXMB_MONI