From: "Catherine S." <pazuzule@...>
Date: 2010-10-25T16:07:18+09:00
Subject: Re: Concurrent Ruby webservices from wsdl2ruby

Charles Nutter wrote in post #956232:
> 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

Hi,

I'm having some success, currently with Ruby 1.8.6 and wsdl2ruby 
generated webservices (no proxy anymore/at the moment, client is using 
webservice directly), but my client isn't receiving the data still in 
appropriate time.
Appropriate time is 2-3 seconds, but it takes over 60 seconds to receive 
the soap answer from the webservice! (watched with Wireshark)

The delay is between accept and close of a socket, but not in the 
implementation of the webservice functionality - need to investigate 
more, perhaps threading? (still my favourite and non-favoured guess...)

But with the 'opening' and 'working on' various requests (especially at 
startup of client) Ruby seems to have a problem and I'm still thinking 
that my basic approach might be faulty?

@Charles Nutter:
JRuby version is:
jruby 1.5.3 (ruby 1.8.7 patchlevel 249) (2010-09-28 7ca06d7) (Java 
HotSpot(TM) Client VM 1.6.0_22) [x86-java]

This behaviour is described - for example - here: 
http://hype-free.blogspot.com/2006/10/what-to-do-if-you-have-many-timewait.html

I think, something like this is happening in JRuby... new instance, new 
instance finishs, system process takes over now-orphaned port,...

Best regards,
CS

-- 
Posted via http://www.ruby-forum.com/.