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