ICM - Timeout Parameters

Question

Hi All,
We are facing issues with ICM only in one of the app servers. It is taking more load and going to emergency mode only in one app. I looked at ICM services in both instances
No. Protocol           Service Name/Port    Host Name            Keep Alive          Proc.Timeo Actv External Bind
  1  HTTP               8000                                  Host2               9,999,999                  1-
  2  SMTP               0                                        Host2               30                        9,999,999
icm/server_port_0     = PROT=HTTP,PORT=8000,PROCTIMEOUT=-1
No. Protocol           Service Name/Port    Host Name         Keep Alive             Proc.Timeo Actv External Bind
1  HTTP               8001                                 Host1               30                                              9,999,999
2  SMTP               0                                      Host1               30                                                9,999,999
icm/server_port_0     = PROT=HTTP,PORT=8001
Problem is with Host2. I see differences here. Please help fixing the issue. Which timeout parameter should I modify? If I just remove Proctimeout=-1, will it fix issue. Production is getting affected. PLs advise ASAP.
Thanks,
Kavitha Rajan.

Answer 1

Great - sorry I misunderstood you at first.
So the users come into the webdispatcher on the address ->  http://host1/sap/bc/bsp/sap/crm_ui_frame/default.htm -> this represents the address of the Web Dispatcher. The dispatcher however, seems to be over loading one of the application servers on the ABAP backend.
A few items I'd check then:
1) Logon to the admin console for the Web Dispatcher itself. Check to ensure that it is indeed seeing all of the logon groups configured in the ABAP backend.
2) Check the configurations of the ABAP logon groups for any issues - i.e. they are excluding servers.
3) Check the configuration of the ICM parameters in each of the ABAP servers - they should all be identicial unless you have exceptions noted.
4) For the Web Dispatcher itself, you may wish to set it up for a 'large system' scenerio with values like this:
icm/max_conn
icm/max_sockets
icm/req_queue_len
icm/min_threads
icm/max_threads
mpi/total_size_MB
mpi/max_pipes
16384
16384
6000
100
250
500
21000
The Web Dispatcher uses the configuration under "Accesssability of Message Server" to determine the location of a ABAP / J2EE message server and in turn read back the available logon groups. If the Web Dispatcher is seeing the logon groups correctly, then it's something to do with either the ICM settings on each app server or the logon group configurations itself.
The only thing I see odd here is that the servername for the Web Dispatcher is "HOST 1" but under the instance profile you have:
# Accesssability of Message Server
rdisp/mshost = Host1
ms/http_port = 8101
So unless that's a typo, are the WD and ABAP stack on the same server? "rdisp/mshost" should be pointing to the servername where the message server service (CI typically) is running for the ABAP stack.
Hope this helps.
Tim