IcmAcceptClient: server overload: conn: 500 - accept delayed

[Former Member]

I am using a NetWeaver AS Java 7.40 8 node cluster to test out some demanding processing and when doing so I noticed I begin to see some sluggish response times with our web application and via SAP NetWeaver Administrator. I feel like we may have too many concurrent HTTP requests going on. As a result, I am trying to figure out how to confirm this or tweak the timeout NetWeaver permits by default for requests and/or tweak the number of requests that can be handled at once.

Also, I am seeing issues in the SAP Web Administration Interface’s Core System’s Trace section with overloads. Please see the following for a snippet of the warnings I'm seeing.

[Thr 140478444431200] Thu Sep  5 14:32:53 2013
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]

[Thr 140478444431200] Thu Sep  5 14:32:54 2013
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]

[Thr 140478444431200] Thu Sep  5 14:32:55 2013
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]
[Thr 140478444431200] *** WARNING => IcmAcceptClient: server overload: conn: 500 - accept delayed [icxxman.c    4861]

What do these mean and how can they be addressed?

I am interested in trying to tweak some timeout properties or maybe the number of requests that can be handled by the dispatcher. How do I get to the following tool:

•    http://help.sap.com/SAPHELP_470/Helpdata/EN/ac/8f813a34872769e10000000a114084/content.htm

The SAP Web Administration Interface seems similar, but does not allow me to “administer” the ICM in anyway it appears. How do I launch this tool?

Section 2.1 of the the following link describes dealing with timeout issues via the transaction code SMICM tool? What is this and how do I launch this tool in NetWeaver 7.40 AS Java (I have been told that this tool is possibly only available to ABAP systems?)?

•    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03...

Also, I found this article that describes the round robin load balancing used by the web dispatcher. Would this need to be tweaked possibly?

•    http://help.sap.com/SAPHELP_NW70EHP3/helpdata/EN/48/99C3D999273987E10000000A421937/content.htm

Any assistance on troubleshooting either the database connection pooling problem or what appears to be a “too many requests” problem for the dispatcher would be greatly appreciated! 

-- Kevin

tracefile.txt.zip

[anandkarthik_raja · Accepted solution]

Hi,

Check your network name enviroment for correct spelling of host names.
Check your /etc/services file (please check  permissions on
/etc/services file to allow user <sid>adm to read the file and get the
message server port number).
Check the profile settings.

Please see notes 63342, 42074.

0413330  Network timeouts
0500235  Network Diagnosis with NIPING
0559119  Call disconnections in the syslog or dev_rd

Please check the health of your network to ensure constant connectivity.
To do this you have two SAP tools (niping and lgtst). For further
info, please have a look at the  Notes 30289 and 64015.

[Former Member]

Hi Kevin,

did you solve your problem?

I have the same issue if I set the icm/host_name_full = "alias_of_web-dispatcher" in the SAP ABAP+Java application server.

Thanks for your help.

Regards,

Paolo

[Aleksandr]

Hello.

Please look at this note 1753749 - Cannot clear ICM server cache

[Former Member]

Hi Kevin,

Technically speaking there ain't any dispatcher.. They got rid of  that for JAVA AS way back with PI 7.1. and from core NW with 7.3.

SMICM is of course only in ABAP. Infact ICM is a relatively new addition to JAVA stack .

For this please visit:

http://help.sap.com/saphelp_nw74/helpdata/en/47/8d787bf41a4f8fad4c225bea4247bb/content.htm

and for its parameters:

http://help.sap.com/saphelp_nw74/helpdata/en/48/62fdfb7df458d8e10000000a421937/content.htm

[Former Member]

Hi Ruchit,

Thanks for taking the time to respond and thanks for this information. I was able to find these parameters, though I was looking at older documentation, for the ICM at here which are prefixed by "icm/" and then these parameters for the Web Dispatcher at here where are prefixed by "wdisp". However, none of the help documents I have found described where to use these parameters. Thankfully another colleague was able to point to the following file /usr/sap/RL3/SYS/profile/DEFAULT.PFL. There seem to be other profiles in this directory for each node in my cluster, but its not clear which should be edited or just the DEFAULT.PFL. Upon restarting my NetWeaver nodes, I was able to see the new values in the Web Administration Interface --> Internet Communication Manager Menu --> Core System --> Parameters (ie, http://rl3nw74:50000/sap/admin/public/default.html). 

Are you saying there is no web dispatcher at all anymore? There is no similar web page to see what web dispatcher properties are set? Because I did find a tool called "wdispmon" which I could use:

rl3nw74:rl3adm 94> wdispmon -function ICMGetStatus
wdispmon=>sapparam(1c): No Profile used.
wdispmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ICMGetStatus
OK
status, pid, max_threads, peak_threads, cur_threads, used_threads, total_threads, max_conn, peak_conn, cur_conn, total_conn, max_req_queue, peak_req_queue, cur_req_queue, total_req_queue, float_req_queue
running, 24939, 1000, 183, 166, 0, 205, 1000, 502, 6, 11940, 10000, 31, 0, 10460, 0

Is this the same as the Web Administration Interface for ICM? If these "wdisp/" prefixed properties are still valid in this version of NetWeaver, are they just set in the same DEFAULT.PFL? Also, some of the properties say they are shared. Does that mean for example that "icm/max_conn" works for both ICM and the Web Dispatcher? Or, does the property need to go into two different locations? Or, does it mean that there is a "icm/max_conn" and "wdisp/max_conn"?

Thanks,

Kevin