Hook for lifecycle "stop"?

[Nick Telford]

Hi Coda,

Firstly - Dropwizard looks excellent, exactly the sort of glue I've been looking for. Thanks for sharing it with the world.

I'm looking to integrate a DW project in to the Apache Commons Daemon process container (jsvc) and I was wondering if there are any "stop" hooks that can be used to gracefully shutdown the process?

I had a look through the code and it appears as if the Command abstraction causes the lifecycle to be encapsulated in a ServerCommand and thus unavailable from the initializing context.

Regards,

Nick Telford

[Coda Hale]

Check out Managed and Environment#manage().

--
Coda Hale
http://codahale.com

[Nick Telford]

These appear to register a Managed object for the Jetty LifeCycle to manage. Is there a facility to invert this - so an external object can manage the lifecycle of the Environment?

Specifically, I'm looking for a way to externally "stop" the Environment - aside from just sending the process SIGINT.

[Coda Hale]

Ah, I see what you mean. No, there currently isn't.

I'll give it some thought, or if you come up with something you can send me a pull request.

--
Coda Hale
http://codahale.com

[Christophe Furmaniak]

I don't think this hook has been provided.

Maybe providing a mechanism that works like jetty start.jar Monitor class  could be interesting? (see https://github.com/eclipse/jetty.project/blob/master/jetty-start/src/main/java/org/eclipse/jetty/start/Monitor.java)

[snoopy woodstock]

https://github.com/codahale/dropwizard/pull/220

Hopefully, the pull request will be accepted, or re-worked to make it available.

[snoopy woodstock]

https://github.com/codahale/dropwizard/pull/220