axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Isajew (JIRA)" <>
Subject [jira] [Commented] (AXIS2C-1605) sockets are being left in CLOSE_WAIT state by client when using SSL in built-in http transport
Date Mon, 08 Oct 2012 11:32:02 GMT


Piotr Isajew commented on AXIS2C-1605:

To reproduce, https transport needs to be configured with the following settings:

<parameter name="PROTOCOL" locked="false">HTTP/1.0</parameter>
<parameter name="Keep-Alive" locked="false">true</parameter>

When client is working, number of file descriptors being open keeps growing, and at end leads
to this:

 [Sat Sep 29 09:05:00 2012] [error] http_client.c(256) Error
creating a socket. Most probably error returned by OS
[Sat Sep 29 09:05:00 2012] [error] http_client.c(257) Socket Creation failed.
[Sat Sep 29 09:05:00 2012] [error] http_client.c(572) Client data stream null or
+socket error for host and 443 port
[Sat Sep 29 09:05:00 2012] [error] http_client.c(574) A read attempt(HTTP) for
+the reply without sending the request
[Sat Sep 29 09:05:00 2012] [error] http_sender.c(1326) status_code < 0
[Sat Sep 29 09:05:00 2012] [error] engine.c(171) Transport sender invoke failed
> sockets are being left in CLOSE_WAIT state by  client when using SSL in built-in http
> -----------------------------------------------------------------------------------------------
>                 Key: AXIS2C-1605
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: transport/http
>    Affects Versions: 1.7.0
>         Environment: slackware linux, 2.6.39 kernel
>            Reporter: Piotr Isajew
>            Priority: Minor
> When using Axis2/C client with internal http transport via SSL and HTTP/1.0 protocol,
sockets are not being closed, and are left in CLOSE_WAIT state.
> After some time that leads to reaching open files limit by client process and failure
to invoke web service anymore.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message