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 )
In reply to SOAP::Lite problem by cornmek1
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |