Avoid timeout dump

Hi friends!!
I have a problem in my program. Sometimes, depending of server I have a timeout dump in a Loop process. Its possible avoid this using try/catch and show to user message instead?
Thanks for any help.
Edited by: Fulvio Valente on Aug 23, 2011 7:53 PM

Hi
try/catch for what?
If you don't have any updating of tables of database you can call a COMMIT WORK, this comand will reset the time
But you should understand why your loop takes so long
Max

Similar Messages

How to avoid short dump in ECC 5.0

Hi
Can anyone tell me how to avoid short dump in ECC 5.0
I'm told we can avoid program going to short dump, instead IT WILL GRACEFULLY EXIT..

Hi
By implementing the code as for every unsuccess/failure conditions control has come out of the program. then only u can avoid dumps even though u code the not perfect functionality.
Regards,
kumar

Avoid timeout error in IC through coding

Hi Experts,
I have a requirement to avoid timeout error in interaction centre ,not through RZ* parameters.
but by coding in ICCMP_HEADER, headerviewset.htm.
Has anyone faced this before, can you pls share your ideas.
Highly rewarded.
Regards,
Lakshmi

Hi Lakshmi,
I assume you are referring to the session timeout that is tied to your basis setting. A hidden frame that does a periodic keep alive postback will keep the session alive. If you also have CTI integration, you need to also be sure your CMS is able to keep the communication session alive too.
Sincerely,
Glenn
Glenn Abel
Covington Creative
www.covingtoncreative.com

Avoid timeout error in IC

Hi Experts,
I have a requirement to avoid timeout error in interaction centre ,not through RZ* parameters.
but by coding in ICCMP_HEADER, headerviewset.htm.
Has anyone faced this before, can you pls share your ideas.
Highly rewarded.
Regards,
Lakshmi

Hi,
Look at the BSP Page headerviewset.htm. Find the following variable:
"var timeoutValue = <%= cl_crm_ic_services=>get_auto_logout( ) %>"
and
function setTimeoutTimer() that uses the variable
You need to manipulate this variable. Hope this helps.
Regards
Prasenjit

How to avoid ABAP dump

Hi,
How to avoid ABAP dump
With Warm Regards
Khaja

Hi,
One of the most common short dumps is while entering the values in selection-screen.
So Before processing the selection-screen, the values entered by user need to be
examined and make sure program handle any kind of input through test cases.
And also Its good practice to catch exceptions raised in between the process of the
program.
Regards and Best wishes.

Avoiding Timeouts with Java Beans.

I've the following problem : I've a bean which write some informations to an Excel file.
Sometimes data should be dumped are a lot and it takes more than the FORMS_TIMEOUT time, then the session ends with many problems (it crashes).
Is there any way to avoid this ?
Can I use the Timeout PJC to solve that problem ?
Tks
Tullio

how about writing this in a thread?
If you want to wait for finishing the execution, you can do the following:
write the whole stuff which creates the excel file in a thread, and start this thread in a method. call this method from forms. in another method you join the thread for e.g. 100 msecs, and return if the thread is alive...
public class MyClass
MyThread thread = new MyThread();
private class MyThread extends Thread
    public void run()
      for(int i = 0; i < 10; i++)
         Thread.sleep(1000);
public void startThread()
    thread.start();
public boolean waitForFinish()
    thread.join(10); //wait 10msecs for the thread to finish
    return(thread.isAlive()); //return the thread status
}and finally in your form:
fbean.invoke('item', 1, 'startThread');
while fbean.invoke_bool('item', 1, 'waitForFinish') loop //wait as long as the thread is not finished without buisywait
null;
end loop;regards

How to avoid timeouts from Enterprise Manager/BPEL console?

Occasionally I want to deploy (from JDev) some BPEL processes to the AppServer.
Surprisingly I got some errors. I found out when I re-login into
Enterprise Manager and tried again to deploy it everything works fine.
So it seems to me all errors occur because of a forced logout from Enterprise Manager.
How can I avoid such situations?
Peter

Hi peter,
See this forum link:
Re: How to avoid auto-logout (=timeout) BPEL console?
It contains your post only. See it.
Cheers,
Abhi...

SAP Smartform Timeout Dump in Production for the invoice form

Hi Friends,
I am working on Invoice Smartform. It is working fine when it is having avg line items. where as in my case one invoice iss having more than 500 line items in production. For this in production it is giving timeout short dump.
In that invoice i am displaying standard fuctionality of invoice form and at the same tim i am displaying Serial Numbers based on delivery and Open Quantity based on Order. So it will take time for back processing.
Insted of Back ground processing is there any other possibility to solve this. If not Please give me some steps how to implement this form in background based on conditions (if it is having more than 200 line items then only i need to run in background else foreground)
Pls give me your valuble inputs.
Thanks,
Srinivas.

