You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Amanda Hopgood (JIRA)" <ax...@ws.apache.org> on 2005/03/09 13:05:52 UTC

[jira] Created: (AXIS-1860) FIN_WAIT2 states

FIN_WAIT2 states
----------------

         Key: AXIS-1860
         URL: http://issues.apache.org/jira/browse/AXIS-1860
     Project: Axis
        Type: Bug
    Versions: 1.2RC1, 1.2RC3    
 Environment: Windows
    Reporter: Amanda Hopgood


I have a problem when I use axis (seen with both 1.2RC1 or RC3), where if I use CommonsHTTPSender in my client wsdd file, then I can have my sockets left in FIN_WAIT2/CLOSE_WAIT combinations.
 
This occurs when my axis application sends out the HTTP request to remote application, and the remote application sends back response, and closes socket, but does NOT send back a Connection:close header in their response. This results in the connection at the remote application staying in FIN_WAIT_2 state, and on my side as CLOSE_WAIT.
 
I assume there is some situation where the method.releaseConnection is not being called.

I am not sure if this is the catch Exception at end of invoke in CommonsHTTPSender or a problem where the close of the ConnectionReleasingInputStream isn't being called.

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