On Aug 14, 2008, at 2:58 PM, david day wrote: > Resin 3.1.3 with Apache 2.0.52 > > While troubleshooting a site failing to respond, I've found many > connections remain in CLOSE_WAIT indefinitely, even after leaving > Resin shut down for hours. Connections are between Resin and > Apache/mod_caucho on the server in question, or another load balanced > server. Connections are only cleared by bouncing Apache.
Well, the CLOSE_WAIT is basically the fundamental limitation of Apache as a load balancer. Since Apache isn't threaded, mod_caucho doesn't have a reaper thread to go around and close all the expired sockets, so sockets only get cleaned up when the next request arrives at that Apache process mod_caucho and is dispatched to Resin. Until that happens, only the Resin end of the socket is closed. Still, that shouldn't freeze the site. It's just a little messy. -- Scott > > > I'm hoping someone has seen this and can recommend a fix, but haven't > found much help with Caucho bugs or internet searches. > > Where: > server1= 192.168.1.40 > server1 app= 192.168.1.43 – Resin srun 6804 > server2= 192.168.1.70 > server2 app= 192.168.1.73 – Resin srun 6804 > > And several connections containing: > tcp 1 0 192.168.1.40:35514 192.168.1.73:6804 > CLOSE_WAIT > tcp 1 0 192.168.1.43:35514 192.168.1.43:6804 > CLOSE_WAIT > tcp 1 0 192.168.1.43:35514 192.168.1.70:6804 > CLOSE_WAIT > > David > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
