May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2269) probe.sh is not working on Ubuntu

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2269?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2269: --------------------------- Fix Version/s: 4.0.12 > probe.sh is not working on Ubuntu > --------------------------------- > > Key: JGRP-2269 > URL: https://issues.jboss.org/browse/JGRP-2269 > Project: JGroups > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.12 > > > Clone the JGroups project using the branch master > diego@diego-note:/storage/git/JGroups/bin$ ./probe.sh > ./probe.sh: 8: ./probe.sh: jgroups.sh: not found -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3806) Eliminate code that was using transitive MSC dependencies

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3806?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3806: -------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.0.0.Final) > Eliminate code that was using transitive MSC dependencies > --------------------------------------------------------- > > Key: WFCORE-3806 > URL: https://issues.jboss.org/browse/WFCORE-3806 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.Alpha1 > > > Prior MSC 1.2.8 stability monitors were reporting problems if > some transitive dependency wasn't available. This has changed > since MSC 1.2.8. There is no notion of transitive > dependencies in JBoss MSC anymore. If stability monitor detects > a problem it is always immediate dependency of monitored controller. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3817) Remove usages of deprecated ServiceListeners

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3817?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3817: -------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.0.0.Final) > Remove usages of deprecated ServiceListeners > -------------------------------------------- > > Key: WFCORE-3817 > URL: https://issues.jboss.org/browse/WFCORE-3817 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2597) Standalone Authoring documentation header example should be better

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2597?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHPAM-1120 to DROOLS-2597: --------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-2597 (was: RHPAM-1120) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: docs (was: Business Central) QE Status: NEW > Standalone Authoring documentation header example should be better > ------------------------------------------------------------------ > > Key: DROOLS-2597 > URL: https://issues.jboss.org/browse/DROOLS-2597 > Project: Drools > Issue Type: Bug > Components: docs > Reporter: Toni Rikkola > Assignee: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2596) KieScanner does not load new rules

by Viacheslav Krot (JIRA)

