May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1172) SimpleResourceDefinition.Parameters should support setting access constraints

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1172?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1172: ------------------------------------- Fix Version/s: 2.2.0.CR1 > SimpleResourceDefinition.Parameters should support setting access constraints > ----------------------------------------------------------------------------- > > Key: WFCORE-1172 > URL: https://issues.jboss.org/browse/WFCORE-1172 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > There are a lot of SimpleResourceDefinition impls that are overriding getAccessConstraints. We should support passing in the constraints via the Parameters object passed to the constructor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1342) XML templates have wrong attribute order for audit log file-handler elements

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1342?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1342: ------------------------------------- Fix Version/s: 2.2.0.CR1 > XML templates have wrong attribute order for audit log file-handler elements > ---------------------------------------------------------------------------- > > Key: WFCORE-1342 > URL: https://issues.jboss.org/browse/WFCORE-1342 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.8.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > The path attribute should come before relative-to, which is how the xsd declares them and how the marshaller persists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1424) typo in prompt

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1424?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1424: ------------------------------------- Fix Version/s: 2.2.0.CR1 > typo in prompt > -------------- > > Key: WFCORE-1424 > URL: https://issues.jboss.org/browse/WFCORE-1424 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Valery Sorokin > Assignee: Darran Lofthouse > Priority: Trivial > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > prompt on 'jboss-cli.sh --connect controller=https-remoting://localhost:8443 ' > displays: > ------------------------------------------------------------------- > Accept certificate? [N]o, [T]emporarily, [P]ermenantly : P > ------------------------------------------------------------------- > (not 'permanently') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1426) NPE in GlobalOperationHandlers.getChildAddresses

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1426?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1426: ------------------------------------- Fix Version/s: 2.2.0.CR1 > NPE in GlobalOperationHandlers.getChildAddresses > ------------------------------------------------ > > Key: WFCORE-1426 > URL: https://issues.jboss.org/browse/WFCORE-1426 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > Second line is a potential NPE if the MRR tree has changed since 'element' was found: > final ImmutableManagementResourceRegistration childRegistration = registry.getSubModel(PathAddress.pathAddress(element)); > final AliasEntry aliasEntry = childRegistration.getAliasEntry(); > Failed here: > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=92710&buildTyp... > ======= Failed test run #1 ========== > org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation failed. > at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForResult(DomainTestUtils.java:160) > at org.jboss.as.test.integration.domain.mixed.DomainHostExcludesTest.readChildrenNames(DomainHostExcludesTest.java:302) > at org.jboss.as.test.integration.domain.mixed.DomainHostExcludesTest.stopSlave(DomainHostExcludesTest.java:111) > at org.jboss.as.test.integration.domain.mixed.DomainHostExcludesTest.setup(DomainHostExcludesTest.java:93) > at org.jboss.as.test.integration.domain.mixed.eap630.DomainHostExcludes630TestCase.beforeClass(DomainHostExcludes630TestCase.java:40) > ------- Stdout: ------- > ... > &amp#27;[0m[Host Controller] &amp#27;[0m&amp#27;[0m22:06:43,569 INFO [org.jboss.as.domain.controller] (management task-5) WFLYHC0026: Unregistered remote slave host "slave"&amp#27;[0m > [Host Controller] &amp#27;[0m&amp#27;[31m22:06:43,569 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("read-children-names") failed - address: ([]): java.lang.NullPointerException&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.operations.global.GlobalOperationHandlers.getChildAddresses(GlobalOperationHandlers.java:960)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.operations.global.ReadChildrenNamesHandler.execute(ReadChildrenNamesHandler.java:78)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)&amp#27;[0m > [Host Controller] &amp#27;[31m at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)&amp#27;[0m > [Host Controller] &amp#27; > ... > The test stops host slave and then starts reading children names of type 'host' to see when 'slave' is gone. The registration disappears in the middle of the getChildAddresses logic resulting in NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1397) Boot errors and unmanageable server if http-interface resource's http-upgrade-enabled attribute != true

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1397?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1397: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Boot errors and unmanageable server if http-interface resource's http-upgrade-enabled attribute != true > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1397 > URL: https://issues.jboss.org/browse/WFCORE-1397 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Brian Stansberry > Assignee: Yeray Santana Borges > Priority: Critical > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > The https://github.com/wildfly/wildfly-core/pull/1360 work added a new XnioWorker service that the HTTP interface depends on, but for a standalone server it isn't installed unless http-upgrade-enabled == true. Otherwise you see this during boot: > {code} > 15:43:25,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.serverManagement.controller.management.http is missing [jboss.serverManagement.controller.management.worker]", > "jboss.serverManagement.controller.management.http.shutdown is missing [jboss.remoting.management.channel.registry]" > ]} > 15:43:25,006 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "jmx"), > ("remoting-connector" => "jmx") > ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.jmx.remoting-connector-ref is missing [jboss.remoting.endpoint.management]"]} > 15:43:25,031 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.remoting.endpoint.management (missing) dependents: [service jboss.jmx.remoting-connector-ref] > service jboss.remoting.management.channel.registry (missing) dependents: [service jboss.serverManagement.controller.management.http.shutdown] > service jboss.serverManagement.controller.management.worker (missing) dependents: [service jboss.serverManagement.controller.management.http] > 15:43:25,127 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled > 15:43:25,128 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled > 15:43:25,128 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.0.12.Final-redhat-1) started (with errors) in 3493ms - Started 254 of 544 services (3 services failed or missing dependencies, 369 services are lazy, passive or on-demand) > {code} > The problem is org.jboss.as.server.operations.HttpManagementAddHandler doesn't install the service. The HC variant of HttpManagementAddHandler does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1370) All configuration changes have the same operation date

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1370?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1370: ------------------------------------- Fix Version/s: 2.2.0.CR1 > All configuration changes have the same operation date > ------------------------------------------------------ > > Key: WFCORE-1370 > URL: https://issues.jboss.org/browse/WFCORE-1370 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > When I list the changes, the operation date for all of the changes are the same, and seem to be the date/time when the `list-changes` operation is performed. I tried this just now with ER5: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1352) Embedded logged leaving filehandles open after stop

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1352?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1352: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Embedded logged leaving filehandles open after stop > --------------------------------------------------- > > Key: WFCORE-1352 > URL: https://issues.jboss.org/browse/WFCORE-1352 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Windows > Reporter: Ken Wills > Assignee: James Perkins > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > After stop-embedded-server or stop-embedded-host-controller commands, logs in standalone/logs/ or domain/logs/ are still held open. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1042) ExtensionRemoveHandler logs client mistakes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1042?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1042: ------------------------------------- Fix Version/s: 2.2.0.CR1 > ExtensionRemoveHandler logs client mistakes > ------------------------------------------- > > Key: WFCORE-1042 > URL: https://issues.jboss.org/browse/WFCORE-1042 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR6 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > If a user tries to remove an extension when there are still subsystems present that come from that extension, a stack trace appears in the log: > {code} > 01:02:23,542 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 2) WFLYCTL0013: Operation ("remove") failed - address: ([("extension" => "org.jboss.as.test.hc.extension")]): java.lang.IllegalStateException: WFLYCTL0219: An attempt was made to unregister extension org.jboss.as.test.hc.extension which still has subsystem HC registered > at org.jboss.as.controller.extension.ExtensionRegistry.removeExtension(ExtensionRegistry.java:331) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.extension.ExtensionRemoveHandler.execute(ExtensionRemoveHandler.java:68) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217) [wildfly-controller-2.0.0.CR7-SNAPSHOT.jar:2.0.0.CR7-SNAPSHOT] > {code} > That's really just a client mistake and there's no reason to log it in the server. ExtensionRemoveHandler can catch the ISE thrown by ExtensionRegistry.removeExtension and convert it to an OperationFailedException. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1361) Update the command synopsis for jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1361?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1361: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Update the command synopsis for jboss-cli > ----------------------------------------- > > Key: WFCORE-1361 > URL: https://issues.jboss.org/browse/WFCORE-1361 > Project: WildFly Core > Issue Type: Task > Components: CLI > Affects Versions: 2.1.0.CR1 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > jboss-cli commnad synopsis should be updated to reflect a new arguments > 7.0.0.ER5 > {noformat} > jboss-cli.sh/jboss-cli.bat [--help] [--version] [--controller=host:port] > [--connect] [--file=file_path] > > [--commands=command_or_operation1,command_or_operation2...] > [--command=command_or_operation] > [--user=username --password=password] > [--no-local-auth] > [--error-on-interact] > [--timeout=timeout] > {noformat} > \- protocol or controller alias can be used with --controller as well > \- --bind is missing > \- extra empty line -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1121?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1121: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Use script name for file related to Wildfly to allow multiple instances easily > ------------------------------------------------------------------------------ > > Key: WFCORE-1121 > URL: https://issues.jboss.org/browse/WFCORE-1121 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 2.0.1.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Optional > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the *exact same script* for all local instances: > {code:bash} > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 > # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2 > {code} > And to take the example of the PIDFILE: > {code:bash} > JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid > {code} > Each links will then look up and creates its own separate file: > /var/run/wildfly-1/jboss-as-domain.pid > /var/run/wildfly-2/jboss-as-domain.pid -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016