If it's package dependent it might be hard for the devs to reproduce.
To facilitate debugging, and to gather information for a JIRA post, try detecting the
deadlock. When the call hangs try connecting to the JVM using JConsole. (It's
included in the JDK for java5 and later.) From JConsole, go to the "Threads" tab
and click the "Detect Deadlock" button.
If you're on a linux (and I think also Solaris) system you can perform a "kill
-3" on the JVM process to get the same information. It will dump the thread state to
stdout.
--- On Thu, 5/13/10, malkhafaji <moe.alkhafaji(a)medcpu.com> wrote:
From: malkhafaji <moe.alkhafaji(a)medcpu.com>
Subject: Re: [rules-users] removeKnowledgePackage Call Hangs!!
To: rules-users(a)lists.jboss.org
Date: Thursday, May 13, 2010, 3:15 PM
I found out one more thing, this call above consistently
happens with that
rule and the package it is unloading. I checked another
rule that unloads
another package and it works consistently fine.
What could be the problem? I am assuming that if there are
threads launched
by Drools to execute rules that that would be taken into
account by Drools'
removeKnowledgePackage correct? So, there shouldn't be a
deadlock. So,
something is causing that call to hang on that package, but
not on another
package. Anybody has any idea where I can look for a
possible solution or
even where to start looking?
Thanks.
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/removeKnowledgePackag...
Sent from the Drools - User mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users