Hi Vipin,
Pls provide more details like SP level , Kernel level etc.
I can see two probable reasons:
Incorrect installtion of GUI , pls try reinstalling the GUI and then try
Kernel upgrade but this solely depends on the current level and defer for further investigation.
Best Regards
Umesh

Timeout dumps

Hi All,
In our PI Production system we are getting lot of time out dumps in ST22 as below.
The program u201CCL_XMS_PERSIST_ADM============CPu201D has exceeded the maximum permitted uninterrupted runtime and has therefore been terminated.
I have checked all of Dialog work process is Running and ON HOLD state is it any cause for these dumps.. as well as rdisp/max_wprun_time chaged to 900.
Short text
    Time limit exceeded.
What happened?
    The program "CL_XMS_PERSIST_ADM============CP" has exceeded the maximum
     permitted uninterrrupted
    runtime and has therefore been terminated.
What can you do?
    Take note of the actions and inputs that lead to the error.
    Contact your SAP administrator for further processing of the problem.
    Using transaction ST22 for ABAP short dump analysis you can see and
    administrate termination messages and retain them for a longer period.
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.
Kindly advice on this..
Regards,
KUMAR

i am able to view the messages in SXMB_MONI but when i click on message to open it will taking long time then it creates dump..
pls find logs below
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_XMS_PERSIST================CP" bzw.
     "CL_XMS_PERSIST================CM02M"
        "READ_CHILDS"
    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,
======================================================================================
Tue Jan 4 17:26:46 2011
rdisp/max_wprun_time: 900 -> 1200
Tue Jan 4 17:59:30 2011
rdisp/max_wprun_time: 1200 -> 1800
Tue Jan 4 18:31:50 2011
     OCIStmtExecute() failed with -1=OCI_ERROR
     SQL error 1013:
SQL cancelled; calling registered function at 4efd80
program canceled
    reason   = max run time exceeded
    user     = PISUPER
    client   = 500
    terminal = dv2700-PC
    report   = CL_XMS_PERSIST================CP
TH VERBOSE LEVEL FULL
RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ROLLBACK entered.
RABAX: level LEV_RX_ROLLBACK completed.
ABAP Program CL_XMS_PERSIST================CP        .
Source CL_XMS_PERSIST================CM02M      Line 53.
Error Code TIME_OUT.
Module $Id: //bas/710_REL/src/krn/th/thhiserv.c#12 $ SAP.
Function ThTimeout Line 1736.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end no http/smtp
RABAX: end RX_GOTO_RABAX
Time limit exceeded..
regards,
kumar

Avoid timeout in Thread.run

I have a Thread running task by task from a taskpool.
while(running) {
task = tasks.elementAt(0);
process(task);
Sometime, processing might take too long (timeout)
so I need to force the thread to skip to the next task.
1) How can I accomplish this without having access to
process (my thread is abstract) ?
2) Do application servers provide such a feature
(timeout controll) at task level ?

why not just time it using System.currentTimeMillis
and then if it was too long (how long is too long ??)
then remove the next task from your tasks vector ??Timing is no problem as I have a monitor doing this.
The problem is that this is an abstract class, and I have
no contorl over process() method. This could event
run forever. As I said, stopping is controled by a monitor
object but the problem is that my thread is running in
process and I can't make it out (like throwing an exception).

JCo client calls as background processes (avoiding timeouts)