Viacheslav Krot created DROOLS-2596: --------------------------------------- Summary: KieScanner does not load new rules Key: DROOLS-2596 URL: https://issues.jboss.org/browse/DROOLS-2596 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final, 7.6.0.Final Reporter: Viacheslav Krot Assignee: Mario Fusco Attachments: drools7_bug.zip, drools7_bug_rules.zip There is a problem with adding new rules via KieScanner. If I add new .drl files to rules artifact - new rules are not fired. KieScanner successfully updates artifact, it applies changes to previously loaded rules, but it does not see new rules. I've created a simple project reproducing this bug. Steps to reproduce: - unpack drools7_bug and drools7_bug_rules projects - build drools7_bug (mvn clean install) - updated repository url in drools7_bug_rules pom, deploy it - run Main in drools7_bug. rule1 is fired, prints to stderr once a second. - copy rule2.drl from src/main/tmp to src/main/resources. change output string in rule1. - deploy artifact - now I expect both rules fired, but only rule1 is works, no output from rule2. Make sure new artifact was loaded in scanner jmx bean. Rule1 writes new string to stderr, it was updated. - now simply restart Main, both rules are fired. There are no error or warning, new rules simply don't work. Am I doing something wrong? Same scenario worked perfect until version 7.5.0. You can update version in pom and same scenario passes successfully. 7.6.0 and 7.7.0 don't though I added api module with pojos just to reproduce our usecase as close as possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10473) mod_cluster subsystem add operation attempts to start services prematurely

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-10473: ------------------------------------- Summary: mod_cluster subsystem add operation attempts to start services prematurely Key: WFLY-10473 URL: https://issues.jboss.org/browse/WFLY-10473 Project: WildFly Issue Type: Bug Components: mod_cluster Reporter: Radoslav Husar Assignee: Radoslav Husar This has been a problem multiple times in the past. Even a single subsystem add operation like {noformat} [standalone@localhost:9990 /] /subsystem=modcluster:add { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } {noformat} causes failures {noformat}10:28:15,128 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" 10:28:15,135 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" {noformat} This is fixes also as a side effect to supporting multiple configurations. Since boot time handling is required, most operations on the subsystem need to leave the server in the reload-required state. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10473) mod_cluster subsystem add operation attempts to start services prematurely

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10473?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10473: ---------------------------------- Affects Version/s: 13.0.0.Beta1 > mod_cluster subsystem add operation attempts to start services prematurely > -------------------------------------------------------------------------- > > Key: WFLY-10473 > URL: https://issues.jboss.org/browse/WFLY-10473 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > This has been a problem multiple times in the past. Even a single subsystem add operation like > {noformat} > [standalone@localhost:9990 /] /subsystem=modcluster:add > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > causes failures > {noformat}10:28:15,128 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" > 10:28:15,135 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" > {noformat} > This is fixes also as a side effect to supporting multiple configurations. > Since boot time handling is required, most operations on the subsystem need to leave the server in the reload-required state. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10473) mod_cluster subsystem add operation attempts to start services prematurely

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10473?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10473: ---------------------------------- Description: This has been a problem multiple times in the past. Even a single subsystem add operation like {noformat} [standalone@localhost:9990 /] /subsystem=modcluster:add { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } {noformat} causes failures {noformat}10:28:15,128 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" 10:28:15,135 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" {noformat} This is fixed also as a side effect to supporting multiple configurations. Since boot time handling is required, most operations on the subsystem need to leave the server in the reload-required state. was: This has been a problem multiple times in the past. Even a single subsystem add operation like {noformat} [standalone@localhost:9990 /] /subsystem=modcluster:add { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } {noformat} causes failures {noformat}10:28:15,128 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" 10:28:15,135 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" {noformat} This is fixes also as a side effect to supporting multiple configurations. Since boot time handling is required, most operations on the subsystem need to leave the server in the reload-required state. > mod_cluster subsystem add operation attempts to start services prematurely > -------------------------------------------------------------------------- > > Key: WFLY-10473 > URL: https://issues.jboss.org/browse/WFLY-10473 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > This has been a problem multiple times in the past. Even a single subsystem add operation like > {noformat} > [standalone@localhost:9990 /] /subsystem=modcluster:add > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > causes failures > {noformat}10:28:15,128 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" > 10:28:15,135 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null" > {noformat} > This is fixed also as a side effect to supporting multiple configurations. > Since boot time handling is required, most operations on the subsystem need to leave the server in the reload-required state. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3829) ReloadRedirectTestCase#testRedirectWithSecurityCommands fails on IBM JDK

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3829?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3829: ---------------------------------------------- @Petr, this seems to me that ReloadRedirectTestCase.testReloadwithRedirect should fail also. There is an option -Dcom.ibm.jsse2.overrideDefaultTLS=true that is missing for all test cases. > ReloadRedirectTestCase#testRedirectWithSecurityCommands fails on IBM JDK > ------------------------------------------------------------------------ > > Key: WFCORE-3829 > URL: https://issues.jboss.org/browse/WFCORE-3829 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Test Suite > Affects Versions: 5.0.0.Alpha7 > Reporter: Petr Kremensky > Assignee: Jean-Francois Denise > > I tried to run the CLI command from failing assertion manually and it does seem to work as expected, so this more like the testing code problem than functional issue. > *reproduce* > {noformat} > ...wildfly-core] $ mvn clean test -Dtest=ReloadRedirectTestCase#testRedirectWithSecurityCommands -DallTests -pl testsuite/manualmode > ... > [INFO] Running org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 33.474 s <<< FAILURE! - in org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase > [ERROR] testRedirectWithSecurityCommands(org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase) Time elapsed: 22.653 s <<< FAILURE! > java.lang.AssertionError: No certificate prompt > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase.testRedirectWithSecurityCommands(ReloadRedirectTestCase.java:269) > ... > {noformat} > *environment* > {noformat} > $ mvn -version > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00) > Maven home: /usr/lib/maven > Java version: 1.8.0_161, vendor: IBM Corporation > Java home: /usr/lib/java/ibm-java-8.0-5.11/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix" > $ git rev-parse --short HEAD > c0847897a3 > {noformat} > *qa note* > The test fail causes some other failures in manualmode module: > org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase.testRedirectWithSecurityCommands > org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase.testReloadwithRedirect > org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testRightVaultPassword > org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.testTrustedCLICertificate > org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.testHTTPS > org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.testHTTP > org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.testHTTPSWithCredentialReference > *ibm jdk download* > https://developer.ibm.com/javasdk/downloads/sdk8/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10472) HttpInvokerDefinition should not be adding optional dependency on mod_cluster event handler adapter

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-10472: ------------------------------------- Summary: HttpInvokerDefinition should not be adding optional dependency on mod_cluster event handler adapter Key: WFLY-10472 URL: https://issues.jboss.org/browse/WFLY-10472 Project: WildFly Issue Type: Bug Components: mod_cluster, Web (Undertow) Affects Versions: 13.0.0.Beta1 Reporter: Radoslav Husar Assignee: Radoslav Husar TBD [3:02 PM] Radoslav Husar: I want this dependency hell thing to go away https://github.com/wildfly/wildfly/blob/master/undertow/src/main/java/org... [3:03 PM] Radoslav Husar: The original issue was https://issues.jboss.org/browse/WFLY-8439 [3:04 PM] Radoslav Husar: but this just looks like a workaround for racy clean shutdown and the notification API [3:05 PM] Radoslav Husar: is there any chance you remember why would the dependency be needed? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

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