[SMXCOMP-363] Jetty engine not stopped when CXF BC is undeployed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.2.3, servicemix-cxf-bc-2008.01
• Component/s: servicemix-cxf-bc

Environment

Win XP, IONA FUSE 3.3.1

• Regression: Regression
• Assignee: Freeman Yue Fang
• Reporter: doug harmon
• Created: 25/Jun/08 12:27
• Updated: 15/Feb/09 09:13
• Resolved: 29/Aug/08 02:19

Description

I'm able to successfully configure a CXF BC SU consumer to listen for requests via SSL. I set the busCfg attribute to a configuration file that is similar to the one found on the Apache CXF site[1] that configures the jetty engine to accept SSL requests. However, after undeploying my service assembly containing this su, the jetty engine is still running on the configured SSL port (my WSDL is no longer available as expected, but jetty is still listening on the port). Therefore all subsequent redeployments of this service assembly fail with the error: "Jetty server: Address already in use: JVM_BIND". I'm forced to stop and start the servicemix JVM in order to deploy and changes that I make to my service assembly.

After undeploying the SA containing the CXF BC, the jetty engine should also be shutdown.

[1]http://cwiki.apache.org/CXF20DOC/standalone-http-transport.html