[ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12445214 ] Jeff Peterson commented on AXIS2-935: -------------------------------------
I'm pretty sure that I did not have REUSE_HTTP_CLIENT set, unless its the default. I still think this is a garbage collection/cleanup related issue. Even if you dont intend to reuse the HttpClient, the act of creating a HttpClient object also creates a new HttpConnectionManager for that client instance. The sockets associated with the HttpConnectionManager do not get cleaned up until garbage connection is triggered. So, in the non-reuse case, lots of http client objects are created (one per request). Each one has its own HttpConnectionManager, which is never explicitly cleaned up. Instead, it is up to the container to garbage collect them and free their sockets. Unfortunately, if the container is slow to get around to garbage collection, this can leave a lot of sockets open. > 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: Critical > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
