Anonymous | Login | Signup for a new account | 12-17-2024 11:43 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001073 | [Resin] | minor | always | 04-24-06 13:38 | 06-16-06 10:26 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | urgent | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.0.20 | Product Version | |||||
Product Build | |||||||||
Summary | 0001073: close_wait with iis | ||||||||
Description |
(rep by Martin Weinig) We are currently testing one of our applications in Resin Pro 3.0.14 that is currently in production in Resin 2.1.16. While testing I am noticing an ever-increasing number of TCP connections hung in a CLOSE_WAIT status. Eventually the HTTP server stops responding. Our configuration utilizes 2 HTTP servers running IIS with the Resin ISAPI Plugin and 3 servers running Resin. My 3 Resin servers are 10.4.198.56, .57, & .58. The hung TCP connections are from the IIS server to the application servers. Restarting IIS clears up all of the connections, but restarting the Resin service doesn't seem to have the same effect. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |