From: Charles Oliver Nutter Date: 2010-10-22T13:34:04+09:00 Subject: Re: Concurrent Ruby webservices from wsdl2ruby On Wed, Oct 20, 2010 at 4:06 AM, Catherine S. wrote: > With the possible thread problem I switched to jruby and ran my > applications with this. On TCPView I saw that there are instances of > jruby started, finished and simultaneously another port goes to > TIME_WAIT. They remain there until my process dies/gets killed. As far > as I read, this is 'normal', but I'm not really proud of this ressources > usage and until now I didn't find the reason for starting another > jruby-instance... It's possible you tried a version of JRuby that had some issues with selectors that caused sockets to be kept open in TIME_WAIT for a while. What version did you try? Where did you read that the TIME_WAIT was normal? - Charlie