December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5872) DrlDumper generates wrong drl when AccumulateDescr does not have constraint

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5872?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5872: -------------------------------- Sprint: 2020 Week 49-51 (from Nov 30) > DrlDumper generates wrong drl when AccumulateDescr does not have constraint > --------------------------------------------------------------------------- > > Key: DROOLS-5872 > URL: https://issues.redhat.com/browse/DROOLS-5872 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.44.0.Final, 7.46.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: accumulate-without-constraint-test.zip > > > When AccumulateDescr does not have constraint, generated DRL can not be built. > Here is an example code. > {code:java} > PackageDescr packageDescr = DescrFactory.newPackage().name("example") > .newImport().target("java.math.BigDecimal").end() > .newRule().name("Test Rule") > .lhs() > .accumulate() > .source().pattern().type("example.RuleTest.Fact").id("$target", false) > .end() > .end() > .function("count", "$cnt", false) > // adding the following constraint can avoid from KieBase build error > // .constraint("true") > .end() > .end() > .rhs("System.out.println($cnt);") > .end() > .end().getDescr(); > String drl = new DrlDumper().dump(packageDescr); > {code} > This dumps the following DRL. > {code:java} > package example > import java.math.BigDecimal > rule "Test Rule" > when > accumulate( > $target : example.RuleTest.Fact( ) , > $cnt : count( ) ; > ) > then > System.out.println($cnt); > end > {code} > KieBase build with above drl fails with the following error. > {noformat} > 2020-12-02 15:05:47,875 ERROR [org.drools.compiler.kie.builder.impl.KieProject] (main) Unable to build KieBaseModel:defaultKieBase > [10,9]: [ERR 101] Line 10:9 no viable alternative at input ')' in rule "Test Rule" > [0,0]: Parser returned a null Package > {noformat} > Adding constraint like comment line in above code can avoid from build error. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14025) Unable to remove the default datasource binding from the ee subsystem

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-14025?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-14025: --------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13744 (was: https://github.com/wildfly/wildfly/pull/13738) > Unable to remove the default datasource binding from the ee subsystem > --------------------------------------------------------------------- > > Key: WFLY-14025 > URL: https://issues.redhat.com/browse/WFLY-14025 > Project: WildFly > Issue Type: Bug > Components: EE, JCA > Reporter: Lin Gao > Assignee: Tomasz Adamski > Priority: Major > Labels: Regression, downstream_dependency > Attachments: reproducer-spring.war, reproducer-spring2.war, reproducer2.war, standalone.xml > > > EAP 7.2+ is creating a dependency on the DefaultDataSource when it should not. > If the default datasource is removed from the ee subsystem and an application is deployed with a class that has @Resource specifying a name to inject which is not linked to the default datasource, it should NOT fail with a missing dependency. > This was found with a Spring application, where Spring configuration is defining java:comp/env/dataSource to link to the real datasource. In EAP 7.1 the application deployed with no issue, in EAP 7.2+ JBoss is failing the deployment due to the datasource=... being removed from the default bindings in the ee subsystem. > > {code:java} > @Resource(name = "dataSource") > private DataSource dataSource; {code} > > {code:java} > 18:08:15,547 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "reproducer2.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.reproducer2.reproducer2.DefaultDataSource"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.reproducer2.reproducer2.env.non-existant is missing [jboss.naming.context.java.module.reproducer2.reproducer2.DefaultDataSource]"] > }{code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14090) Use shared test utilities for log handling in NetworkHealthTestCase

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFLY-14090?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Smietanko reassigned WFLY-14090: ----------------------------------------------- Assignee: Bartosz Spyrko-Smietanko > Use shared test utilities for log handling in NetworkHealthTestCase > ------------------------------------------------------------------- > > Key: WFLY-14090 > URL: https://issues.redhat.com/browse/WFLY-14090 > Project: WildFly > Issue Type: Task > Components: JMS, Test Suite > Reporter: Brian Stansberry > Assignee: Bartosz Spyrko-Smietanko > Priority: Minor > > NetworkHealthTestCase has hand written code for finding the server log file and reading the potentially thousands of lines in it to look for a few recently written lines. > In wildfly-testsuite-shared there are utilities for this kind of thing that can be used. See LoggingUtil and TestLogHandlerSetupTask. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5201) Update commons-io to 2.8.0

by Boris Unckel (Jira)

Boris Unckel created WFCORE-5201: ------------------------------------ Summary: Update commons-io to 2.8.0 Key: WFCORE-5201 URL: https://issues.redhat.com/browse/WFCORE-5201 Project: WildFly Core Issue Type: Component Upgrade Components: Modules Affects Versions: 14.0.0.Beta2 Reporter: Boris Unckel Assignee: Richard Opalka Update to [commons-io 2.8.0|https://mvnrepository.com/artifact/commons-io/commons-io/2.8.0] [Release Notes|https://commons.apache.org/proper/commons-io/changes-report.html#a2...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14137) Typo in JWT_CAPABILITY_NAME

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14137: --------------------------------------- Summary: Typo in JWT_CAPABILITY_NAME Key: WFLY-14137 URL: https://issues.redhat.com/browse/WFLY-14137 Project: WildFly Issue Type: Bug Components: MP JWT Reporter: Brian Stansberry Assignee: Darran Lofthouse static final String JWT_CAPABILITY_NAME = "org.wildlfly.microprofile.jwt"; The 'wildfly' has an extra 'l'. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5876) [Test Scenario Editor] Display actual test results instead of a generic message

by Yeser Amer (Jira)

Yeser Amer created DROOLS-5876: ---------------------------------- Summary: [Test Scenario Editor] Display actual test results instead of a generic message Key: DROOLS-5876 URL: https://issues.redhat.com/browse/DROOLS-5876 Project: Drools Issue Type: Enhancement Reporter: Yeser Amer Assignee: Yeser Amer -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14094) Potential memory leak when using opentracing

by Roland Spindelbalker-Davila (Jira)

[ https://issues.redhat.com/browse/WFLY-14094?page=com.atlassian.jira.plugi... ] Roland Spindelbalker-Davila commented on WFLY-14094: ---------------------------------------------------- Are you planning to create bugfix releases for the other affected versions of WildFly as well? Or will this bug only be fixed in WildFly 22? > Potential memory leak when using opentracing > -------------------------------------------- > > Key: WFLY-14094 > URL: https://issues.redhat.com/browse/WFLY-14094 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, MP OpenTracing > Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final > Reporter: Michel Erard > Assignee: Matěj Novotný > Priority: Major > Labels: downstream_dependency > Fix For: 22.0.0.Beta1 > > Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png > > > Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak. > Here I did a little sample project to simulate the issue: > [https://github.com/erard22/wildfly-memory-leak] > Requests handeled by this class > {code:java} > @ApplicationScoped > @Traced > public class HelloWorldService { > public String sayHello() { > return "Hello World!"; > } > } {code} > leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap. > !bad_heapdump.png! > Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14152) Upgrade smallrye-fault-tolerance to 4.3.2

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-14152: ------------------------------------- Summary: Upgrade smallrye-fault-tolerance to 4.3.2 Key: WFLY-14152 URL: https://issues.redhat.com/browse/WFLY-14152 Project: WildFly Issue Type: Component Upgrade Components: MP Fault Tolerance Affects Versions: 21.0.0.Beta1, 21.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 22.0.0.Alpha1 Brings in new API module. Release notes: https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/4.3.1 Changes: https://github.com/smallrye/smallrye-fault-tolerance/compare/4.3.0...4.3.1 Notable changes: Fixes: https://github.com/smallrye/smallrye-fault-tolerance/commit/0e85a1ee4c689... https://github.com/smallrye/smallrye-fault-tolerance/commit/28b2c26fc031a... Improvements: https://github.com/smallrye/smallrye-fault-tolerance/commit/af4ca42825c79... https://github.com/smallrye/smallrye-fault-tolerance/commit/4b5081ba807ea... "Breaking changes" https://github.com/smallrye/smallrye-fault-tolerance/commit/e195d42b01f60... - this now requires a new module and new module dependency on 'smallrye-metrics-api' Deprecations: https://github.com/smallrye/smallrye-fault-tolerance/commit/b03f9d90d22b0... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14152) Upgrade smallrye-fault-tolerance to 4.3.2

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-14152?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-14152: ---------------------------------- Description: Release notes: https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/4.3.2 Changes: https://github.com/smallrye/smallrye-fault-tolerance/compare/4.3.1...4.3.2 No notable changes. was: Brings in new API module. Release notes: https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/4.3.2 Changes: https://github.com/smallrye/smallrye-fault-tolerance/compare/4.3.1...4.3.2 No notable changes. > Upgrade smallrye-fault-tolerance to 4.3.2 > ----------------------------------------- > > Key: WFLY-14152 > URL: https://issues.redhat.com/browse/WFLY-14152 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Fault Tolerance > Affects Versions: 21.0.0.Beta1, 21.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 22.0.0.Alpha1 > > > Release notes: > https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/4.3.2 > Changes: > https://github.com/smallrye/smallrye-fault-tolerance/compare/4.3.1...4.3.2 > No notable changes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14094) Potential memory leak when using opentracing

by Roland Spindelbalker-Davila (Jira)

[ https://issues.redhat.com/browse/WFLY-14094?page=com.atlassian.jira.plugi... ] Roland Spindelbalker-Davila edited comment on WFLY-14094 at 12/1/20 5:47 AM: ----------------------------------------------------------------------------- Are you planning to create bugfix releases for the other affected versions of WildFly as well, or will this bug only be fixed in WildFly 22? was (Author: roland.spindelbalker-davila): Are you planning to create bugfix releases for the other affected versions of WildFly as well? Or will this bug only be fixed in WildFly 22? > Potential memory leak when using opentracing > -------------------------------------------- > > Key: WFLY-14094 > URL: https://issues.redhat.com/browse/WFLY-14094 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, MP OpenTracing > Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final > Reporter: Michel Erard > Assignee: Matěj Novotný > Priority: Major > Labels: downstream_dependency > Fix For: 22.0.0.Beta1 > > Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png > > > Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak. > Here I did a little sample project to simulate the issue: > [https://github.com/erard22/wildfly-memory-leak] > Requests handeled by this class > {code:java} > @ApplicationScoped > @Traced > public class HelloWorldService { > public String sayHello() { > return "Hello World!"; > } > } {code} > leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap. > !bad_heapdump.png! > Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 4 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 December 2020