Hi Guys!
Could you please assist us to resolve a simple issue:
Our JCo Client call takes sometimes longer than the given timout for sap dialog processes (so, it's now clear, the jco client simply uses the dialog processes and not something smarter/more flexible).
My question is, ho to entice the jco client call to run without runtime timeout and take as long time as necessary. If the only possibility is, to use the tRFC, does anybody have an example for tRFC usage from JCo Client?
Is also a JCo server component needed to implement some callback functionality from SAP system by using the tRFC, or it could be enough to poll the server and implement the timeout on the client level (it could be for us the best solution if we realy must use the tRFC).
Once again, we want to run the JCo client calls unlimited time (as long as needed) without the annoying dialog process timeout. The tRFC is not necessary by use cases now.
Any help would be appreciated!
Many thanks, Gena

Hi Gena,
so, it's now clear, the jco client simply uses the dialog processes and not something smarter/more flexible
Well, that's a feature of the underlying RFC protocol: All RFC calls are executed in dialog work processes, thus also the runtime limitations for dialog processes apply.
My question is, ho to entice the jco client call to run without runtime timeout and take as long time as necessary. If the only possibility is, to use the tRFC, does anybody have an example for tRFC usage from JCo Client?
The JCo client cannot do anything about it, it's a profile parameter in SAP, i.e. rdisp/max_wprun_time. But as this parameter applies to all dialog processes (so dialog users and RFC calls), so it shouldn't be changed to make a single RFC application work. Anyhow, tRFC won't help you in this case, because all RFC calls are processed in a dialog process no matter of the type of RFC.
Once again, we want to run the JCo client calls unlimited time (as long as needed) without the annoying dialog process timeout.
Impossible without making any changes in SAP. In theory one could modify the RFC function so that it resets the "runtime counter" and thus having the capability to run longer than rdisp/max_wprun_time. I'd recommend though not to do that, especially since a very long running RFC seems rather questionable. Long running tasks should be processed in background.
Cheers, harald

How to run a block from client avoiding timeout

Hi,
I have a block to run on my pc which will then communicate with the server and then complete the process and get the results. Now if my network connection dies in mean time, then the job gets terminated halfway. PLEASE let me know if anyone know how to run a job directly on the server or somekind of workaround to run it unexhaustively. just like we have NOHUP facility for UNIX scripts, do we have something for oracle.
Would be eager to get some solution.
Thanks and Regards.

You don't need the DBA role, no. You would need EXECUTE access on the DBMS_JOB or DBMS_SCHEDULER package, which you may well already have. Note that the DBMS_SCHEDULER package is only available in 10g-- you didn't specify what version of Oracle you're using, so I'm not sure if that's an option for you.
The simplest possible solution would be something like
DECLARE
l_jobno NUMBER;
BEGIN
dbms_job.submit( l_jobno, <<SQL script>>, sysdate + interval '1' minute );
commit;
END;which would run the <<SQL script>> in a background session starting in 1 minute.
Justin

Select query - timeout error

hi experts,
I have written a pgm where i need to select records from BSAD table. This table has about 10 key fields. But according to my requirement, i can pass only 2 key fields to the table and have to fetch records from this table. But it goes to dump (timout error) in BSAD select query.
So i have used PACKAGE SIZE 20 and tried to fetch only 20 records at a time from the table. But still, it takes lot of time in fetching records from BSAD table.
Pls tell me what is the solution to avoid timeout error and how to fetch the records quickly.
Regards,
Shanthi

I hope that your " two fields" are BUKRS and KUNNR.
Consider this: If I can't supply a value for the first field (after mandt), then the second, etc., the select is going to run FOREVER. I think that, if you used ST05 and explained the BSAD open, you would see the problem. I'm guessing that you're not supplying a value for BUKRS, etc., and thereby causing a full table scan. Or you may have supplied NOT operators in the where clause or included an order by statement. Current ABAP CHECK tools (like SLIN or SCID) should point out problems in the where statement also...
May I suggest utilizing SE11 and looking at BS* tables to see if there is an alternative data source where you can supply an EQ value for the first few fields (at least) of the index? Or, post psuedocode so that the forum users can help you out.

Short dump-internal table size issue

Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CM

Hello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW      = 1.
W_UP       = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
    R_PKUNWE-SIGN = 'I'.
    R_PKUNWE-OPTION = 'EQ'.
    R_WERKS-SIGN = 'I'.
    R_WERKS-OPTION = 'EQ'.
    LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
      MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
      MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
      APPEND R_PKUNWE.
      APPEND R_WERKS.
    ENDLOOP.
*fetch sold to party
     SELECT KUNNR NAME1
       FROM KNA1
       APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
       WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
         FROM T001W
         APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
         WHERE WERKS IN R_WERKS.
   REFRESH: R_PKUNWE,
            R_WERKS.
    W_LOW = W_LOW + 1000.
    W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh

Getting dump while assigning resource to role

Hi,
We are using BAPI_BUS2177_STAFFING_ADD to assign resource to role.
It is assigning first resource to first role in first project. And giving dump for next resource to role assignment for the same project.
Short dump description is like as follows:
The exception 'CX_DPR_FATAL_ERROR' was raised, but it was not caught anywhere
along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_DPR_AUTHORIZATION_SERVICES=CP' has to be
terminated.
The problem is of "COMMIT". I ma not understanding where to write exact commit. Even if we are commiting at project level it is giving dump.
Could you please give any suggestion on it.
Thanks & Regards,
Anil Salekar

Hello Kaixiang,
When you add staffing to project then commit after each resource assignment. That will avoid the dump.
Use:
CALL FUNCTION 'BAPI_CPROJECTS_COMMIT_WORK'
TABLES
return = it_return.
Note: Re award if useful
Thanks,
Appasaheb..

Avoid timeout dump

Similar Messages

Maybe you are looking for