> Ok, I reproduced it and found the problem with Ebean not shutting down
> in a timely fashion.

> Logged as BUG 176 : Shutdown taking 30 secs or so ... should be
> immediate

> http://www.avaje.org/bugdetail-176.html

> The problem was there is optionally a Timer that is used to warm the
> Ebean server cache. That Timer was not a daemon ... so effectively
> stopped the JVM from shutting down - hence hanging for 30 secs or so.
> The fix was to make the Timer a daemon - I also made the thread names
> a bit more meaningful.

> Fixed in HEAD.

> Cheers, Rob.

> On Oct 19, 7:38 pm, Rob Bygrave <robin.bygr...@gmail.com> wrote:
> > Hmmm. Well, I wasn't able to reproduce... in that it terminated in about 1
> > second or so.

> > I wonder if it is specific to a particular JDK/JVM.

> > On Mon, Oct 19, 2009 at 7:00 PM, Alex <alxa...@googlemail.com> wrote:

> > > Hi

> > > > I haven't tried this yet.  The code looks fine ... the line
> > > > "serverConfig.addClass(Hello.class);" ... should probably be outside that
> > > if
> > > > statement (you always register the bean even if you don't run the DDL).
> > > ok

> > > > You don't (shouldn't) need that explicit call to
> > > > ShutdownManager.shutdown();  Ebean registers a shutdown hook ... we
> > > should
> > > > never need to code that ourselves. I'm pretty sure you added that after
> > > you
> > > > got this issue.
> > > yes, that was the reason why I've added that.

> > > > I think we are running different JVM's (Linux, MacOS and I'm using
> > > Windows
> > > > mostly).

> > > > So yeah, I'll give it a go tonight. A ~1min wait/hang at shutdown ...
> > > I'll
> > > > probably look to use MySql so as to discount H2 background threads from
> > > the
> > > > issue.
> > > great, thanks, alx