Re: [jetty-users] Upgrade Jetty 8 to 9

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

Actually, the setGracefulShutdown() has been migrated to ShutdownThread.register(LifeCycle)

In reality, the Server.setStopAtShutdown(boolean) simply calls this behavior.

With Jetty 9, there is the possibility of having multiple lifecycles active in the same JVM. 

Such as using Jetty Client, Jetty WebSocket Client, or even having multiple Server instances in the same JVM.

So the logic for proper LifeCycle.stop() and Destroyable.destroy() is now generalized for all cases on a Runtime shutdownHook.

As for a migration guide, that could be a good idea.

I went ahead and opened an issue on that

https://github.com/jetty-project/jetty-documentation/issues/12

--

Joakim Erdfelt <joakim@xxxxxxxxxxx>

webtide.com

Developer advice, services and support
from the Jetty & CometD experts

eclipse.org/jetty - cometd.org

On Wed, Jun 26, 2013 at 7:26 AM, Kristian Rosenvold <kristian.rosenvold@xxxxxxxxx> wrote:

From what I gleaned by liberal use of git-pickaxe, setGracefulShutdown
is now called setStopTimeout

Kristian

2013/6/26 Stephen Colebourne <scolebourne@xxxxxxxx>:

> Is there a migration guide? I can't seem to find one.
>
> Specifically, what is the replacement for server.setGracefulShutdown(timeout) ?
>
> Finally, is there a documentation page which describes what each of
> the maven jars is meant to do? For example, the difference between
> jetty-servlet and jetty-servlets.
>
> thanks
> Stephen
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users