Hi Cliff, I believe that AXIS2C-1001, [1], is partially related. That means this issue is a part of the reported bug.
[1] https://issues.apache.org/jira/browse/AXIS2C-1001 Regards, Senaka > Hello Senaka, > > Thanks for your help with this. Is there an issue associated with this, > so that I can track the resolution of the bug. > > Cheers, > Cliff > > -----Original Message----- > From: Senaka Fernando [mailto:[EMAIL PROTECTED] > Sent: February 20, 2008 22:47 > To: Apache AXIS C Developers List > Subject: RE: FW: Question regarding the adjustment of response timeouts > > Hi Cliff, > > No you don't need to change that default value, you rather will be able > to simply specify the timeout in milliseconds inside your code after the > fix is applied. As Samisa says it is a straight forward fix. > > Regards, > Senaka > > On Wed, 2008-02-20 at 13:58 -0800, Clifford THOMPSON wrote: > I meant 60000ms... >> >> -----Original Message----- >> From: Clifford THOMPSON [mailto:[EMAIL PROTECTED] >> Sent: February 20, 2008 13:40 >> To: Apache AXIS C Developers List >> Subject: RE: FW: Question regarding the adjustment of response >> timeouts >> >> Hello Senaka, >> >> I took a look at "axis2_http_transport.h" and noticed that the >> constants, AXIS2_HTTP_DEFAULT_SO_TIMEOUT and >> AXIS2_HTTP_DEFAULT_CONNECTION_TIMEOUT, both held values of 6000ms. >> This coincides with the upper timeout limit our team was experiencing, > >> so it may provide a clue to the timeout problem. >> >> Cheers, >> Cliff >> >> -----Original Message----- >> From: Senaka Fernando [mailto:[EMAIL PROTECTED] >> Sent: February 18, 2008 11:35 >> To: Apache AXIS C Developers List >> Subject: Re: FW: Question regarding the adjustment of response >> timeouts >> >> Hi Cliff, >> >> We'll look into this before the 1.3.0 release and try to have it fixed > >> before we release. >> >> Regards, >> Senaka >> >> > Hello Dev Team, >> > >> > I presented this question with regards to using timeouts in the >> > axis2-c-user forum. Dimuthu is getting similar results under Linux, >> > and suggested that there may be a bug in timeout behaviour. Please >> > see >> >> > below for the details. >> > >> > Cheers, >> > Cliff >> > >> > -----Original Message----- >> > From: Dimuthu Gamage [mailto:[EMAIL PROTECTED] >> > Sent: February 16, 2008 05:23 >> > To: Apache AXIS C User List >> > Subject: Re: [AXIS2C] Question regarding the adjustment of response >> > timeouts >> > >> > Hi, >> > >> > I too checked it in Linux and got the same result, >> > >> > Seems we are not using axis2_options_get_timeout_in_milli_seconds >> > anywhere.. If this is a bug, should be fixed before the 1.3 release. >> > >> > Thanks >> > Dimuthu >> > >> > On Feb 16, 2008 1:07 AM, Clifford THOMPSON >> > <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Hello, >> >> >> >> I have a question about adjusting the timeout period for web >> services. >> > >> >> Our current software dictates that we can have upwards of a 300 >> >> second >> > >> >> delay before a response is sent (we have a large amount of data >> >> that needs to be prepared before being sent). Currently, our web >> >> service component will timeout after roughly 60 sec (I'm not sure >> >> if this is the Axis API, or from the OS). I have tried using some >> >> of the timeout >> >> >> functions in the Axis2C API, but they appear to have no effect (if >> >> I set the timeout 5 secs and the server takes 10 secs to respond, >> >> the client will wait 10 secs for the response). I am assuming that >> >> I am using the API incorrectly. We are working under WinXP, and >> >> have >> > generate portions of our code using the WSDL2C tool. >> >> We have chosen to generate synchronous code using WSDL2C (so the >> >> eventual call in the generate code will be to >> >> "axis2_svc_client_send_receive_with_op_qname"). Here is a rough >> >> paraphrase of the code that we have and how I thought the timeout >> >> function should be >> >> applied: >> >> >> >> env = axutil_env_create_all( "MyServiceLog.log", >> >> AXIS2_LOG_LEVEL_TRACE); >> >> assert(NULL != env); >> >> >> >> stub = axis2_stub_create_MyService( env, >> >> >> >> AXIS2_GETENV("AXIS2C_HOME"), >> >> >> >> "http://myserver.ca:8080/services/MyService";); >> >> assert(NULL != stub); >> >> >> >> >> >> status = axis2_options_set_timeout_in_milli_seconds( >> >> axis2_stub_get_options( stub, >> >> env ), >> >> env, >> >> 300000); >> >> assert(AXIS2_SUCCESS == status); >> >> >> >> /* */ >> >> /* lots of interleaving non-Axis2C code */ >> >> /* */ >> >> >> >> responseNode = axis2_stub_op_MyService_MyOperation( >> >> stub, >> >> env, >> >> headerNode1, >> >> headerNode2, >> >> bodyNode); >> >> if(NULL !=) >> >> { >> >> /* process the response */ >> >> } >> >> else >> >> { >> >> /* log the response error */ >> >> } >> >> >> >> Thank you in advance for the help. >> >> >> >> Cheers, >> >> Cliff >> >> >> > >> > -------------------------------------------------------------------- >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > -------------------------------------------------------------------- >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
