axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Peterson (JIRA)" <j...@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"
Date Fri, 22 Sep 2006 05:07:23 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12436737 ] 
            
Jeff Peterson commented on AXIS2-935:
-------------------------------------

I think one of the key causes of this issue is a lack of proper cleanup/garbage collection.
 As a result, it is exhibited mostly in situations where the app server has a large heap and
a lax garbage collection policy.  Try increasing your app servers heap to something large
(i was using 2GB).

> 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: core
>    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


Mime
View raw message