November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7388) NullPointerException Adding FileSystemRealm with identities in a batch.

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7388?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7388: ---------------------------------- Stacktrace: {code:java} [standalone@localhost:9990 /] run-batch --file=/opt/jboss/commands.txt 13:18:29,763 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("filesystem-realm" => "exampleFsRealm"), ("identity" => "jduke(a)JBOSS.ORG") ]): java.lang.NullPointerException at org.wildfly.extension.elytron.IdentityResourceDefinition$IdentityAddHandler.lambda$execute$0(IdentityResourceDefinition.java:136) 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:1361) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:411) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:233) 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) The batch failed with the following error: : {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-5" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}} {code} > NullPointerException Adding FileSystemRealm with identities in a batch. > ----------------------------------------------------------------------- > > Key: WFLY-7388 > URL: https://issues.jboss.org/browse/WFLY-7388 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > {{/subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add() > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add-attribute(name=Roles, value=["Admin","Guest"]) > /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) > /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)}} > {noformat} > Step 21 : RUN /opt/jboss/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/bin/jboss-cli.sh --commands=embed-server\ --server-config=standalone-elytron.xml,run-batch\ --file=/opt/jboss/commands.txt,stop-embedded-server > ---> Running in fb3e83746136 > The batch failed with the following error: : {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}} > {noformat} > NullPointerException experienced randomly, initially this sounds like the service is not fully up by the time the first command completes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1921?page=com.atlassian.jira.plugi... ] Hynek Švábek updated WFCORE-1921: --------------------------------- Description: Problem with resources which name contains only NUMBERS. Particularly the number which beginning with ZERO(s). *Scenario* * I have resources which name contains only numbers with ZERO(s) prefix * I want set capability-reference to it * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111]) *Actual result* {code} { "outcome" => "failed", "failure-description" => "WFLYCTL0369: Required capabilities are not available: org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.", "rolled-back" => true } {code} *Expected result* {code} Success {code} *NOTE* In my opinion is this global problem. I tried it with another subsystem and problem is there too. {code} /subsystem=datasources/data-source=001:add(connection-url="url", jndi-name="java:jboss/datasources/001", driver-name=h2) /subsystem=infinispan/cache-container=server/local-cache=default/store=string-jdbc:add(data-source=001) {code} was: Problem with resources which name contains only NUMBERS. Particularly the number which beginning with ZERO(s). *Scenario* * I have resources which name contains only numbers with ZERO(s) prefix * I want set capability-reference to it * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111]) *Actual result* {code} { "outcome" => "failed", "failure-description" => "WFLYCTL0369: Required capabilities are not available: org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.", "rolled-back" => true } {code} *Expected result* {code} Success {code} > Problem with capability-reference to resource whose name is number with ZERO(s) prefix. > --------------------------------------------------------------------------------------- > > Key: WFCORE-1921 > URL: https://issues.jboss.org/browse/WFCORE-1921 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Hynek Švábek > Assignee: Jean-Francois Denise > > Problem with resources which name contains only NUMBERS. > Particularly the number which beginning with ZERO(s). > *Scenario* > * I have resources which name contains only numbers with ZERO(s) prefix > * I want set capability-reference to it > * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111]) > *Actual result* > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.", > "rolled-back" => true > } > {code} > *Expected result* > {code} > Success > {code} > *NOTE* > In my opinion is this global problem. > I tried it with another subsystem and problem is there too. > {code} > /subsystem=datasources/data-source=001:add(connection-url="url", jndi-name="java:jboss/datasources/001", driver-name=h2) > /subsystem=infinispan/cache-container=server/local-cache=default/store=string-jdbc:add(data-source=001) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1922) Use a subsystem to manage configuration changes in the future

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-1922: ----------------------------------------- Summary: Use a subsystem to manage configuration changes in the future Key: WFCORE-1922 URL: https://issues.jboss.org/browse/WFCORE-1922 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha11 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Currently configuration-changes are managed as a part of the 'kernel' of WildFly Core. Moving this feature to a proper subsystem is more appropriate as it would provide a nice way to deploy on managed servers according to a profile instead of a host. Making this subsystem host-enabled we could also just configure it at a host level. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1351) Calling KieRepository.getKieModule() for a GAV of a non KJar throws Exception instead of returning null as per API contract.

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1351?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1351: ---------------------------------------- This issue is induced by changes introduced with [DROOLS-1335]. This issue has not been cloned to product at the time of this writing, and therefore not cherry-picked to 6.5.x community, as neither have been [DROOLS-1335]. > Calling KieRepository.getKieModule() for a GAV of a non KJar throws Exception instead of returning null as per API contract. > ---------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1351 > URL: https://issues.jboss.org/browse/DROOLS-1351 > Project: Drools > Issue Type: Bug > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Fix For: 7.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1716) JMX domains jboss.as and jboss.as.expr do not always correctly handle propertly list patters in queryMBeans and queryNames

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1716?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1716: ------------------------------------------------- Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1367784|https://bugzilla.redhat.com/show_bug.cgi?id=1367784] from MODIFIED to ON_QA > JMX domains jboss.as and jboss.as.expr do not always correctly handle propertly list patters in queryMBeans and queryNames > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1716 > URL: https://issues.jboss.org/browse/WFCORE-1716 > Project: WildFly Core > Issue Type: Bug > Components: JMX > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha6 > > > The ObjectName filtering logic added for WFLY-3161 does not handle queryMBeans and queryNames correctly in some cases where the ObjectName param to the method is a property list pattern (i.e. one that includes a simple '*' at the end of the list of properties, meaning "all other properties besides previous ones whose keys were specifically enumerated, match".) > The problem occurs when the the ObjectName does specifically include some keys, and those keys don't correspond to the final elements of the related management resource's PathAddress. As the RootResourceIterator walks the management resource tree, ModelControllerMBeanHelper.ObjectNameMatchResourceAction will not identify the parent resources of children that should match as matching, with the result that the iterator will not descend into that part of the tree and the children will not be matched. For example, this query will return an empty set because the /socket-binding-group=standard-sockets parent will not be matched, preventing checks of the socket-binding-group children. > {code} > Set<ObjectInstance> instances = connection.queryMBeans(createObjectName("jboss.as:socket-binding=*,*"), null); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7453) Resource description should not contain javadoc style links

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/WFLY-7453?page=com.atlassian.jira.plugin.... ] Martin Švehla updated WFLY-7453: -------------------------------- Affects Version/s: 11.0.0.Alpha1 > Resource description should not contain javadoc style links > ----------------------------------------------------------- > > Key: WFLY-7453 > URL: https://issues.jboss.org/browse/WFLY-7453 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Švehla > Assignee: Jason Greene > Priority: Minor > Labels: user_experience > > Description of the attribute {{date-format}} in > {code} > /core-service=management/access=audit/json-formatter=json-formatter > {code} > has following description: > {panel} > The date format to use as understood by \{@link java.text.SimpleDateFormat}. Will be ignored if include-date=\"false\". > {panel} > The description string shouldn't contain javadoc style @link -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7451) Extra commas in descriptions of *-outbound-socket-binding CLI resources

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7451?page=com.atlassian.jira.plugin.... ] Ondrej Kotek updated WFLY-7451: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Extra commas in descriptions of *-outbound-socket-binding CLI resources > ----------------------------------------------------------------------- > > Key: WFLY-7451 > URL: https://issues.jboss.org/browse/WFLY-7451 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Kotek > Assignee: Jason Greene > Priority: Trivial > Labels: user_experience > > There are extra commas in descriptions of children resources of _socket-binding-group_ CLI resource (_local-destination-outbound-socket-binding_ and _remote-destination-outbound-socket-binding_). > E.g., there is "Configuration information for a, local destination, outbound socket binding.", there should be "Configuration information for a local destination outbound socket binding." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7448) Wrong description of Elytron configurable-sasl-server-factory in CLI

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7448?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7448: ------------------------------- Priority: Major (was: Minor) > Wrong description of Elytron configurable-sasl-server-factory in CLI > -------------------------------------------------------------------- > > Key: WFLY-7448 > URL: https://issues.jboss.org/browse/WFLY-7448 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > Description of {{configurable-sasl-server-factory}} resource in CLI is incorrectly copied from {{aggregate-sasl-server-factory}}. It says "description" => "A sasl server factory definition where the sasl server factory is an aggregation of other sasl server factories.". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7452) Insufficient failure-description for filters of Elytron configurable-sasl-server-factory

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7452?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7452: ------------------------------- Priority: Major (was: Minor) > Insufficient failure-description for filters of Elytron configurable-sasl-server-factory > ---------------------------------------------------------------------------------------- > > Key: WFLY-7452 > URL: https://issues.jboss.org/browse/WFLY-7452 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > In case when both {{pattern-filter}} and {{predefined-filter}} are set in one Object in CLI command for {{filters}} of Elytron {{configurable-sasl-server-factory}} then it finishes with insufficient failure-description: > {code} > /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}]) > { > "outcome" => "failed", > "failure-description" => "WFLYELY01014: Invalid [filters] definition.", > "rolled-back" => true > } > {code} > This failure-description is not wrong but it is also not helpful. Improve failure-description to say that only one of {{pattern-filter}} and {{predefined-filter}} can be set in one Object in list of filters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7450) Wrong documentation of Elytron configurable-http-server-mechanism-factory properties element in XSD

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7450?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7450: ------------------------------- Priority: Major (was: Optional) > Wrong documentation of Elytron configurable-http-server-mechanism-factory properties element in XSD > --------------------------------------------------------------------------------------------------- > > Key: WFLY-7450 > URL: https://issues.jboss.org/browse/WFLY-7450 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > Documentation of element {{properties}} for {{configurable-http-server-mechanism-factory}} (httpServerMechanismFactoryType) in wildfly-elytron_1_0.xsd says: "Additional properties that should be passed to the factor for SASL mechanism detection and creation.". However it should be HTTP mechanism instead of SASL. There is also typo "factor", it should be "factory". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016