on 10-05-2010 4:07 AM
Hi Gurus,
We are getting an issue with our PI 7.1 Test system due to long running and
never ending loop of SAPLHTTP_RUNTIME program that is causing TIME_OUT
short dump (Please refer to below short dump).
And after the process was cancelled, in several minutes, there will be
another same process until ended with short dump, it looks like an
never ending loop.
Need your help in case you already had this kind of experiences. We've already rebooted the system but the issue still persists.
Thanks,
Yan
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 1800 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.
Hi,
Did you check SAP Note 1421784 ?
Thanks,
Sunil Singh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sunil,
Thanks. Just got a chance to check OSS 1421784. Below are the analysis results:
a) rdisp/start_icman --> our value is already TRUE
b) I can't find the similar symptoms and rdisp/softsignal_delay is set the same as another PI system that has no issue.
And further check on OSS 1426469, our kernel version is higher, we are using SAP Kernel 7.10 SP188.
Appreciate for any other input.
Regards,
Yan
Hi Yan
What Operating System do you use? Is it HP-UX?
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Can you provide more information on the dump? Go to the "Error analysis" section and the "Information on where terminated" section and copy the text into the thread (if possible for you).
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Please find out the detail below:
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 1800 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.
Information on where terminated
Termination occurred in the ABAP program "SAPLHTTP_RUNTIME" - in
"HTTP_READ_SC".
The main program was "SAPMSSY8 ".
In the source code you have the termination point in line 23
of the (Include) program "LHTTP_RUNTIMEU07".
The program "SAPLHTTP_RUNTIME" was started as a background job.
Job Name....... " "
Job Initiator.. " "
Job Number..... " "
Thanks,
Yan
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.