[
https://issues.apache.org/jira/browse/AXIS2-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676359#action_12676359
]
Alexis Midon commented on AXIS2-935:
------------------------------------
I have the exact same issue with the default settings (axis 1.3): unclosed
connection and too many open files.
I tried the options REUSE_HTTP_CLIENT and AUTO_RELEASE_CONNECTION and drew the
exact same conclusions as Guillaume (see his comment above):
. REUSE_HTTP_CLIENT starves the pool and invocations hang out
. AUTO_RELEASE_CONNECTION release the connection, but before the SOAP handler
had a chance to read the http input stream :(
> Connections are not properly released causing them to stick in the
> "CLOSE_WAIT" state and cause "Too many files open"
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-935
> URL: https://issues.apache.org/jira/browse/AXIS2-935
> Project: 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
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
