June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2575) Executable model - DRL integration tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2575?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2575. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/6e8a8d85cbb5004896adbdd49d41b6a... > Executable model - DRL integration tests fail with the model > ------------------------------------------------------------ > > Key: DROOLS-2575 > URL: https://issues.jboss.org/browse/DROOLS-2575 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When running DRL integration tests [1] with the executable model, 118 out of 510 test cases fail. PR with tests is here [2]. > [1] https://github.com/kiegroup/drools/tree/master/drools-compiler/src/test/j... > [2] https://github.com/kiegroup/drools/pull/1915 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3910) jboss-cli not starting using jre10 (possible regression)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3910?page=com.atlassian.jira.plugi... ] Jean-Francois Denise moved WFLY-10512 to WFCORE-3910: ----------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3910 (was: WFLY-10512) Component/s: CLI (was: CLI) Affects Version/s: (was: 13.0.0.Final) > jboss-cli not starting using jre10 (possible regression) > -------------------------------------------------------- > > Key: WFCORE-3910 > URL: https://issues.jboss.org/browse/WFCORE-3910 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: Java 10.0.1 (oracle server-jdk), Windows 10 > Reporter: Martin Miller > Assignee: Jean-Francois Denise > Priority: Blocker > > Under an environment with a JAVA_HOME to java 10.0.1, > I can start the jboss-cli.ps1 under Wildfly 12, but under Wildfly 13 I get: > org.jboss.modules.ModuleNotFoundException: jdk.jconsole > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10512) jboss-cli not starting using jre10 (possible regression)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-10512?page=com.atlassian.jira.plugin... ] Jean-Francois Denise updated WFLY-10512: ---------------------------------------- Priority: Blocker (was: Major) > jboss-cli not starting using jre10 (possible regression) > -------------------------------------------------------- > > Key: WFLY-10512 > URL: https://issues.jboss.org/browse/WFLY-10512 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 13.0.0.Final > Environment: Java 10.0.1 (oracle server-jdk), Windows 10 > Reporter: Martin Miller > Assignee: Jean-Francois Denise > Priority: Blocker > > Under an environment with a JAVA_HOME to java 10.0.1, > I can start the jboss-cli.ps1 under Wildfly 12, but under Wildfly 13 I get: > org.jboss.modules.ModuleNotFoundException: jdk.jconsole > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3909) jboss-cli script does not delegate -D properties to java process

by Erich Duda (JIRA)

Erich Duda created WFCORE-3909: ---------------------------------- Summary: jboss-cli script does not delegate -D properties to java process Key: WFCORE-3909 URL: https://issues.jboss.org/browse/WFCORE-3909 Project: WildFly Core Issue Type: Bug Components: CLI, Scripts Affects Versions: 5.0.0.Final Reporter: Erich Duda Assignee: Jean-Francois Denise *Scenario:* I want to change logging configuration of CLI using system properties. My expectation is that I just put the properties on command line as arguments. {code} ./jboss-cli.sh -Dlogging.configuration=... -Djboss.cli.log.level=TRACE -Djboss.cli.log.level=TRACE {code} However what I actually have to do is to put the properties into the {{JAVA_OPTS}} env variable. {code} JAVA_OPTS="-Dlogging.configuration=... -Djboss.cli.log.level=TRACE -Djboss.cli.log.level=TRACE" ./jboss-cli.sh {code} This is different behavior than I am used to standalone.sh script. IMO it is more natural to put the properties as arguments of the script. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-282) modify "assert_all_items" to create more user defined combinations

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-282?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-282: --------------------------------------- PR sent: https://github.com/Kiali-QE/kiali-qe-python/pull/50 > modify "assert_all_items" to create more user defined combinations > ------------------------------------------------------------------ > > Key: SWSQE-282 > URL: https://issues.jboss.org/browse/SWSQE-282 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > modify "assert_all_items" to create more user-defined combinations -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2575) Executable model - DRL integration tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2575?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2575: ------------------------------------- 2nd commit https://github.com/kiegroup/drools/commit/aa8f2fa9dc1ffba2bc8734476075dc6... > Executable model - DRL integration tests fail with the model > ------------------------------------------------------------ > > Key: DROOLS-2575 > URL: https://issues.jboss.org/browse/DROOLS-2575 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When running DRL integration tests [1] with the executable model, 118 out of 510 test cases fail. PR with tests is here [2]. > [1] https://github.com/kiegroup/drools/tree/master/drools-compiler/src/test/j... > [2] https://github.com/kiegroup/drools/pull/1915 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10488) Upgrade WildFly HTTP Client to 1.0.13.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10488?page=com.atlassian.jira.plugin... ] Stuart Douglas reassigned WFLY-10488: ------------------------------------- Assignee: Stuart Douglas > Upgrade WildFly HTTP Client to 1.0.13.Final > ------------------------------------------- > > Key: WFLY-10488 > URL: https://issues.jboss.org/browse/WFLY-10488 > Project: WildFly > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3908) Server fails to start after setting invalid property of remoting connector

