Re: Error from http_client.c "http client , response timed out"

[nshifman]

Hi Nandika,

The issue was resolved without me having to change anything in my AXIS2C client code.
It's possible that the problem was at the endpoint web server.
The feedback from the web server support team was: "we do notice occasionally such issues getting fixed by service restarts (to clear any hung sockets)".

One additional point: it's a little confusing when the axis2c http client function returns "response timed out" error in this case.  You can clearly see from the axis2c log file, that the error was returned within one second after the request was sent, and the timeout is set to 30000 mlsec, as returned by the axis2_options_set_timeout_in_milli_seconds method.

Thank you for your help.

Nadine

Nadine Shifman---08/29/2012 08:43:34 AM---Hi Nandika, Thank you for your reply.

From:	Nadine Shifman/Person/World Bank
To:	Nandika Jayawardana <jayaw...@gmail.com>
Cc:	Apache AXIS C User List <c-user@axis.apache.org>
Date:	08/29/2012 08:43 AM
Subject:	Re: Error from http_client.c "http client , response timed out"
	458-8812   IMTTR

---

Hi Nandika,

Thank you for your reply.
The endpoint is accessible from the machine I am running axis2c from.  I have tested it with other applications like telnet, and tcpmon ( my client application is on Solaris ).
It's unlikely that the timeout is the real issue, as the error is returned within just a few seconds after the call to axis2_svc_client_send_receive() function, and the timeout is set to 30000 mlsec.

Regards,
Nadine


Nandika Jayawardana ---08/29/2012 01:40:14 AM---Hi Nadine, Looks like the specified endpoint is not accessible from the machine you

From:	Nandika Jayawardana <jayaw...@gmail.com>
To:	Apache AXIS C User List <c-user@axis.apache.org>
Date:	08/29/2012 01:40 AM
Subject:	Re: Error from http_client.c "http client , response timed out"

---

Hi Nadine,
Looks like the specified endpoint is not accessible from the machine you are running axis2c or the client is timing out. You can adjust the timeout by using the axis2_options_set_timeout_in_milli_seconds method. 

Another option would be to use a client like soapui to check whether the endpoint is accessible from the machine.

Regards
Nandika

On Wed, Aug 29, 2012 at 2:06 AM, <nshif...@worldbank.org> wrote:

Hello,

I am sending a request to a Web Service using the function axis2_svc_client_send_receive().
I tested it with several web services and it worked fine, expect for one case, when I get the following errors, and the above function returns NULL.

[Mon Aug 27 15:04:27 2012] [debug] http_transport_sender.c(246) ctx_epr:http://some_url
[Mon Aug 27 15:04:27 2012] [debug] http_transport_sender.c(807) using axis2 native http sender.
[Mon Aug 27 15:04:27 2012] [debug] http_sender.c(416) msg_ctx_id:urn:uuid:065f0be7-f06a-2e10-21a7-00213848b676
[Mon Aug 27 15:04:27 2012] [debug] http_client.c(571) http client , response timed out

When I send requests to this URL "some_url" manually, through other test applications that don't use AXIS2C, everything works fine.

When initializing my AXIS2C client, I don't set the timeout in options specifically.
If I call the function axis2_options_get_timeout_in_milli_seconds() after creating the client (with axis2_svc_client_create), the timeout value returned is 30000.
This is 30 sec, and it should be enough for the web service to respond.

I would appreciate an advise, what could cause this problem, and how to solve it?

Thanks,
Nadine Shifman
Software Consultant, WorldBank.
--------------------------------------------------------------------- To unsubscribe, e-mail: c-user-unsubscr...@axis.apache.org For additional commands, e-mail: c-user-h...@axis.apache.org 

<<inline: graycol.gif>>

<<inline: ecblank.gif>>