[Red Hat JIRA] (DROOLS-5957) drools-workbench-models unused dependencies
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5957:
-----------------------------------
Summary: drools-workbench-models unused dependencies
Key: DROOLS-5957
URL: https://issues.redhat.com/browse/DROOLS-5957
Project: Drools
Issue Type: Task
Components: Guided Decision Table Editor, Guided Template Editor
Affects Versions: 7.49.0.Final
Reporter: Jozef Marko
Assignee: Jozef Marko
Using {{mvn dependency:analyze}} two unused compile dependencies were found during DROOLS-5892 review.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14271) NullPointerException when ejb timers services fails during loading timer from database upon activation
by Enrique González Martínez (Jira)
[ https://issues.redhat.com/browse/WFLY-14271?page=com.atlassian.jira.plugi... ]
Enrique González Martínez updated WFLY-14271:
---------------------------------------------
Description:
NullPointerException when ejb timers services fails during loading timer from database upon activation.
This causes the timerObjectId set not being created and failing afterwards.
{noformat}
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:632)
at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createTimer(TimerServiceImpl.java:480)
at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createSingleActionTimer(TimerServiceImpl.java:305)
at deployment.ROOT.war//org.jbpm.services.ejb.timer.EJBTimerScheduler.internalSchedule(EJBTimerScheduler.java:202)
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.addTimer(DatabaseTimerPersistence.java:337)
at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:613)
{noformat}
was:
NullPointerException when ejb timers services fails during loading timer from database upon activation.
This causes the timerObjectId set not being created and failing afterwards.
> NullPointerException when ejb timers services fails during loading timer from database upon activation
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-14271
> URL: https://issues.redhat.com/browse/WFLY-14271
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Enrique González Martínez
> Assignee: Enrique González Martínez
> Priority: Major
> Fix For: 22.0.0.Final
>
>
> NullPointerException when ejb timers services fails during loading timer from database upon activation.
> This causes the timerObjectId set not being created and failing afterwards.
> {noformat}
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:632)
> at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createTimer(TimerServiceImpl.java:480)
> at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createSingleActionTimer(TimerServiceImpl.java:305)
> at deployment.ROOT.war//org.jbpm.services.ejb.timer.EJBTimerScheduler.internalSchedule(EJBTimerScheduler.java:202)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.addTimer(DatabaseTimerPersistence.java:337)
> at org.jboss.as.ejb3@7.2.9.GA-redhat-00003//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:613)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14310) JPASubsystemAdd uses non-standard attribute value resolution
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14310?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-14310:
------------------------------------
Description:
JPASubsystemAdd processes a couple attributes in non-standard ways, not using AttributeDefinition.resolveModelAttribute. The code handles the primary things resolveModelAttribute handles (default values and basic expression resolution) but it doesn't handle the full set of expression resolution capability WildFly supports.
The code also uses ModelNode.require to read the default-datasource attribute, which has the effect of forcing callers to set that attribute even though the resource description says it is optional and the runtime code can deal with a null value. To workaround this our standard config xml files are setting the xml attribute to the empty string which is unintuitive and shouldn't be needed.
was:JPASubsystemAdd processes a couple attributes in non-standard ways, not using AttributeDefinition.resolveModelAttribute. The code handles the primary things resolveModelAttribute handles (default values and basic expression resolution) but it doesn't handle the full set of expression resolution capability WildFly supports.
> JPASubsystemAdd uses non-standard attribute value resolution
> ------------------------------------------------------------
>
> Key: WFLY-14310
> URL: https://issues.redhat.com/browse/WFLY-14310
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> JPASubsystemAdd processes a couple attributes in non-standard ways, not using AttributeDefinition.resolveModelAttribute. The code handles the primary things resolveModelAttribute handles (default values and basic expression resolution) but it doesn't handle the full set of expression resolution capability WildFly supports.
> The code also uses ModelNode.require to read the default-datasource attribute, which has the effect of forcing callers to set that attribute even though the resource description says it is optional and the runtime code can deal with a null value. To workaround this our standard config xml files are setting the xml attribute to the empty string which is unintuitive and shouldn't be needed.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5956) Illegal reflective access
by Damon Horrell (Jira)
Damon Horrell created DROOLS-5956:
-------------------------------------
Summary: Illegal reflective access
Key: DROOLS-5956
URL: https://issues.redhat.com/browse/DROOLS-5956
Project: Drools
Issue Type: Bug
Affects Versions: 7.48.0.Final
Reporter: Damon Horrell
Assignee: Mario Fusco
Using Java 11, Drools MVEL is reporting an Illegal reflective access warning:
{{WARNING: Illegal reflective access by org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer (file:/Users/damon/.m2/repository/org/drools/drools-mvel/7.48.0.Final/drools-mvel-7.48.0.Final.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)}}{{at org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer.createDefineMethod(ClassGenerator.java:126)}}{{at org.drools.mvel.asm.ClassGenerator$DefineMethodInitializer.<clinit>(ClassGenerator.java:117)}}{{at org.drools.mvel.asm.ClassGenerator.generateClass(ClassGenerator.java:177)}}{{at org.drools.mvel.asm.ClassGenerator.newInstance(ClassGenerator.java:214)}}{{at org.drools.mvel.asm.ConsequenceGenerator.generate(ConsequenceGenerator.java:140)}}{{at defaultpkg.Rule_Expand_HealthCase181668088DefaultConsequenceInvoker.evaluate(Unknown Source)}}{{at org.drools.core.phreak.RuleExecutor.innerFireActivation(RuleExecutor.java:434)}}{{at org.drools.core.phreak.RuleExecutor.fireActivation(RuleExecutor.java:382)}}{{at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:138)}}{{at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:90)}}{{at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:33)}}{{at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)}}{{at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1111)}}{{at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1058)}}{{at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1050)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1346)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1337)}}{{at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1321)}}
{{Is there a plan to update this code to avoid the warning (which will become an error in some future version of Java)?}}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Description:
KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
This was using 7.48.Final drools libraries and Business Central 7.48.Final but experienced similar issue before on 7.43.1.Final as well.
I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
My dependencies in maven for RunTest.java were:
* group: org.drools artifact: drools-bom ,version: 7.48.Final
* group: org.kie artifact: kie-ci
* group: org.drools artifact: drools-workbench-models-guided-dtable
* group: org.drools artifact: drools-workbench-models-guided-template
was:
KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
My dependencies in maven for RunTest.java were:
* group: org.drools artifact: drools-bom ,version: 7.48.Final
* group: org.kie artifact: kie-ci
* group: org.drools artifact: drools-workbench-models-guided-dtable
* group: org.drools artifact: drools-workbench-models-guided-template
> KieScanner not properly updating model assets (classes) on incremental updates
> ------------------------------------------------------------------------------
>
> Key: DROOLS-5955
> URL: https://issues.redhat.com/browse/DROOLS-5955
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: B Brown
> Assignee: Mario Fusco
> Priority: Major
> Attachments: LogFile.txt, RunTest.java, TestScannerUpdate-1.0.0-SNAPSHOT.jar
>
>
> KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
> Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
> It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
> This was using 7.48.Final drools libraries and Business Central 7.48.Final but experienced similar issue before on 7.43.1.Final as well.
> I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
>
> My dependencies in maven for RunTest.java were:
> * group: org.drools artifact: drools-bom ,version: 7.48.Final
> * group: org.kie artifact: kie-ci
> * group: org.drools artifact: drools-workbench-models-guided-dtable
> * group: org.drools artifact: drools-workbench-models-guided-template
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Description:
KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
My dependencies in maven for RunTest.java were:
* group: org.drools artifact: drools-bom ,version: 7.48.Final
* group: org.kie artifact: kie-ci
* group: org.drools artifact: drools-workbench-models-guided-dtable
* group: org.drools artifact: drools-workbench-models-guided-template
was:
KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
My dependencies in maven were:
* group: org.drools artifact: drools-bom ,version: 7.48.Final
* group: org.kie artifact: kie-ci
* group: org.drools artifact: drools-workbench-models-guided-dtable
* group: org.drools artifact: drools-workbench-models-guided-template
> KieScanner not properly updating model assets (classes) on incremental updates
> ------------------------------------------------------------------------------
>
> Key: DROOLS-5955
> URL: https://issues.redhat.com/browse/DROOLS-5955
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: B Brown
> Assignee: Mario Fusco
> Priority: Major
> Attachments: LogFile.txt, RunTest.java, TestScannerUpdate-1.0.0-SNAPSHOT.jar
>
>
> KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
> Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
> It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
>
> I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
>
> My dependencies in maven for RunTest.java were:
> * group: org.drools artifact: drools-bom ,version: 7.48.Final
> * group: org.kie artifact: kie-ci
> * group: org.drools artifact: drools-workbench-models-guided-dtable
> * group: org.drools artifact: drools-workbench-models-guided-template
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Description:
KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
My dependencies in maven were:
* group: org.drools artifact: drools-bom ,version: 7.48.Final
* group: org.kie artifact: kie-ci
* group: org.drools artifact: drools-workbench-models-guided-dtable
* group: org.drools artifact: drools-workbench-models-guided-template
was:
KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
> KieScanner not properly updating model assets (classes) on incremental updates
> ------------------------------------------------------------------------------
>
> Key: DROOLS-5955
> URL: https://issues.redhat.com/browse/DROOLS-5955
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: B Brown
> Assignee: Mario Fusco
> Priority: Major
> Attachments: LogFile.txt, RunTest.java, TestScannerUpdate-1.0.0-SNAPSHOT.jar
>
>
> KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
> Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
> It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce".
>
> I've attached the final kjar that caused the error, the RunTest.java containing the main method that ran the test as well as the log file.
>
> My dependencies in maven were:
> * group: org.drools artifact: drools-bom ,version: 7.48.Final
> * group: org.kie artifact: kie-ci
> * group: org.drools artifact: drools-workbench-models-guided-dtable
> * group: org.drools artifact: drools-workbench-models-guided-template
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (DROOLS-5955) KieScanner not properly updating model assets (classes) on incremental updates
by B Brown (Jira)
[ https://issues.redhat.com/browse/DROOLS-5955?page=com.atlassian.jira.plug... ]
B Brown updated DROOLS-5955:
----------------------------
Attachment: RunTest.java
> KieScanner not properly updating model assets (classes) on incremental updates
> ------------------------------------------------------------------------------
>
> Key: DROOLS-5955
> URL: https://issues.redhat.com/browse/DROOLS-5955
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: B Brown
> Assignee: Mario Fusco
> Priority: Major
> Attachments: LogFile.txt, RunTest.java, TestScannerUpdate-1.0.0-SNAPSHOT.jar
>
>
> KieScanner is not correctly applying incremental kjar updates to KieContainer when those updates include changes to "Model" assets authored in Business Central.
> Adding a new field to a model in business central, then updating a rule to reference that value will work the first time. If you repeat this again, adding another new field and new reference in a rule, after updating the KieContainer using KieScanner, executing fireAllRules on a new session will fail with an exception, claiming it cannot find the setter method for the new attribute.
> It is expected that the KieScanner should be able to take new kjars produced from BC and consistently update KieContainers with their updates. There is no workaround for this. Please refer to the "Steps to Reproduce". I've also attached the final kjar that caused the error, the main method that ran the test as well as the log file.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months