Posted by lkosak on 06/05/07 21:50

On Jun 5, 2:31 pm, lko...@gmail.com wrote:
> Hi everyone,
>
> I am encountering what appears to be a timeout problem using a PHP
> soap client to connect to a VB.net soap server. I cannot provide the
> WSDL as it is only available for internal use -- if this is essential
> I can create an equivalent mockup.
>
> I'm running an Apache 1.3 webserver. I call the script via a web
> browser.
>
> php.ini has the following pertinent settings:
>
> default_socket_timeout = 120
> max_execution_time = 60
> memory_limit = 20M
>
> A simple equivalent to the script looks like:
>
> <?php
>
> $soapClient = new SoapClient('http://www.example.com/path/to.wsdl',
> array('connection_timeout' => 120));
>
> try {
> $soapClient->WaitBeforeResponse(500);} catch(Exception $e) {
>
> echo $e->getMessage();
>
> }
>
> ?>
>
> The server method WaitBeforeResponse sleeps for the time provided, and
> then returns 'Hello, World!'.
>
> Consistently, after 15 seconds the Soap Client throws the following
> exception:
>
> "Error Fetching http headers"
>
> Nowhere in any of my configuration files do I see the number '15' come
> up. If WaitBeforeResponse(5) is called, it returns 'Hello, World!'
> correctly.
>
> Is anyone aware of a configuration directive I am missing that would
> explain the consistent 15 second timeout? When executed directly on
> the soap server (.NET provides built in WSDL execution functionality)
> calls can take as long as they want, and still ultimately produce a
> result.

Apologies, I discovered that somewhere between php.ini and script
execution, default_socket_timeout is being set to 15.

[Back to original message]