> Yes, the addition of the shutdown() call[1] in 4.3.0 can cause ENOTCONN > occasionally. > > Ignoring the exception works, but given the cost of generating > exceptions in Ruby in the first place (especially 1.9), I don't > think it's a good idea... > > I can't reproduce this error. Are you on a UNIX listener or TCP > listene? What environment (OS/kernel version) is this?
I am running OS X 10.7.3, ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.3.0]. I was going to try it on my linux dev machine in a bit. I can get you kernel version then, if it occurs. I am just running unicorn in local dev and hitting it with a browser (Safari Version 5.1.5 (7534.55.3)) on localhost:8080. In production, I use a UNIX listener. (I am seeing no errors in production.) _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
