[jira] Commented: (CXF-1652) CXF Decoupled Endpoints are not getting cleaned up properly even after bus.Shutdown() in org.apache.cxf.systest.ws.rm.SequenceTest.

["Ulhas Bhole (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608509#action_12608509 ] 

Ulhas Bhole commented on CXF-1652:
----------------------------------

Further analysis suggest that the jettyHTTPDestination's deactiveate() method which is responsible for removing servant never get called.  Even if Bus.shutdown() would call jettyHTTPDestination shutdown() which then calls jettyHTTPTransportFactory's removeDestination(), This sequence only removes the Destination from the map hold by jettyHTTPTransportFactory but doesn't really inform JettyHTTPServerEngine to remove the servant. So unless the JVM is shutdown jetty threads will never go away.

I understand that there is some problem with keep alive and socket remaining open for 60 second afterwards as per the comment in jettyHTTPServerEngine's shouldDestroyPort() method. 



> CXF Decoupled Endpoints are not getting cleaned up properly even after bus.Shutdown() in org.apache.cxf.systest.ws.rm.SequenceTest.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-1652
>                 URL: https://issues.apache.org/jira/browse/CXF-1652
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.0.6
>            Reporter: Ulhas Bhole
>
> I am getting some test failures in ServiceMix test related to CXF  which points to lingering Decoupled endpoints started by some previous test. 
> So I tried org.apache.cxf.systest.ws.rm.SequenceTest from CXF Systest module and debugged it in Eclipse and see the same behaviour. If you monitor the threads each test that starts decoupled endpoint never get cleaned up and jetty therads keep listening on those ports.
> how To reproduce:
> Run org.apache.cxf.systest.ws.rm.SequenceTest  from eclipse and monitor debug stack trace. You will see the list of threads running with listener on port 9999,9998,9997 ....

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