April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by G Xiong (JIRA)

G Xiong created DROOLS-1540: ------------------------------- Summary: Drools does not work with spring-boot-devtools Key: DROOLS-1540 URL: https://issues.jboss.org/browse/DROOLS-1540 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final Reporter: G Xiong Assignee: Mario Fusco Priority: Critical Attachments: complete.zip Drools does work with spring-boot-devtools. If you add in pom.xml the following, no rules will be fired in Drools. <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-devtools</artifactId> </dependency> if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2730) empty target-name in constant-permission-mapper is not allowed

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2730?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-2730: ------------------------------- Description: For some purposes there is need to construct permission with blank string as param (name/action) - for example *WebResourcePermission*. Such permission cannot be currently assigned using *constant-permission-mapper* because it requires at least one character to be not-null: If I try to assing permission with blank name ({{target-name=""}}) (example in steps to reproduce), parse error is thrown: {code} | > ParseError at [row,col]:[367,5] | > Message: "WFLYCTL0113: '' is an invalid value for parameter | > target-name. Values must have a minimum length of 1 characters" {code} was: I need to have an empty target-name because of the WebResourcePermission. But with unspecified target-name the primary underlying error message was: {code} | > ParseError at [row,col]:[367,5] | > Message: "WFLYCTL0113: '' is an invalid value for parameter | > target-name. Values must have a minimum length of 1 characters" {code} > empty target-name in constant-permission-mapper is not allowed > -------------------------------------------------------------- > > Key: WFCORE-2730 > URL: https://issues.jboss.org/browse/WFCORE-2730 > Project: WildFly Core > Issue Type: Bug > Reporter: Eva Jarkovská > Assignee: Jan Kalina > > For some purposes there is need to construct permission with blank string as param (name/action) - for example *WebResourcePermission*. > Such permission cannot be currently assigned using *constant-permission-mapper* because it requires at least one character to be not-null: > If I try to assing permission with blank name ({{target-name=""}}) (example in steps to reproduce), parse error is thrown: > {code} > | > ParseError at [row,col]:[367,5] > | > Message: "WFLYCTL0113: '' is an invalid value for parameter > | > target-name. Values must have a minimum length of 1 characters" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2739) Misspelt capability org.wildfly.management.model-controller-client-factory/notification-handler-registry names

by Radoslav Husar (JIRA)

