September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1307) Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1307: -------------------------------------- Summary: Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage Key: DROOLS-1307 URL: https://issues.jboss.org/browse/DROOLS-1307 Project: Drools Issue Type: Task Components: integration Reporter: Matteo Mortari Assignee: Matteo Mortari Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1306) Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1306: -------------------------------------- Summary: Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage Key: DROOLS-1306 URL: https://issues.jboss.org/browse/DROOLS-1306 Project: Drools Issue Type: Task Components: integration Reporter: Matteo Mortari Assignee: Matteo Mortari Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1305) Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1305?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1305: ---------------------------------------- As requested at https://github.com/droolsjbpm/droolsjbpm-integration/pull/649#issuecommen... > Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1305 > URL: https://issues.jboss.org/browse/DROOLS-1305 > Project: Drools > Issue Type: Task > Components: integration > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1305) Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1305?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1305: ---------------------------------------- As original droolsjbpm-integration/droolsjbpm-integration-tests module is passing all tests, all CI cycles etc. however due to a bug of a rule of the nexus-staging-maven-plugin it prevents from successfully staging the reactor build for nexus publishing (this module does not contain any JAR and the nexus-staging-maven-plugin ENFORCES having a jar for staging and publishing to Nexus) > Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1305 > URL: https://issues.jboss.org/browse/DROOLS-1305 > Project: Drools > Issue Type: Task > Components: integration > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1305) Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1305: -------------------------------------- Summary: Move DROOLS-1278 from droolsjbpm-integration/droolsjbpm-integration-tests to jbpm/jbpm-test-coverage Key: DROOLS-1305 URL: https://issues.jboss.org/browse/DROOLS-1305 Project: Drools Issue Type: Task Components: integration Reporter: Matteo Mortari Assignee: Matteo Mortari Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7202) generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7202?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-7202: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1378723, https://bugzilla.redhat.com/show_bug.cgi?id=1379571, https://bugzilla.redhat.com/show_bug.cgi?id=1379572 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1378723, https://bugzilla.redhat.com/show_bug.cgi?id=1379571) > generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7202 > URL: https://issues.jboss.org/browse/WFLY-7202 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Tom Ross > Assignee: Tom Ross > > The code snippet shows that the method returns wrong type. > {noformat} > public String getSessionDefaultType() { > if (type == JmsConnectionFactory.AGNOSTIC) > return "agnostic"; > else if (type == JmsConnectionFactory.QUEUE) > return TOPIC_TYPE; > else > return QUEUE_TYPE; > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7202) generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7202?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-7202: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1378723, https://bugzilla.redhat.com/show_bug.cgi?id=1379571 Bugzilla Update: Perform > generic-jms-ra's JmsMCFProperties.getSessionDefaultType returns incorrect value for session type > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7202 > URL: https://issues.jboss.org/browse/WFLY-7202 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Tom Ross > Assignee: Tom Ross > > The code snippet shows that the method returns wrong type. > {noformat} > public String getSessionDefaultType() { > if (type == JmsConnectionFactory.AGNOSTIC) > return "agnostic"; > else if (type == JmsConnectionFactory.QUEUE) > return TOPIC_TYPE; > else > return QUEUE_TYPE; > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1830) Upgrade MSC from 1.2.6.Final-redhat-1 to 1.2.7.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1830?page=com.atlassian.jira.plugi... ] Ivo Studensky moved JBEAP-6219 to WFCORE-1830: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1830 (was: JBEAP-6219) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management (was: MSC) Affects Version/s: 3.0.0.Alpha8 (was: 7.0.0.ER1) > Upgrade MSC from 1.2.6.Final-redhat-1 to 1.2.7.Final > ---------------------------------------------------- > > Key: WFCORE-1830 > URL: https://issues.jboss.org/browse/WFCORE-1830 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Domain Management > Affects Versions: 3.0.0.Alpha8 > Reporter: Ivo Studensky > Assignee: David Lloyd > > This is an upgrade jira for MSC component. See the referenced issues that need to get in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7226) Missing realm-map attribute for mapped-regex-realm-mapper throws IllegalArgumentException to server log

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7226: ---------------------------------- Summary: Missing realm-map attribute for mapped-regex-realm-mapper throws IllegalArgumentException to server log Key: WFLY-7226 URL: https://issues.jboss.org/browse/WFLY-7226 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse In case when mapped-regex-realm-mapper is added through CLI and realm-map attribute is not used then IllegalArgumentException is thrown to server log instead of some CLI failure message like "realm-map may not be null". Expcetion in server log: {code} ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("mapped-regex-realm-mapper" => "MappedRealmMapper") ]): java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:139) at org.jboss.dmr.ModelNode.keys(ModelNode.java:1378) at org.wildfly.extension.elytron.RealmMapperDefinitions$MappedRegexRealmMapperAddHandler.performRuntime(RealmMapperDefinitions.java:221) 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:940) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) 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) at org.jboss.threads.JBossThread.run(JBossThread.java:320) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7226) Missing realm-map attribute for mapped-regex-realm-mapper throws IllegalArgumentException to server log

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7226?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7226: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Missing realm-map attribute for mapped-regex-realm-mapper throws IllegalArgumentException to server log > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-7226 > URL: https://issues.jboss.org/browse/WFLY-7226 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In case when mapped-regex-realm-mapper is added through CLI and realm-map attribute is not used then IllegalArgumentException is thrown to server log instead of some CLI failure message like "realm-map may not be null". > Expcetion in server log: > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("mapped-regex-realm-mapper" => "MappedRealmMapper") > ]): java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:139) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1378) > at org.wildfly.extension.elytron.RealmMapperDefinitions$MappedRegexRealmMapperAddHandler.performRuntime(RealmMapperDefinitions.java:221) > 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:940) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 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 September 2016