Hi Marcin, You likely started another runtime somewhere else in the code. That needs to be shutdown too of course.
Andrus On May 27, 2011, at 4:33 AM, Marcin Skladaniec wrote: > Hi > > In my application I start embedded derby and jetty http server (as a servlet > container). Then the cayenne runtime is initiated (for both 1tier and ROP). > > When the application shuts down I reverse this order, first closing the > cayenne service by runtime.shutdown(), then jetty then db. All seems fine, > database and jetty stops fully, but from about 18 cayenne-edt threads only > half is finalized. Also I can see a few PoolManagerCleanup threads, which > seems to be originating from cayenne as well. > > Is there something I'm doing wrong? > > below is an example list of threads when application is meant to quit. > > ... > Daemon Thread [cayenne-edt-20121261-1] (Running) > Daemon Thread [cayenne-edt-20121261-2] (Running) > Daemon Thread [cayenne-edt-20121261-4] (Running) > Daemon Thread [cayenne-edt-20121261-3] (Running) > Daemon Thread [cayenne-edt-20121261-0] (Running) > Daemon Thread [PoolManagerCleanup-5665047] (Running) > Daemon Thread [cayenne-edt-25452612-0] (Running) > Daemon Thread [cayenne-edt-25452612-2] (Running) > Daemon Thread [cayenne-edt-25452612-1] (Running) > Daemon Thread [cayenne-edt-25452612-3] (Running) > Daemon Thread [cayenne-edt-25452612-4] (Running) > Daemon Thread [PoolManagerCleanup-32749756] (Running) > Daemon Thread [PoolManagerCleanup-9280290] (Running) > Thread [DestroyJavaVM] (Running) > > Thanks > Marcin >
