[jira] Closed: (SOAP-161) Apache SOAP 2.3.1 socket leak.

[ji...@apache.org]

Message:

   The following issue has been closed.

   Resolver: Scott Nichol
       Date: Fri, 9 Apr 2004 6:19 AM

Since I never manage to solicit the posting of a patch, I have added a try/finally in HTTPUtils#post.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/SOAP-161

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: SOAP-161
    Summary: Apache SOAP 2.3.1 socket leak.
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: Apache SOAP
 Components: 
             All
   Versions:
             2.3

   Assignee: Scott Nichol
   Reporter: Frederic Bages

    Created: Sun, 11 Jan 2004 3:57 PM
    Updated: Fri, 9 Apr 2004 6:19 AM
Environment: Operating System: All
Platform: All

Description:
We use a socket timeout with our Apache SOAP client (running under tomcat) to 
ensure that we anwser (even if it's an error page) under 4 seconds. The 
problem is that the post method under the HTTPUtils source file does not close 
the socket in case of a timeout/other exception. This cause tomcat 4.1.29 to 
fail to listen on its port (Too many file open error). 
 
I've modified the source file to include a try { ... } finally { } clause 
closing the streams, socket, .... Since that modification the server has never 
stopped again.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira