Re: [rules-users] StatefulKnowledgeSession leaves threads running

The problem here is a different one. The engine is calling shutdown() on a thread pool and even without any task being executed, the thread is blocked in an internal JDK queue waiting for the timeout. I replaced the call by shutdownNow(), forcing the jdk to signal an interrupt to the thread and this seemed to work. I am investigating side effects of this procedure right now. []s Edson 2009/7/16 Mark Proctor <mproctor(a)codehaus.org&gt; Rafael Ribeiro wrote: > > Hi all, > > > > I've downloaded Drools fusion sample and started to make some changes > to > > the code (first of all wipe out the UI so I can test it easier). > > I tried to get to a minimal set so I can run a console main class and > see > > what happens but I am facing a strange behaviour. > > As soon as I start pushing events into the WorkingMemoryEntryPoint > > ("StockTick stream") a Thread - not daemonized since it blocks shutdown > from > > ending - is spawned and this prevents my JVM from shutting down > (obviously > > if I call System.exit(0) it will but I am avoiding this). > > I've tried both to halt and dispose the session that this entry point > > belongs but with no success. Does anyone know how could I get rid of > this > > thread? > > > Drools is starting up threads in a number of places now - using "new > Thread()". I think the plan is to change this to an interface call that > allows pluggable implementations. So that the user can decide how > threads are executed and stopped. > > Mark > > best regards, > > > > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users