You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Hopgood, Amanda" <Am...@logicacmg.com> on 2005/03/07 10:03:10 UTC

fin_wait states

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.
 
Has anyone else seen this problem? Is there anyway I can resolve this
problem? I have not seen this problem when I've used commons httpclient
when used without axis for non-SOAP applications.
 
Thanks,
Amanda

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.