HTTPS-500 Internal Server Error or SYSTEM_CORE_DUMPED while testing WS

[Former Member]

Hi Gurus,

We are having ECC 6.0 without Enhancement Packs. I have created web service for BAPI using wizard. While testing the Web service using WS navigator I am getting the above error. (if required, I can paste the Log from ST22)

I tried suggestions in -

Problem with a ABAP Web Service Call

SYSTEM_CORE_DUMPED Process terminated by signal 7

[Former Member]

The problem got solved. The following steps were followed by our Basis to resolve. -

a) deleted core file

b) stopped the saposcol

c) stopped the database listener

d) stopped the SAP

e) then started the saposcol

f) started listener

g) started the SAP

The problem seems to me as some 'buffer overrun' ...(don't know what THAT means!)

Thanks all for supporting me!

[Former Member]

Hi Markus,

Here is the error analysis-

An R/3 System process was terminated by an operating system signal.
 Possible reasons for this are:
 1. Internal system error.
 2. Process was terminated externally (by the system administrator).
    -

 Last error logged in SAP kernel

 Component............ "Taskhandler"
 Place................ "SAP-Server sapretail_RET_01 on host sapretail (wp 0)"
 Version.............. 1
 Error code........... 11
 Error text........... "ThSigHandler: signal"
 Description.......... " "
 System call.......... " "
 Module............... "thxxhead.c"
 Line................. 10841

 The error reported by the operating system is:
 Error number..... " "
 Error text....... " "

We have deleted the 'core' file and tested it, as suggested in possible solution part-

How to correct the error
    The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.

    Save this file under another name.

Still error is coming up.

[Former Member]

"SAP-Server sapretail_RET_01 on host sapretail (wp 0)"

Please post the dev_w0 from /usr/sap/SID/INSTANCE0/work, sort by time and paste the log here.

Thanks

SM

[markus_doehr2]

Please check the "analysis" section in ST22, post the stack trace of the workprocess.

You may update your kernel (dw_*) to the latest patchlevel and try again.

Markus