|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4639 | minor | always | 06-22-11 11:44 | 07-07-11 14:13 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.19 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.20 | ||
|
|
|||||
| Summary: | 0004639: CLOSE_WAIT | ||||
| Description: |
(rep by Mark Price) we've noticed some odd behaviour with sockets being left in CLOSE_WAIT state inside of resin. Attached are two outputs from netstat taken 15 minutes apart that show several connections in this state for the duration of that period. The server in question is not handling a great deal of traffic, in fact the source of about half of the connections is a local monitoring process which essentially does a web-ping to the resin server (and cleanly closes its connection). We also saw this behaviour in out production environment, with sockets remaining in this state for several hours. >From what I can gather, CLOSE_WAIT implies that the tcp stack is waiting for the local application to close the socket. We are using a pre-release version of resin 4.0.19 - is this a known issue? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |