cornmek1 has asked for the wisdom of the Perl Monks concerning the following question:

Hi,
I have posted this to the SOAP::Lite mailing list but I thought some SOAP'y novice's might be lurking in the pews with a handy RTFM reference. The Problem I have a SOAP::Transport::HTTP server ( daemon ) running on my solaris box. When I access the server using my PC SOAP::Lite client all is hunky-dory :@) When a collegue accesses the same service via IIS XMLHTML he gets the data, but the server is then 'hung' to my PC client, the IIS SOAP client still runs fine. If he kills the IIS server, I get access again. So it looks like there is some kind of lock condition, or maybe incomplete transaction going on ? Diagnostics. When I view the server process via truss I notice that my PC client leaves it in the following state accept(3, 0xFFBEF580, 0xFFBEF57C, 1) (sleeping...) which I guess is 'ok'. The IIS client however leaves the daemon as read(4, 0x00574050, 2048) (sleeping...) which I guess is 'bad'. The operative word is guess, and I wouldnt be surprised if I've be been bitten by some interoperability gotcha. Help! and thanks. ( FX: lights votive candles )

Replies are listed 'Best First'.
Re: SOAP::Lite problem
by dragonchild (Archbishop) on Jan 27, 2005 at 16:04 UTC
    Check to see if the IIS client has keep-alive turned on.

    Being right, does not endow the right to be rude; politeness costs nothing.
    Being unknowing, is not the same as being stupid.
    Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
    Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.