Fwd: catching soap::emptyResponseErrors

---------- Forwarded message ----------
From: Charlie B. [email protected]
Date: Oct 25, 2006 11:44 AM
Subject: catching soap::emptyResponseErrors
To: [email protected]

My SOAP client appears to be working fine, but the soap server I’m
connecting too seems flaky. How can I trap any errors and re-run the
call
to the service? Here’s what I’m doing. I get the error about 1 in 10
calls.

filterCriteriaArray = Array.new
filterCriteriaArray << ‘ListName=my_list’
members = obj.selectMembers(filterCriteriaArray)
members.each do |member|
puts “#{member.fullName}”
#methods = member.methods - obj.class.ancestors.methods
end

the error:
/usr/lib/ruby/1.8/soap/rpc/proxy.rb:145:in call': SOAP::EmptyResponseError (SOAP::EmptyResponseError) from /usr/lib/ruby/1.8/soap/rpc/driver.rb:179:incall’
from (eval):6:in `selectMembers’
from lmapiClient.rb:324

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs