June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5458) Project broken after test scenario run with possibly a class-loading issue

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5458?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5458: --------------------------------- Sprint: 2020 Week 25-27 (from Jun 15) > Project broken after test scenario run with possibly a class-loading issue > -------------------------------------------------------------------------- > > Key: DROOLS-5458 > URL: https://issues.redhat.com/browse/DROOLS-5458 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Jan Stastny > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: bpms_scesim-tickets.zip > > > For a Scenario Simulation that tests DRL rule and facts having an enum property a seemingly class-loading issue occurs in Business Central. > The ultimate error is in the DRL file validation: > {code:java|title=DRL file} > package org.jboss.qa.ba.scesim; > rule "child ticket" > when > t: Ticket ( type==TicketType.CHILD) > then > t.setPrice(5.0); > end > {code} > {code:java|title=Validation error} > [KBase: defaultKieBase]: Unable to Analyse Expression type == TicketType.CHILD: > [Error: Comparison operation requires compatible types. Found class org.jboss.qa.ba.scesim.TicketType and class org.jboss.qa.ba.scesim.TicketType] > [Near : {... type == TicketType.CHILD ....}] > ^ > {code} > The issue happens in given scenario: > # import project > # go to DRL file and run validation - succeeds > # go to scenario simulation and run - succeeds > # go back to DRL file and run validation - fails with the error above > # go to scenario simulation and run again - fails due to the rule not being evaluated for given facts > The issue disappears when running Build of the project in the Project perspective. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5458) Project broken after test scenario run with possibly a class-loading issue

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5458?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-5458: ------------------------------------ Assignee: Toni Rikkola (was: Yeser Amer) > Project broken after test scenario run with possibly a class-loading issue > -------------------------------------------------------------------------- > > Key: DROOLS-5458 > URL: https://issues.redhat.com/browse/DROOLS-5458 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Jan Stastny > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: bpms_scesim-tickets.zip > > > For a Scenario Simulation that tests DRL rule and facts having an enum property a seemingly class-loading issue occurs in Business Central. > The ultimate error is in the DRL file validation: > {code:java|title=DRL file} > package org.jboss.qa.ba.scesim; > rule "child ticket" > when > t: Ticket ( type==TicketType.CHILD) > then > t.setPrice(5.0); > end > {code} > {code:java|title=Validation error} > [KBase: defaultKieBase]: Unable to Analyse Expression type == TicketType.CHILD: > [Error: Comparison operation requires compatible types. Found class org.jboss.qa.ba.scesim.TicketType and class org.jboss.qa.ba.scesim.TicketType] > [Near : {... type == TicketType.CHILD ....}] > ^ > {code} > The issue happens in given scenario: > # import project > # go to DRL file and run validation - succeeds > # go to scenario simulation and run - succeeds > # go back to DRL file and run validation - fails with the error above > # go to scenario simulation and run again - fails due to the rule not being evaluated for given facts > The issue disappears when running Build of the project in the Project perspective. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1994: --------------------------------------- For anyone who does pick this up next, the JaasSecurityRealm Sonia identifies is probably the most important as this becomes a part of our supported implementation. We presently compile on Java 11 but when available we may want to jump to Java 17. I have heard mention that when compiling to an older version the older APIs may still be available to compile against (this may be something we have to add to the build) so we may still be able to produce a jar compatible with Java 8 / 11. For Java 14 and later we likely have two options to consider: # Use a multi version jar to make unsupported from Java 14 and onwards. # Provide an alternative implementation from Java 14 that does not rely on the API which is removed from that point. > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Gabriele Cardosi commented on DROOLS-5451: ------------------------------------------ [~dmarrazzo] [~jomarko] Not completely sure about the version of the PMML {code:java} <PMML xmlns="http://www.dmg.org/PMML-4_4" xmlns:data="http://jpmml.org/jpmml-model/InlineTable" -->version="4.3" <--- >{code} This is the expected tag (from referenced spec) {code:java} <PMML version="4.4" xmlns="http://www.dmg.org/PMML-4_4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">{code} Anyway, to verify effect of this PR(s) should be enough to replace xmlns and version attributes from previous PMMLs > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5451. ------------------------------------ > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5449) ClassCastException upon unreferenced declare update

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-5449?page=com.atlassian.jira.plug... ] Matteo Casalino commented on DROOLS-5449: ----------------------------------------- yes we noticed this. Still I thought this would be worth reporting because the fact that it is only reproducible when iterating fireAllRules many times may hide some race condition. > ClassCastException upon unreferenced declare update > --------------------------------------------------- > > Key: DROOLS-5449 > URL: https://issues.redhat.com/browse/DROOLS-5449 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: class-cast-exception-on-unreferenced-declare-update.zip > > > After updating a declared type that is not referenced in the rules with _updateToVersion()_, > running _fireAllRules()_ many times in a loop throws _ClassCastException_. > E.g., when the following DRL: > {noformat} > declare UnreferencedType > x : int > end > declare ReferencedType > str : String > end > > rule "example rule" > when > ReferencedType( str == "A" ) > then > end{noformat} > is updated to: > {noformat} > declare UnreferencedType > x : int > newField : String > end > declare ReferencedType > str : String > end > > rule "example rule" > when > ReferencedType( str == "A" ) > then > end{noformat} > the following exception it thrown by _fireAllRules()_: > {noformat} > java.lang.RuntimeException: Error evaluating constraint 'str == "A"' in [Rule "example rule" in org/example/rules.drl] > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:277) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:225) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:139) > ... > Caused by: java.lang.ClassCastException: class org.example.ReferencedType cannot be cast to class org.example.ReferencedType (org.example.ReferencedType is in unnamed module of loader org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader @46292372; org.example.ReferencedType is in unnamed module of loader org.drools.dynamic.DynamicProjectClassLoader$DefaultInternalTypesClassLoader @23b8d9f3) > at ConditionEvaluator7ed8b2c57cad4e74b856fdba30554aa1.evaluate(Unknown Source) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:275) > ... 43 more{noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-5451: ------------------------------------- [~dmarrazzo] thank you. > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12778) EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-12778?page=com.atlassian.jira.plugi... ] Parul Sharma updated WFLY-12778: -------------------------------- Comment: was deleted (was: Thanks [~spyrkob], If you don't mind can I look into this issue?) > EAR deployed on colocated master/slave servers does not wait for the embedded JMS services to startup properly > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12778 > URL: https://issues.redhat.com/browse/WFLY-12778 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Spyrko-Smietanko > Assignee: Bartosz Spyrko-Smietanko > Priority: Major > > When an EAR containing MDBS is deployed in one of the colocated master/slave servers, the application does not wait for the embedded broker to start up and generates these errors in the logs: > {code:java} > /14:48:11,134 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "EJB_MDBEAR.ear")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => [ > "jboss.ra.activemq-ra", > "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory" > ], > {code} > When the broker is eventually started, these MDBs get deployed and start working fine without any redeployment but these errors are not desirable in the logs. > Defining the resource-ref in ejb-jar.xml or annotating with @Resource does not help either. > The application should wait for its dependencies to be available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13621) GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-13621?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos closed WFLY-13621. ------------------------------------------ This is done ... > GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT > ------------------------------------------------------------- > > Key: WFLY-13621 > URL: https://issues.redhat.com/browse/WFLY-13621 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Loukas Kopanias > Priority: Major > > This is a task of Loukas Kopanias for the 1st Phase of GSoC 2020. > All testcases and configuration files in EAT updated to run successfully on the latest released version of Wildfly (currently 20.0.0.Final). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13621) GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-13621?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos commented on WFLY-13621: ------------------------------------------------ This is done. Thank you Louka. Closing the issue ... > GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT > ------------------------------------------------------------- > > Key: WFLY-13621 > URL: https://issues.redhat.com/browse/WFLY-13621 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Loukas Kopanias > Priority: Major > > This is a task of Loukas Kopanias for the 1st Phase of GSoC 2020. > All testcases and configuration files in EAT updated to run successfully on the latest released version of Wildfly (currently 20.0.0.Final). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020