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 514:32:532013
[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 514:32:542013
[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 514:32:552013
[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-eb5d95e03747?overridelayout=true
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