February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-411: --------------------------------------- Assignee: Alexey Loubyansky (was: Emanuel Muckenhuber) Alexey, I'm not sure if this relates to patching or not; may just be a CLI script issue? > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-348) review server debug-options configuration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-348?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-348: --------------------------------------- Assignee: (was: Emanuel Muckenhuber) > review server debug-options configuration > ----------------------------------------- > > Key: WFCORE-348 > URL: https://issues.jboss.org/browse/WFCORE-348 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > > We need to review the server debug-options configuration, since it's not entirely clear what value is expected. Currently the JVM specific builder is doing additional checks, so that the value passed to the JVM startsWith -X. Which might not be true for all JVMs. > <jvm name="default" debug-enabled="true" debug-options="runjdwp:transport=dt_socket,address=8787,server=y,suspend=n" /> > https://issues.jboss.org/browse/AS7-1606 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-305) Future returned by ModelControllerClient executeAsync does not provide reliable return value from "cancel"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-305?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-305: --------------------------------------- Assignee: (was: Emanuel Muckenhuber) > Future returned by ModelControllerClient executeAsync does not provide reliable return value from "cancel" > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-305 > URL: https://issues.jboss.org/browse/WFCORE-305 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > > DelegatingCancellableAsyncFuture.asyncCancel does not block waiting for the response to the cancel request. As result it is a race whether the status is not reliably set to CANCELLED before that value is tested to determine whether to return true/false. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-315) NPE executing domain operation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-315?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-315: --------------------------------------- Assignee: Brian Stansberry (was: Emanuel Muckenhuber) > NPE executing domain operation > ------------------------------ > > Key: WFCORE-315 > URL: https://issues.jboss.org/browse/WFCORE-315 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > > {noformat} > [ERROR] Request > [ERROR] { > [ERROR] "operation" => "composite", > [ERROR] "address" => [], > [ERROR] "steps" => [ > [ERROR] { > [ERROR] "address" => [("server-group" => "*")], > [ERROR] "operation" => "read-resource-description", > [ERROR] "access-control" => "trim-descriptions", > [ERROR] "operations" => true > [ERROR] }, > [ERROR] { > [ERROR] "address" => [ > [ERROR] ("host" => "master"), > [ERROR] ("server" => "*") > [ERROR] ], > [ERROR] "operation" => "read-resource-description", > [ERROR] "access-control" => "trim-descriptions", > [ERROR] "operations" => true > [ERROR] }, > [ERROR] { > [ERROR] "address" => [("extension" => "*")], > [ERROR] "operation" => "read-resource-description", > [ERROR] "access-control" => "trim-descriptions", > [ERROR] "operations" => true > [ERROR] } > [ERROR] ], > [ERROR] "operation-headers" => {"roles" => "OPERATOR"} > [ERROR] } > {noformat} > leads to > {noformat} > [Host Controller] 16:34:53,544 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-12) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.NullPointerException > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.HostControllerExecutionSupport$Factory.create(HostControllerExecutionSupport.java:167) > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.HostControllerExecutionSupport$Factory.create(HostControllerExecutionSupport.java:181) > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationSlaveStepHandler.addSteps(OperationSlaveStepHandler.java:108) > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:201) > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:124) > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:103) > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:610) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:488) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:257) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:142) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:154) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$2.run(SubjectDoAsHandler.java:96) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$2.run(SubjectDoAsHandler.java:92) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_17] > [Host Controller] at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_17] > [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:92) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:86) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:50) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12] > [Host Controller] at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Host Controller] at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12] > [Host Controller] at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12] > [Host Controller] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > [Host Controller] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > [Host Controller] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master based on a shared lock

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-338: --------------------------------------- Assignee: (was: Emanuel Muckenhuber) This is lower priority now; I think using some sort of a quorum based voting protocol should be the primary approach for auto-promotion of a slave. Anyone who wants this assigned to themselves, please discuss with me first. > Auto-promotion of slave HC to master based on a shared lock > ----------------------------------------------------------- > > Key: WFCORE-338 > URL: https://issues.jboss.org/browse/WFCORE-338 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > Implement an option for a properly configured slave HC to promote itself to master after acquiring an exclusive lock mediated via some persistent store shared between all HCs that are possibly master. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-377) The management API should provide a command to restart only all servers that are in state 'reload-required'

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-377?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-377: --------------------------------------- Assignee: (was: Emanuel Muckenhuber) > The management API should provide a command to restart only all servers that are in state 'reload-required' > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-377 > URL: https://issues.jboss.org/browse/WFCORE-377 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Wolf-Dieter Fink > Labels: cli, domain, management > Fix For: 1.0.0.Beta1 > > > After configuration changes via CLI batch it might be that different processes needs to be restarted. > It is possible to iterate over all servers and check it. > But I think it would be easier to have a command that restart all controllers and servers conditional to the 'relod required' state > - at domain level > - at host level > - at server level > command example : > :restart(ifRequired=true) > :reload(ifRequired=true) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-401) Consider using a "describe" notion for providing the model to slaves on registration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-401?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-401: --------------------------------------- Assignee: Kabir Khan (was: Emanuel Muckenhuber) Kabir, this is the JIRA that resulted in all that host controller stuff you took over. It went in quite a different direction from the description here, which is fine. I'm assigning this to you because you're dealing with the overall task and should know best how to clean up this JRIA (reject, reword to fit the actual work, etc.) > Consider using a "describe" notion for providing the model to slaves on registration > ------------------------------------------------------------------------------------ > > Key: WFCORE-401 > URL: https://issues.jboss.org/browse/WFCORE-401 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 1.0.0.Beta1 > > > When a slave HC registers, the master provides it a copy of the domain-wide model as a DMR tree. This has a weakness in that the Resource impl types that comprise that tree on the master side are not transmitted. If custom Resource impls are used, they may not be recreated on the slave. > Consider instead sending a list of mgmt ops, a la what we do with servers when starting from an HC. > This could potentially be limited to subsystems, with the core model sent as it is now. The core model is handled by core-AS code on the slave side, so we can reasonably ensure that code always uses the correct Resource type. There are places where we already do that. The bigger problem is subsystems. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-282) Wildcard operations that span multiple processes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-282?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFCORE-282: --------------------------------------- Assignee: Brian Stansberry (was: Emanuel Muckenhuber) > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFCORE-282 > URL: https://issues.jboss.org/browse/WFCORE-282 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: as7-ignored > Fix For: 1.0.0.Beta1 > > > Handle host=* and host=y,server=* type operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-272) Provide a "default" role for management users with no other role specified

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-272?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFCORE-272. ------------------------------------- Assignee: Brian Stansberry (was: Emanuel Muckenhuber) Fix Version/s: (was: 1.0.0.CR1) Resolution: Won't Fix I've opened separate issues for the two minor points in my comment of 2014/01/28; otherwise the software is behaving as expected. > Provide a "default" role for management users with no other role specified > -------------------------------------------------------------------------- > > Key: WFCORE-272 > URL: https://issues.jboss.org/browse/WFCORE-272 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Jakub Cechacek > Assignee: Brian Stansberry > Labels: rbac-filed-by-qa > > Currently it seems that when using RBAC provider users with no defined role are unable to read domain model at all. Consequently logging into Admin Console leads to 500 error page. Similar errors in CLI. > In relation to this, it should be considered what is the expected behavior of unsecured management interface. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-554) Unintuitive CLI behavior with 'rbac' enabled and no security-realm configured on mangement interface

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-554: --------------------------------------- Summary: Unintuitive CLI behavior with 'rbac' enabled and no security-realm configured on mangement interface Key: WFCORE-554 URL: https://issues.jboss.org/browse/WFCORE-554 Project: WildFly Core Issue Type: Enhancement Components: CLI Reporter: Brian Stansberry Assignee: Alexey Loubyansky Priority: Minor See WFCORE-272 for background; this issue is to track the CLI part of my comment of 2014/01/28. With no security realm configured on the management interface and the 'rbac' provider chosen, CLI behavior is not very intuitive. You can connect and you get the [standalone@localhost:9990 /] prompt. But if you attempt to do anything that requires server-side work you get various errors indicating you aren't authorized. E.g.: {code} $ bin/jboss-cli.sh -c [standalone@localhost:9990 /] ls Failed to fetch the list of children: { "outcome" => "failed", "failure-description" => "WFLYCTL0313: Unauthorized to execute operation 'composite' for resource '[]' -- \"WFLYCTL0332: Permission denied\"", "rolled-back" => true } {code} In this situation the user is not going to have permissions to do much of anything at all, so it would be good to detect that somehow and respond accordingly. (The lack of a security realm means there is no way to map the user to a role. They can log in but they are not in any role and thus have no permissions.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015