[jira] Updated: (AXIS2-935) Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"
[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Davanum Srinivas updated AXIS2-935: --- Priority: Critical (was: Blocker) Not a blocker. > 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]
[jira] Updated: (AXIS2-935) Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"
[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Deepal Jayasinghe updated AXIS2-935: Priority: Blocker (was: Critical) I think we need to fix this before 1.1 > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-935) Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"
[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Deepal Jayasinghe updated AXIS2-935: Priority: Critical (was: Blocker) I dont think this a blocker for 1.1, so I am reducing the priority > 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: 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]
[jira] Updated: (AXIS2-935) Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"
[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Davanum Srinivas updated AXIS2-935: --- Priority: Blocker (was: Critical) Blocker? -- 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: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-935) Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"
[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Jeff Peterson updated AXIS2-935: Attachment: AXIS2-935.patch Attached "AXIS2-935.patch" > 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 >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]