by Radovan Stancel (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3908?page=com.atlassian.jira.plugi... ] Radovan Stancel moved JBEAP-14844 to WFCORE-3908: ------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3908 (was: JBEAP-14844) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Remoting (was: Remoting) Affects Version/s: 6.0.0.Alpha1 (was: 7.1.0.CR2) > Server fails to start after setting invalid property of remoting connector > -------------------------------------------------------------------------- > > Key: WFCORE-3908 > URL: https://issues.jboss.org/browse/WFCORE-3908 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 6.0.0.Alpha1 > Reporter: Radovan Stancel > Assignee: Radovan Stancel > Priority: Critical > > When adding an property with invalid name to the remoting connector and subsequent reload, the server fails to start. > See server stack-trace: > {code:java} > 2017-09-27 15:23:08,755 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "remoting"), > ("connector" => "bbb") > ]): java.lang.IllegalArgumentException: XNIO000005: No such field named "bbb" in class org.xnio.Options > at org.xnio.Option.fromString(Option.java:157) > at org.jboss.as.remoting.ConnectorUtils.addOptions(ConnectorUtils.java:164) > at org.jboss.as.remoting.ConnectorUtils.getFullOptions(ConnectorUtils.java:82) > at org.jboss.as.remoting.ConnectorAdd.launchServices(ConnectorAdd.java:82) > at org.jboss.as.remoting.ConnectorAdd.performRuntime(ConnectorAdd.java:78) > at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:976) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:446) > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:386) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10512) jboss-cli not starting using jre10 (possible regression)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-10512?page=com.atlassian.jira.plugin... ] Jean-Francois Denise updated WFLY-10512: ---------------------------------------- Summary: jboss-cli not starting using jre10 (possible regression) (was: jboss-cli.ps1 not working (possible regression)) > jboss-cli not starting using jre10 (possible regression) > -------------------------------------------------------- > > Key: WFLY-10512 > URL: https://issues.jboss.org/browse/WFLY-10512 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 13.0.0.Final > Environment: Java 10.0.1 (oracle server-jdk), Windows 10 > Reporter: Martin Miller > Assignee: Jean-Francois Denise > > Under an environment with a JAVA_HOME to java 10.0.1, > I can start the jboss-cli.ps1 under Wildfly 12, but under Wildfly 13 I get: > org.jboss.modules.ModuleNotFoundException: jdk.jconsole > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10512) jboss-cli.ps1 not working (possible regression)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-10512?page=com.atlassian.jira.plugin... ] Jean-Francois Denise commented on WFLY-10512: --------------------------------------------- I can reproduce by using jre10 instead of jdk10 both with ps1 and bat file on Windows. As you wrote, with wildly12, jboss-cli can start with jre. Something changed in jboss modules. Investigating. For now be sure to set JAVA_HOME to jdk10. > jboss-cli.ps1 not working (possible regression) > ----------------------------------------------- > > Key: WFLY-10512 > URL: https://issues.jboss.org/browse/WFLY-10512 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 13.0.0.Final > Environment: Java 10.0.1 (oracle server-jdk), Windows 10 > Reporter: Martin Miller > Assignee: Jean-Francois Denise > > Under an environment with a JAVA_HOME to java 10.0.1, > I can start the jboss-cli.ps1 under Wildfly 12, but under Wildfly 13 I get: > org.jboss.modules.ModuleNotFoundException: jdk.jconsole > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 June 2018