|
 |
Sacha Mallais
|
 |
|||||||||
|
|
|
|||||||||
|
|
|
| Navigate Database Table: "WOFAQ" | ||||||||||
| Current record is #7 out of 21 in found set (21 total records in table) | ||||||||||
|
|
|||||||||
| Question | Under a increased load there is a large number of TCP connections in CLOSE_WAIT state. When there is enough of them the adapter to no longer able to find any app (including the JavaMonitor) and the whole system grinds to a halt... This is under WO 5.2.3. |
|---|---|
| Answer | The cause is a bug in wotaskd in WO 5.2.2 and 5.2.3. The only real solution is to upgrade to WO 5.2.4. If that is not possible, a workaround is to simply kill wotaskd once a night. It may also be possible to write a script to detect this condition and kill wotaskd. |
| Figure 1 | No file available. |
| Figure 2 | No file available. |
| Figure 3 | No file available. |
| Date Modified | Mar 29 2006 |
| Modified By | sacha@global-village.net |