The client error log indicates the timeout:
[Thu Nov 19 18:30:56 2009] [debug] http_client.c(571) http client , response timed out
[Thu Nov 19 18:30:56 2009] [error] http_client.c(574) Response timed out
[Thu Nov 19 18:30:56 2009] [error] http_sender.c(1381) status_code < 0
[Thu Nov 19 18:30:56 2009] [error] engine.c(179) Transport sender invoke failed
[Thu Nov 19 18:30:56 2009] [error] TestCases.c(239) Stub invoke FAILED: Error code: 92 :: Response timed out
The default timeout is 60000 ms (1 minute) as given in axis2_http_transport.h
To increase the timeout to the required value of 300 seconds (300000 ms), I set the option in the client as follows.
axis2_options_set_timeout_in_milli_seconds(options, env, 300000);
Responses taking more than 2 minutes are now returning properly.
George
-------------- Forwarded Message: --------------
From: Sam Carleton <scarle...@miltonstreet.com>
To: Apache AXIS C User List <axis-c-user@ws.apache.org>
Subject: Re: [ot] adjusting timeouts
Date: Sun, 15 Nov 2009 22:29:04 +0000
George,Actually, after a bit more investigation I discovered the error was between the keyboard and chair...The .Net client is setting up the binding at runtime... I discovered that that after the .Net client set SendTimeout to 10 minutes, it set it to 25 seconds. Opps!SamOn Sun, Nov 15, 2009 at 4:01 PM, <gsherw...@att.net> wrote:I too am interested in how to set the timeout for the Axis2/C module. Rarely my application will need up to 300 seconds (the Apache httpd default). But I have not tried that yet.
Thanks,
George
-------------- Original message from Sam Carleton <scarle...@miltonstreet.com>: --------------
My Axis2/C code is being used by a .Net client and being hosted via Apache 2.2 and mod_axis2. I have set the SendTimeout on the .Net binding to 10 minutes but things are still timing out in about 30 seconds. I am wondering if anyone in this forum has run into this problem and has any suggestions on setting on either apache or the .net side to extend the timeout.
