I read this in some oracle forum:
"You may want to check if your updating the HashMap concurrently. If you are
then the HashMap can get internally corrupt (The items in one bucket can get
a circular linked reference) and result in a infinite loop upon calling
get(). If this is the case use ConcurrentHashMap instead."
I wonder if changing org.drools.util.CompositeClassLoader$CachingLoader
from HashMap to ConcurrentHashMap solves this.
actually "long pSpmaId" shouldnt be resolved. Since drools should know its
type "long" anyway from parameter declaration.
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com