I have a problem with a SOAP::Lite client making HTTP calls to a SOAP server.
At certain points in time, it stops working. Calls to "remote methods" die
Can't connect to my.host.name:80 (Bad file descriptor)
And that keeps happening until the program is restarted, which makes the
error message go away. Then it continues to perform around 270 (or more)
calls and then it breaks again. The number of calls each time are pretty
much the same when it stops working.
I used to re-use the SOAP object, but stopped doing that. That doesn't
help, and my current theory is that something doesn't get destroyed
properly so I'm trying to cache it more aggressively instead. ... Nope,
doesn't really help.
I have run this script on Solaris for years in production with no problem,
and in my Windows development environment during development. I have not
been able to figure out any other patterns when this happens.
Searching the Net didn't give me anything useful so I hope someone have
encountered this thing before.
Is this a known error message? Is it a known, fixed bug (see below)?
If not, what could it indicate? Where could I start looking in the
SOAP::Lite source? Something to do with sockets?
Is there a fixed number of file descriptors or something I could configure?
The SOAP::Lite client runs on w2k as a PerlApp application. It uses
SOAP::Lite 0.51 (I'd like to use a more recent version, but the program
calls a home-grown, non-compliant "SOAP server" that doesn't play well with
later versions for some reason). The program is designed to exit and be
restarted by a shell script after n minutes, to fully release all resources.
This is perl, v5.6.1 built for MSWin32-x86-multi-thread
Binary build 632 provided by ActiveState
PerlApp version: 2.0 <- old, but it works
 This is what I mean by "SOAP object":
-------- ------ ---- --- -- -- -- - - - - -
Johan Lindström Sourcerer @ Boss Casinos johanl@...
Latest bookmark: "Clio -- A Schema Mapping Management Tool"
dmoz (1 of 3): /Computers/Data_Formats/Markup_Languages/XML/ 12