[Jetty-support] Re: Possible Bug in HttpServletContext upon Shutdown

[Greg W. <gr...@mo...>]

Tom,

this has already been fixed in the latest releases.

thanks



Tom Keeney wrote:
> Hi,
> 
>  
> 
> I’m not sure which list I should post a possible bug report to, so I
> chose this one so this problem can be captured somewhere in the Jetty
> community.
> 
>  
> 
> I’m running embedded Jetty 5.1.3 by starting an instance of HttpServer
> and adding a ServletHttpContext to it.  I noticed when I stop the
> server, mainly invoke HttpServer.stop(false) then HttpServer.destroy(),
> that the SessionScavenger thread is still alive.  I believe there is a
> problem in the ServletHttpContext.doStop() method since it is only
> releasing the reference to its servlet handler.  It should also stop the
> servlet handler, which would stop the SessionScavenger.  It seems like a
> bug since I noticed that the ServletHttpContext’s superclass,
> HttpContext, does in fact stop all contained handlers in its doStop()
> method.  With this in mind, perhaps one line should be added to the
> ServletHttpContext.doStop() method to invoke doStop() on the superclass
> before releasing the reference to the servlet handler:
> 
>  
> 
> protected void doStop() throws Exception {
> 
>     >>>super.doStop();
> 
>    _servletHandler=null;
> 
> }
> 
>  
> 
> I hope this helps!
> 
>  
> 
> Best regards,
> 
> Tom
>