on 04-25-2013 4:08 AM
well, please make sure to use the latest saphttp patch.
If the problem still persists, open a message at SAP OSS.
Memory leaks could not be handeled here.
Meanwhile restart the application server on a regular basis (every 2-3 days, depending on the memory consumption) as a workaround.
regards
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
Thanks for your reply. Ok, SAP replied like this.
"You may kill the saphttp.exe process manually as a workaround to releasethe memory for now.
Could you upgrade your SAPHTTP program (both on frontend and server)
to the latest version? Refer to the attached note 164203.
In addtion, I can see lots of Z transactions running in your system
according to the screenshot. Please check with your system admin and
find out how saphttp is used in your programs."
A quick question:
Could I limit the maximum memory for saphttp? something like abap/heap_area_dia and abap/heap_area_nondia.
Hi Dennis,
no there is no method to limit memory consumption of saphttp (at least I know none).
On the operating system side there is one possibility to limit memory consumption but this one is unfortunately only working on process groups (so called job objects). But for this interface there is not tool (cmd-line or GUI-based). So there is no way to use it.
saphttp is used for the communication of an ABAP Server with an HTTP Server using the http protocol.
I would never expect saphttp to have any report specific memory structures left over after the corresponding RFC-call finishes or fails. So Z transactions should be no problem.
On Microsoft Windows we meanwhile have tools to find out the source memory leaks.
Open a message again and ask for analysis of the memory leak.
regards
Peter
Hi Dennis,
High memory consumption and High CPU Utilization issues has been fixed from SAP now. New patches are available in the SAP SMP for all the kernel releases except 721.
New patch for kernel release 721 will be released soon.
Best Regards,
Manu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andreas,
For kernel release 720 and 721, the new patches are available. This has been released last year only.
You can check the version of SAPHTTP by executing command " SAPHTTP -V " in the directory where it is installed. You can look for SAPHTTP version there. It should be similar to:
@(#) $Id: //bas/720_REL/src/krn/ftp/http.c#21
This is for 720 Release. http.c 21 is the latest version which solves memory leak issue of SAPHTTP.
I hope this helps you.
Best Regards,
Manu .
Hi Manu,
the problem still persists.
this is a summary of the current state:
- we are using kernel 721 EXT x64 UC on Windows x64
- currently, there is no separate download of saphttp.exe available on SMP
- we have deployed the binary which is part of SAPEXE_201-10011367.SAR
- it actually was deployed already but I made 100 % sure that we are using the lastest patch
- yesterday and today we had CPU problems on 2 different servers, running Windows 2008 R2 x64. One was a VM, the other one physical hardware
- last week we also had memory problems.
Saphttp -V:
@(#) $Id: //bas/721_REL/src/krn/ftp/http.c#2 $ SAP
SAP release: 721 SAP release no: 7210
Binary Details in Windows Explorer:
File Version: 7210.201.22.18122
Product Version: 721, patch 201, changelist 1459914
Regards
Andreas
Dear Lee,
Please also read following link and sap note in which explain the problems which you can face against saphttp.
Note 164203 - Problems with SAPHTTP
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Dennis,
You are getting issue due to memory which is not properly set, Please go through the below SAP Note. 1120481
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.