Thanks for the response.
I thought I had read that the CompositeClassLoader was not being used in
v6.x.
I'd like to be able to experiment with the current version of Drools v6.x,
but I'm still trying to work
past the issue I have with the non-passive changes of protobuf v.2.5.0 that
Drools v6.x
On 19 May 2014, at 03:21, mikerod wrote:
>
> I'm not sure how any of this relates to the Drools v6.x family.
CompositeClassLoader is all gone, so I don’t think this issue will exist in
6.x. Would be good if you could verify with beta3:
http://downloads.jboss.org/drools/release/6.1.0.Beta3/
W
I was finally able to take some time and find out where multiple threads
could be showing up
in the environment where my application was not doing any multithreaded work
with the Drools
knowledge base or session.
One example I have can be seen by looking at the
`org.drools.rule.constraint.MvelCons
We are also experiencing the same problems using 5.x and it is causing us
big problems.
I haven't had time to try it yet but do any developers know whether we
would be safe to change the HashMap the CompositiveClassLoader is using to
a ConcurrentHashMap?
thanks
Steve
Does anyone have any thoughts on this issue?
I still haven't been able to get to the root of the concurrency issue.
Digging through some of the Drools implementations, but no luck. :)
--
View this message in context:
http://drools.46999.n3.nabble.com/CompositiveClassLoader-CachingLoader-load
I cannot easily reproduce an issue that I'm seeing. This is an intermittent
issue that happens probably 3% of the time or less.
This is observed behavior in
* Drools v5.6.0.Final, using
* Janino compiler v2.5.16 && transitively Drools brings
* mvel2 v2.1.8.Final
We have an environment that loads
