on 02-01-2008 12:37 PM
Hello,
Sap release : ECC6 SP12
Integrated ITS 7.00
We receive incoming requests to our SAP server from an EP6 portal. The "SAP Gui for HTML" sessions are then displayed in SM04/SITSPMON transactions.
From yesterday, we had the following erreor mesage, every time a user is lauching a new request :
ITS, New user session denied due to memory bottleneck.
ITS, User session could not be created
Transaction Canceled ITS_P 027 ( )
We found in SM04, that a user that was no more connected , was still displayed using 3Gb of memory ...
The user sessions has been killed in sm04, and the user session is no more displayed, but still the memory bottleneck stills avoid any ITS connection.
In transaction SITSPMON, the session is still here
9427
Session - Memory Used
-
Session | Memory Type | Peak | Memory | Total | Current |
-
9427 | Session Memory | 782.370.074 | 782.370.074 | 8.793.685 | 2.976.865 |
-
Sess. & Templ. 782.825.098 Bytes
Amount of em/global_area_MB used (1024 MB)
Sessions: 1 782.370.074 Bytes 782370.074 Bytes/Session
How can I release the memory, without having to shutdown the sap server ?
thank you !
Any useful help would be appreciated.
Regards.
Hi,
I don't have an idea what has happened here. Something seems to be
broken totally. I cannot imagine an IAC consuming 782.370.074 Bytes.
Are you able to reproduce this issue? I suggest to create an OSS
ticket.
best regards
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
After further analysis, I've found out that the user of that session has generated a short dump when the ITS bottleneck occured :
Runtime Errors SYSTEM_CORE_DUMPED
User and Transaction
Client.............. 200
User................ "J544362"
Language Key........ "S"
Transaction......... "IW40 "
Transactions ID..... " "
Program............. "SAPLOLEA"
Screen.............. "RIAUFK10 0100"
Screen Line......... 0
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "xxxxxxxxxxxxxxxxxx"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/gui/sap/its/webgui/~flNUQVRFPTIwNDQwLjAy
wOA=="
Information on where terminated
Termination occurred in the ABAP program "SAPLOLEA" - in
"AC_FLUSH_CALL_INTERNAL".
The main program was "RIAUFK10 ".
In the source code you have the termination point in line 224
of the (Include) program "LOLEAU10".
********************************************************************
Before that, the same day , many other dumps have been generated, they're all the related to the ITS :
******************************************************************
Runtime Errors MESSAGE_TYPE_X
Error analysis
Short text of error message:
The dataset (222.056.640 bytes) is too big (abap/alvgrid/size_nodod_mb)
Long text of error message:
Diagnosis
The system tried to send a data record to the frontend, which
contains 222.056.640 bytes. However, the data volume has been
restricted to 52.428.800 bytes.
System Response
The current application program has been terminated with a runtime
error.
Procedure
Restrict the data selection if possible or contact your system
administrator.
Procedure for System Administration
The maximum size of these data volumes can be set using the kernel
parameter 'abap/alvgrid/size_nodod_mb' (in mega bytes).
Technical information about the message:
Message class....... "AWRT"
Number.............. 000
Variable 1.......... "222.056.640"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
User and Transaction
Client.............. 200
User................ "J544362"
Language Key........ "S"
Transaction......... "IW39 "
Transactions ID..... " "
Program............. "SAPLAWRT"
Screen.............. "SAPLSLVC_FULLSCREEN 0500"
Screen Line......... 3
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "xxxxxxxxxxx"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/gui/sap/its/webgui/~flNUQVRFPTExMTYuMDIxLjA3LjA
3===="
Information on where terminated
Termination occurred in the ABAP program "SAPLAWRT" - in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "RIAUFK20 ".
In the source code you have the termination point in line 25
of the (Include) program "LAWRTU22".
Line SourceCde
1 FUNCTION its_check_alv_data_size.
2 *"----
3 ""Lokale Schnittstelle:
4 *" TABLES
5 *" DATA_TABLE TYPE TABLE
6 *"----
7
8 * DATA n TYPE i.
9 DATA currsize TYPE i.
10 STATICS maxsize TYPE i.
11 DATA par_value(56).
12 IF maxsize IS INITIAL.
13 sy-subrc = 0.
14 CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alv
15 ID 'VALUE' FIELD par_valu
16 IF sy-subrc NE 0.
17 maxsize = 52428800. " Default 50 MB
18 ELSE.
19 maxsize = 1048576 * par_value.
20 ENDIF.
21 ENDIF.
22 DESCRIBE TABLE data_table. " LINES n.
23 currsize = sy-tfill * sy-tleng.
24 IF currsize GT maxsize.
>>>>> MESSAGE x000 WITH currsize maxsize.
26 ENDIF.
27
28 ENDFUNCTION.
Thank you for your help.
Regards.
Edited by: Indus COMPAS on Feb 4, 2008 3:39 PM
Hi,
that's it. And after reading the text of the dump carefully this statement will attract
attention:
The maximum size of these data volumes can be set using the kernel
parameter 'abap/alvgrid/size_nodod_mb' (in mega bytes).
But this does not declare the reason why the session memory cannot be
released.
best regards
Tobias
Have you found out the reason why this is not releasing memory ?
I have similar prolbem - SITSPMON shows "currently available to ITS - 0 of 512MB"
WP0(10) Malloc Mem. 245,829,458 245,746,128 53,576 3,823
WP0(10) Shared (EG) 527,385,100 525,926,620 129,066 64,005
WP1(10) Malloc Mem. 0 0 0 0
even after bounce WP0, the memory still does not get released. users getting -
<ErrorMessage>New session was refused due to memory bottleneck</ErrorMessage>
<Date>20080428</Date>
<Time>121625</Time>
this is ECC 6.0 (basis 700) kernel patch 133.
thanks..Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.