May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10457) Upgrade WildFly Transaction Client to 1.0.4.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10457?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-10457: ------------------------------ Fix Version/s: 13.0.0.CR1 > Upgrade WildFly Transaction Client to 1.0.4.Final > ------------------------------------------------- > > Key: WFLY-10457 > URL: https://issues.jboss.org/browse/WFLY-10457 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 13.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10453) NPE on EJB txn recover request

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10453?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-10453. ------------------------------- Fix Version/s: 13.0.0.CR1 Resolution: Done > NPE on EJB txn recover request > ------------------------------ > > Key: WFLY-10453 > URL: https://issues.jboss.org/browse/WFLY-10453 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Blocker > Fix For: 13.0.0.CR1 > > > An NPE can occur during transaction recovery requests from the EJB protocol (and possibly other places as well). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3895) module.path of embedded server cannot be modified after it is set

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3895?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFCORE-3895: ------------------------------------- [~jamezp] this regression happened with WFCORE-3205 since 5.0.0.Beta1. This is a regression against WildFly 12 and this should be fixed before WildFly 13 is released > module.path of embedded server cannot be modified after it is set > ----------------------------------------------------------------- > > Key: WFCORE-3895 > URL: https://issues.jboss.org/browse/WFCORE-3895 > Project: WildFly Core > Issue Type: Bug > Components: Embedded > Affects Versions: 5.0.0.Beta5 > Reporter: Erich Duda > Assignee: James Perkins > Priority: Blocker > > *Scenario:* > * Run CLI in non-modular class loading mode. > * Run embed-server with {{--jboss-home}} pointing to server A > * Stop embed-server > * Remove server A > * Run embed-server with {{--jboss-home}} pointing to server B > *Expectation:* embed-server with {{--jboss-home}} pointing to server B will boot. > *Reality*: The following error message is thrown. As you can see the embed server tries to load modules from server A directory even if the jboss-home was set to server B. > {code} > Cannot start embedded server: The first directory of the specified module path /home/eduda/Projects/wildfly/dist/target/wildfly-A/modules is invalid or does not exist. > {code} > *Users impact:* Behavior of non-modular class loading \[1\] has changed. This change can break user's automation or tests. > *Blocker priority* was chosen because this is change in behavior against Wildfly 12. > *Technical details* > When the embed-server is started for the second time, following warning is logged. > {code} > 2018-05-28 08:10:57,621 WARN [org.jboss.as.embedded] (main) WFLYEMB0145: The module loader has already been configured. Changing the module.path property will have no effect > {code} > It seems that the change in behavior was caused by commit \[2\]. > \[1\] http://wildfly.org/news/2015/03/13/Offline-CLI/#classloading > \[2\] https://github.com/wildfly/wildfly-core/commit/22f3956f1adcdf8b1cb11e24f2... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3885) XNIO prints WARNING with JDK10+ if CLI connects to server

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3885?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3885: ------------------------------- Labels: blocker-WF14 (was: ) > XNIO prints WARNING with JDK10+ if CLI connects to server > --------------------------------------------------------- > > Key: WFCORE-3885 > URL: https://issues.jboss.org/browse/WFCORE-3885 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Scripts > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Priority: Blocker > Labels: blocker-WF14 > > CLI prints WARNING with JDK10+ if CLI connects to server > {noformat} > [mkopecky@dhcp-10-40-5-52 bin]$ java -version > java version "10" 2018-03-20 > Java(TM) SE Runtime Environment 18.3 (build 10+46) > Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode) > [mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh "echo test" > test > [mkopecky@dhcp-10-40-5-52 bin]$ ./jboss-cli.sh -c "echo test" > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/eap/7.2.0.CD13.1/jboss-eap-7.2/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.3.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider() > WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2 > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > test > [mkopecky@dhcp-10-40-5-52 bin]$ > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2592) PMML - tests in class ScorecardReasonCodeTest fail randomly

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2592?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2592: ---------------------------------- Description: When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove, testReasonCodesCombination and probably others (I tested those 3 mentioned). [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 was: When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove, testReasonCodesCombination and probably others (I tested just those 3 mentioned). [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 > PMML - tests in class ScorecardReasonCodeTest fail randomly > ----------------------------------------------------------- > > Key: DROOLS-2592 > URL: https://issues.jboss.org/browse/DROOLS-2592 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > Priority: Critical > > When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove, testReasonCodesCombination and probably others (I tested those 3 mentioned). > [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2592) PMML - tests in class ScorecardReasonCodeTest fail randomly

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2592?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2592: ---------------------------------- Description: When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove, testReasonCodesCombination and probably others (I tested just those 3 mentioned). [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 was: When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove. [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 > PMML - tests in class ScorecardReasonCodeTest fail randomly > ----------------------------------------------------------- > > Key: DROOLS-2592 > URL: https://issues.jboss.org/browse/DROOLS-2592 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > Priority: Critical > > When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove, testReasonCodesCombination and probably others (I tested just those 3 mentioned). > [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2592) PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2592?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2592: ---------------------------------- Tester: Jiri Petrlik > PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly > --------------------------------------------------------------------------------- > > Key: DROOLS-2592 > URL: https://issues.jboss.org/browse/DROOLS-2592 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > Priority: Critical > > When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove. > [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2592) PMML - tests in class ScorecardReasonCodeTest fail randomly

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2592?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2592: ---------------------------------- Summary: PMML - tests in class ScorecardReasonCodeTest fail randomly (was: PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly) > PMML - tests in class ScorecardReasonCodeTest fail randomly > ----------------------------------------------------------- > > Key: DROOLS-2592 > URL: https://issues.jboss.org/browse/DROOLS-2592 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > Priority: Critical > > When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove. > [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2592) PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2592?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2592: ---------------------------------- Summary: PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly (was: PMML - ScorecardReasonCodeTest.testPointsBelow fails randomly) > PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly > --------------------------------------------------------------------------------- > > Key: DROOLS-2592 > URL: https://issues.jboss.org/browse/DROOLS-2592 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > Priority: Critical > > When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. > [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2592) PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2592?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2592: ---------------------------------- Description: When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove. [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 was: When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 > PMML - ScorecardReasonCodeTest.testPointsBelow and testPointsAbove fails randomly > --------------------------------------------------------------------------------- > > Key: DROOLS-2592 > URL: https://issues.jboss.org/browse/DROOLS-2592 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Lance Leverich > Priority: Critical > > When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove. > [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2018