[
https://issues.jboss.org/browse/DROOLS-1717?page=com.atlassian.jira.plugi...
]
Mario Fusco commented on DROOLS-1717:
-------------------------------------
[~tzimanyi] I think I fixed the problem in mvel with this commit
https://github.com/mvel/mvel/commit/061ce2dab4e3ce4bdc8bca67873f9e09e985adc2
I let your reproducer running for more than 10K times and couldn't reproduce this
issue anymore. Please confirm that this is ok also for you and I'll drop another
stable release of mvel asap.
Concurrency problems with enum constraints in MVEL
--------------------------------------------------
Key: DROOLS-1717
URL:
https://issues.jboss.org/browse/DROOLS-1717
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.2.0.Final
Reporter: Tibor Zimányi
Assignee: Mario Fusco
Labels: concurrency
Having a test case like this [1], it sometimes fails on
java.lang.RuntimeException: java.util.concurrent.ExecutionException: [Error: unable to
resolve method using strict-mode:
org.drools.compiler.integrationtests.facts.FactWithEnum.AnEnum()]
[Near : {... enumValue == AnEnum.SECOND ....}]
... see here [2]. When using direct imports that are commented out in the pasted example,
I see very rarely also a ClassCastException. See stacktrace here [3].
Tested with mvel 2.2.8 on 6.5.x branch, 2.3.0 and 2.3.1 on master branch.
[1]
https://gist.github.com/baldimir/d0f5f21d5b1a383887c5ebfb6013e5af
[2]
https://gist.github.com/baldimir/da5c9cb23fab2eae1576948c8ca2a4c8
[3]
https://gist.github.com/baldimir/72eafe3909c21e25265cd3ee9a731d8e
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)