Radoslav Husar created WFCORE-2739: -------------------------------------- Summary: Misspelt capability org.wildfly.management.model-controller-client-factory/notification-handler-registry names Key: WFCORE-2739 URL: https://issues.jboss.org/browse/WFCORE-2739 Project: WildFly Core Issue Type: Bug Components: Server Affects Versions: 3.0.0.Beta17 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor org.wildfly.managment.notification-handler-registry org.wildfly.managment.model-controller-client-factory -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8674) Principal from @RunAsPrincipal bean annotation does not get authorised with role from @RunAs bean annotation unless the user exists in backing security realm

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8674?page=com.atlassian.jira.plugin.... ] Farah Juma moved JBEAP-10636 to WFLY-8674: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8674 (was: JBEAP-10636) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB Security (was: EJB) (was: Security) Affects Version/s: (was: 7.1.0.DR12) (was: 7.1.0.DR13) (was: 7.1.0.DR14) (was: 7.1.0.DR16) (was: 7.1.0.DR15) (was: 7.1.0.DR17) > Principal from @RunAsPrincipal bean annotation does not get authorised with role from @RunAs bean annotation unless the user exists in backing security realm > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8674 > URL: https://issues.jboss.org/browse/WFLY-8674 > Project: WildFly > Issue Type: Bug > Components: EJB, Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Labels: KK-DR18, eap7.1-rfe-blocker, eap71_beta_candidate > > If a bean is annotated with both {{@RunAs}} and {{@RunAsPrincipal}} annotations, the principal will not get authorised unless the user with such principal exists in security realm that the bean is backed by. > This was not the case with PicketBox. Since the existing EJB-Elytron integration analyses and documentation does not mention such a modification and the change makes an AS TS test case fail, this is an unexpected change of behavior. > Reproducer and sources attached. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8673) ASYM_ENCRYPT legacy configuration should not attempt to create elytron reference

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8673?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-10635 to WFLY-8673: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8673 (was: JBEAP-10635) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) (was: Migration) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR16) > ASYM_ENCRYPT legacy configuration should not attempt to create elytron reference > -------------------------------------------------------------------------------- > > Key: WFLY-8673 > URL: https://issues.jboss.org/browse/WFLY-8673 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Labels: eap7.1-rfe-failure > > I found that currently, when configuring {{ASYM_ENCRYPT}} in legacy way, an elytron key-store reference is always automatically created. That should not happen as people who want to use the legacy security may want to remove the Elytron subsystem entirely. JGroups boot would fail in that case. > {noformat} > /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT:add() > /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT/property=encrypt_entire_message:add(value=true) > /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT/property=sym_keylength:add(value=512) > /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT/property=sym_algorithm:add(value=AES/ECB/PKCS5Padding) > /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT/property=asym_keylength:add(value=512) > /subsystem=jgroups/stack=udp2/protocol=ASYM_ENCRYPT/property=asym_algorithm:add(value=RSA) > {noformat} > Here, I removed the elytron subsystem and used configuration from JBEAP-8405. > {noformat} > 12:56:22,202 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "jgroups"), > ("stack" => "tcp"), > ("protocol" => "ASYM_ENCRYPT") > ]) - failure description: "WFLYCLJG0026: No add operation registered at /subsystem=elytron/key-store=jgroups-tcp" > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-95) Test Case - Topology Fails when Linked to Container

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-95: -------------------------------------- Summary: Test Case - Topology Fails when Linked to Container Key: HAWKULARQE-95 URL: https://issues.jboss.org/browse/HAWKULARQE-95 Project: Hawkular QE Issue Type: Feature Request Reporter: Matt Mahoney Assignee: Michael Foley Do we have a test case for the following? " topology view fails once I have a server linked to a container" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-94) Pumba Testing on ER2

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created HAWKULARQE-94: ------------------------------------------------- Summary: Pumba Testing on ER2 Key: HAWKULARQE-94 URL: https://issues.jboss.org/browse/HAWKULARQE-94 Project: Hawkular QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-94) Pumba Testing on ER2

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-94?page=com.atlassian.jira.plu... ] Guilherme Baufaker Rêgo reassigned HAWKULARQE-94: ------------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Pumba Testing on ER2 > -------------------- > > Key: HAWKULARQE-94 > URL: https://issues.jboss.org/browse/HAWKULARQE-94 > Project: Hawkular QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2738) Attachments.SUB_DEPLOYMENTS leaks on undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2738?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFCORE-2738: ----------------------------------- Priority: Critical (was: Major) > Attachments.SUB_DEPLOYMENTS leaks on undeploy > --------------------------------------------- > > Key: WFCORE-2738 > URL: https://issues.jboss.org/browse/WFCORE-2738 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.0.Beta17 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > {noformat} > 19:33:36,944 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "clusterbench-ee7-singleton-jbossall.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > 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:745) > Caused by: java.lang.NullPointerException > at org.jboss.as.server.deployment.module.SubDeploymentDependencyProcessor.deploy(SubDeploymentDependencyProcessor.java:74) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2738) Attachments.SUB_DEPLOYMENTS leaks on undeploy

by Radoslav Husar (JIRA)

Radoslav Husar created WFCORE-2738: -------------------------------------- Summary: Attachments.SUB_DEPLOYMENTS leaks on undeploy Key: WFCORE-2738 URL: https://issues.jboss.org/browse/WFCORE-2738 Project: WildFly Core Issue Type: Bug Affects Versions: 3.0.0.Beta17 Reporter: Radoslav Husar Assignee: Radoslav Husar {noformat} 19:33:36,944 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "clusterbench-ee7-singleton-jbossall.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) 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:745) Caused by: java.lang.NullPointerException at org.jboss.as.server.deployment.module.SubDeploymentDependencyProcessor.deploy(SubDeploymentDependencyProcessor.java:74) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) ... 5 more {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 11 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 April 2017