3:42 a.m.
Hi All,
We are using Drools-core 5.2.0.M2 version and we are facing issue while
inserting facts within
StatefulKnowledge session we insert around 50 facts in single request. We
have 10 threads concurrently requesting for fireAllRules. We are using mvel
dialect and our threads are getting blocked over class.forName
Below is the thread dump
java.lang.Thread.State: BLOCKED (on object monitor) at
java.lang.Class.forName0(Native Method) at
java.lang.Class.forName(Class.java:247) at
org.mvel2.ParserConfiguration.checkForDynamicImport(ParserConfiguration.java:110)
at
org.mvel2.ParserConfiguration.hasImport(ParserConfiguration.java:140)
at org.mvel2.ParserContext.hasImport(ParserContext.java:343) at
org.mvel2.compiler.AbstractParser.createPropertyToken(AbstractParser.java:1308)
at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:830)
at
org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:132)
at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2097)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:900)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:338)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140)
at org.mvel2.ast.ASTNode.optimize(ASTNode.java:158) at
org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115) at
org.mvel2.ast.Or.getReducedValueAccelerated(Or.java:31) at
org.mvel2.ast.Or.getReducedValueAccelerated(Or.java:31) at
org.mvel2.MVELRuntime.execute(MVELRuntime.java:87) at
org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:125)
at org.mvel2.MVEL.executeExpression(MVEL.java:954) at
org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:97)
at
org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:291)
at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:134) at
org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:450)
at
org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:378)
at
org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:360)
at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:138) at
org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59)
at
org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:185)
at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:143)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:332)
at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:293)
at
org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905)
at
org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:864)
at
org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:251)
at
Please advise if this is a known issues in MVEL 2?
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.
2:04 a.m.
Hi All,
Has anyone faced similar issues ??. Please advise
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.
4:20 a.m.
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.
6:30 a.m.
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
9:40 a.m.
You mention ... "We have 10 threads concurrently requesting for fireAllRules"
Are all these threads using the KnowledgeSession? It might not be thread
safe. Different threads may use, but maybe not concurrently. The API doc
doesnt mention, it that is what I suspect.
--
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.
3:11 a.m.
Hi,
We are creating different StatefulKnowledge Session for different threads
all this StatefulKnowledgeSession are created from same KnowledgeBase,
KnowledgePackage. Is this an issue ? You are correct the API doesnt tells if
StatefuleKnowledgeSession is not thread safe. If I use
StatelessKnowledgeSession will it resolve the issue ?
But as per my knowledge internally StatelessKnowledgeSession uses
StatefuleKnowledgeSession.
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.
3:20 a.m.
SatefulKnowledgeSesssion is thread safe - it just uses a big lock on the session, so only
one thread can interact with it at any one time.
We will need to see your problem to be able to assist. The sample rules, and how you are
bootstrapping and using these 10 threads.
As per previous request, can you submit a self contained unit test as a pull request, that
we can run. If we don't get this we cannot assist you further.
Mark
On 2 Sep 2013, at 09:11, lalit2583 <lalit2583(a)gmail.com> wrote:
Hi,
We are creating different StatefulKnowledge Session for different threads
all this StatefulKnowledgeSession are created from same KnowledgeBase,
KnowledgePackage. Is this an issue ? You are correct the API doesnt tells if
StatefuleKnowledgeSession is not thread safe. If I use
StatelessKnowledgeSession will it resolve the issue ?
But as per my knowledge internally StatelessKnowledgeSession uses
StatefuleKnowledgeSession.
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
3:21 a.m.
On 02/09/2013, lalit2583 <lalit2583(a)gmail.com> wrote:
Hi,
We are creating different StatefulKnowledge Session for different threads
all this StatefulKnowledgeSession are created from same KnowledgeBase,
KnowledgePackage. Is this an issue ?
It should not cause a problem. Synchronisation among user objects
(facts, globals) is user's burden.
You are correct the API doesnt tells
if
StatefuleKnowledgeSession is not thread safe. If I use
StatelessKnowledgeSession will it resolve the issue ?
Possibly: a Stateless KS is discarded after an execute, so you might appear
to avoid running into whatever caused your problem, but without
removing the cause.
But as per my knowledge internally StatelessKnowledgeSession uses
StatefuleKnowledgeSession.
That's what the documentation says.
-W
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
4085
days inactive
4097
days old
7 comments
4 participants
participants (4)
-
lalit2583 -
Mark Proctor -
maunakea -
Wolfgang Laun