This is happening in a MVELPredicate, i.e. an eval. The ASM based JIT we do is not used
for predicates (I think, @mario will confirm), so it will use stock MVEL. MVEL is
defaulted to work in reflection mode, hence the reflection optimizer. It has an ASM
optimiser, but there were issues with that, so we hard coded it to safe reflective mode.
So right now there isn't much you can do.
I'd recommend you create a minimal unit test, that demonstrates the issue with
assertions (so that it clearly identifies the issue, and tracks regressions), and submit
it as a pull request. Please make sure you do this against 6.x
http://docs.jboss.org/drools/release/5.5.0.Final/droolsjbpm-introduction-...
Mark
On 1 Sep 2013, at 10:20, lalit2583 <lalit2583(a)gmail.com> wrote:
Hi Team,
We are facing this issue even with Drools 5.5. Does drools compiled or
interpreted mvel expression ?
Should we disable mvel JIT compiler to solve this issue ??
Regards,
Lalit.
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Concurrent-Execution-causes-Bloc...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users