Connection error between clients and ICM/Web dispatcher
[dispatcher] [dispatcher handler] [EXTBIND] [icm/listen_queue_len] [icmbnd] [java dispatcher] [struts2 dispatcher]
- Missing response cookies in log file of ICM Web dispatcherSymptom In the HTTP log file of the ICM or the SAP Web Dispatcher, the system no longer writes response cookies. Other terms response cookies, HTTP, HyperText Transfer Protocol, logging, missing, ICM,...
- SAP Web Dispatcher 7.10: Patch historySymptom You want to assign the changes to the SAP Web Dispatcher to a patch level. Other terms sapwebdisp, HTTP load balancing, webdispatcher, wbdisp, wdisp, dispatcher, HTTP, HTTPS, ROUTER Reason and Prerequisites...
Symptom
In load situations, HTTP/HTTPS clients sometimes receive a timeout error or the error message “Connection timed out” from the Internet Communication Manager (ICM) or SAP Web Dispatcher.
Other terms
icm/listen_queue_len, icmbnd, EXTBIND
Reason and Prerequisites
The error occurs only when you use icmbnd. The use of icmbnd is activated using the option EXTBIND=1 for the parameter icm/server_port_.During connection setup, the operating system must keep requests in a queue. The parameter icm/listen_queue_len specifies the maximum number of connections that can have this status. The standard value is 512.If this queue is full, the system rejects any additional connection requests without notifying the partner.Due to an error, the queue length is always set to 20 when you use the icmbnd. This may lead to the error described above when there is a high load.
Solution
The error is corrected with the following patch levels:
7.00: Not yet available
7.01: Not yet available
7.10: 150
a97v5e2ni3
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}