Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <25587780.1161955279201.JavaMail.root@brutus>
Date: Fri, 27 Oct 2006 06:21:19 -0700 (PDT)
From: "Davanum Srinivas (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS2-935) Connections are not properly released
 causing them to stick in the "CLOSE_WAIT" state and cause "Too many files
 open"
In-Reply-To: <33401626.1153952833823.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12445182 ] 
            
Davanum Srinivas commented on AXIS2-935:
----------------------------------------

If they use REUSE_HTTP_CLIENT, they can access the HTTPClient and tweak whatever they need to tweak. So let's leave it alone.

thanks,
dims

> Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-935
>                 URL: http://issues.apache.org/jira/browse/AXIS2-935
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.0
>         Environment: Weblogic 8.1.2, Solaris 8 (dont ask!)
>            Reporter: Jeff Peterson
>         Assigned To: Deepal Jayasinghe
>            Priority: Blocker
>         Attachments: AXIS2-935.patch
>
>
> It appears that org.apache.axis2.transport.http.SOAPOverHTTPSender does not properly cleanup the http post connection after payload has been sent.
> The symptoms of this problem show up in `netstat` as literally hundreds of connections in the "CLOSE_WAIT" state.  On a busy server this can cause the application to report exceptions with the message "Too many open files."
> I looked in the source code for axis2 1.0 and discovered that in SOAPOverHTTPSender.java the releaseConnection() is never called on the postMethod variable.  This seems to be a likely candidate for the source of the issue.
> See SOAPOverHTTPSender.java:97-118

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org