HTTP Binding : Jetty connection not closed when FraSCAti stop

The problem occurs when a HTTP binding is used in a composite and this composite is started on a tomcat embedded FraSCAti (packaged in a war).

When the stop command is sent to the tomcat server, the FraSCAti composite are trigered to stop. There is a problem with the components using a HTTP binding, the jetty resources are not unregistred/destroyed correctly.

In some cases, the java process ends but in others the java process remains alive and the resart of the application is not possible because the error "port already in use is throwed".

After some researchs, we have seen that the JettyServletManager.unregisterServlet(...) method is never called for an HTTP binding. In the HttpBinding class, there are an init and a destroy methods associated with @init and @destroy annotations. These annotations do not seem to work. The destroy method is never called and the init method is called "manually" in the FrascatiBindingHttpProcessor class (See method doInstanciate, line 154).