Hey,
We're having an issue with soap4r, using it as a SOAP client to some web services. Basically, what happens is we fire up a Mongrel with soap4r, and it works fine for a random number of requests, then suddenly stop working - it makes a connection to the Tomcat (or Apache, or whatever) server, but never sends the POST request. Here is an example from the logs:
-- start of logs --
Wire dump:
= Request
POST /soap/locationfinder HTTP/1.1
SOAPAction: ""
Content-Type: text/xml; charset=utf-8
User-Agent: SOAP4R/1.5.9-SNAPSHOT (/187, ruby 1.8.6 (2008-03-03) [x86_64-linux])
Date: Fri, 04 Apr 2008 20:44:44 GMT
Content-Length: 474
Host: localhost:8080
-- end of logs --
Until we kill that mongrel, it is unable to service any other requests - it just sits there with the socket open.
I know this is a rather vague ticket, but have you seen issue(s) like this? We were originally running SOAP4R 1.5.8; I've tried the current svn for 1.5 (as seen above) with the same issue. If you have any ideas on how to debug this, we'd appreciate it! We've verified that the web services are fine - we can hit it at the same time with other ws clients with no issues, even using something like Charles to just pound it.
Appreciate any thougsh!
