Syslog Q01 when operating system call writev fails

[] [] [] [] [] [] [] [] [] []

  1. 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,...

Symptom

The syslog Q01 occurs when an attempt to write to a network connection fails.
The trace file dev_w* of the affected work process contains
entries such as the following:
M ***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3948]
M *** ERROR => NiIWrite: SiSendV failed for hdl / sock
(SI_ECONN_BROKEN/32; UD; ST; 127.0.0.1: ) [nixxi.cpp 3948]
M *** ERROR => IcmLogout: ICM_SEND failed (rc=-6) [icxxext.c 274]
M *** ERROR => ThPlgCleanup: IcmLogout failed (rc -8) [thxxplg.c 545
Where , and are numbers.
Other terms

Q01, ICM, Internet Communication Manager, restart
Reason and Prerequisites

Each work process connects itself to the ICM at the start. The system does not periodically check the status of this connection. If you restart the ICM, this is not communicated to the work processes. If you stop the work process, for example, using rdisp/wp_auto_restart, the work process tries to inform the ICM that it is being terminated and tries to close the connection to the ICM. This causes an error to occur because the connection already closed when you stopped the ICM.
Solution

Before the system attempts to write to the connection, it checks if the ICM terminated the connection. This error is corrected with a kernel patch and is available as of the following patch levels:
6.40: Not yet available
7.00: Not yet available
7.01: Not yet available
7.10: Not yet available
7.11: Not yet available

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment