PHP wizards, represent! :)

Everything todo with programming goes HERE.
Post Reply
User avatar
Lucifer
Project Developer
Posts: 8683
Joined: Sun Aug 15, 2004 3:32 pm
Location: Republic of Texas
Contact:

PHP wizards, represent! :)

Post by Lucifer »

Ok, here's the problem.

The server is a new installation of Mandriva LE 2005, so it's Apache2, php4.3, and a few others. (I had to install php4.3 and run it instead of the php5 it installed already)

In one directory is a soap server based on nusoap, a php library for making soap servers. :) There are actually two implementations of the soap server, the one I've been complaining about and my own OOP version of it.

In another directory is Mambo, and a component I've written that uses the nusoap library to hit the soap servers aforementioned.

So let's name the two soap servers like this:
Procedural - the official soap server
Lucifer's - my OOP version of the same soap server

From the soap client embedded in Mambo as a component:

1. If I direct it to the Procedural soap server, I get this for the actual RPC:

Code: Select all

soap_transport_http: read line of 0 bytes: 
soap_transport_http: socket read of headers timed out after length 0
soap_transport_http: read before timeout:

soap_transport_http: end of send()

soap_proxy_1127364502: Error: HTTP Error: socket read of headers timed out
But for the WSDL retrieval, it *works fine*.

2. If I direct it to Lucifer's server, it works fine, flawlessly, without errors of any sort, and the data gets returned properly.

Both servers are built with nusoap and the client is nusoap. Both servers, the application they're embedded in, Mambo, and my component are all hosted on the same Apache server, same physical machine (my laptop), running Mandriva LE 2005 (aka Mandrake Linux 10.2).

3. Now, if I reboot and run the test of the Procedural server in XAMPP under windows, it *works fine*.

4. If I set the server up as an SSL server, nusoap uses cURL for the connection to the soap server. Again, the Procedural server has the same problem and LUcifer's server runs flawlessly.

I can't post the code because it hasn't been released, and it can't be released until it tests fine (we might ignore this problem and release it anyway, at which point I can direct you to the appropriate code).

Any ideas?
Image

Be the devil's own, Lucifer's my name.
- Iron Maiden
Post Reply