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 "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/12/18 18:17:44 UTC

[jira] Resolved: (AXIS2-2033) SimpleHttpServer shutdown setUseListener(true) leaves sockets on server side in CLOSE_WAIT

     [ https://issues.apache.org/jira/browse/AXIS2-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen resolved AXIS2-2033.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5
         Assignee: Andreas Veithen  (was: Deepal Jayasinghe)

> SimpleHttpServer shutdown setUseListener(true)  leaves sockets on server side in CLOSE_WAIT
> -------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-2033
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2033
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Solaris2.9, Java5
>            Reporter: Michael Schick
>            Assignee: Andreas Veithen
>             Fix For: 1.5
>
>
> Using setUseListener(true) on client side causes a SimpleHttpServer to be run on Client and Server side.
> Using on client side "configContext.getListenerManager().stop()", does not cleanly stop. It seems that the
> server tries to re-connect during the shutdown. Further more it is noticed that on server side the sockets 
> used for communication remain in "CLOSE_WAIT".
> This leads eventually to the problem that the server runs out of file descriptors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.