[jboss-jira] [JBoss JIRA] (WFLY-2220) Unable to reload server after adding role and executing :reload
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Fri Oct 4 10:30:02 EDT 2013
[ https://issues.jboss.org/browse/WFLY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809479#comment-12809479 ]
RH Bugzilla Integration commented on WFLY-2220:
-----------------------------------------------
Ladislav Thon <lthon at redhat.com> made a comment on [bug 1015585|https://bugzilla.redhat.com/show_bug.cgi?id=1015585]
Description of problem:
When you add a new role mapping and then request a server restart via the management interface, your server will crash.
Version-Release number of selected component (if applicable):
EAP 6.2.0.ER4
How reproducible:
Always
Steps to Reproduce:
1. start a new server
./bin/standalone.sh
2. run CLI
./bin/jboss-cli.sh -c
3. add a new role mapping
/core-service=management/access=authorization/role-mapping=Operator:add()
4. restart the server
:reload
Actual results:
The server restarts fine with no error message.
Expected results:
The server "crashes" with an error message:
16:24:48,601 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([
("core-service" => "management"),
("access" => "authorization"),
("role-mapping" => "SuperUser")
]): java.lang.UnsupportedOperationException
at java.util.Collections$UnmodifiableMap.put(Collections.java:1283) [rt.jar:1.6.0_45]
at org.jboss.as.controller.access.management.WritableAuthorizerConfiguration.addRoleMappingImmediate(WritableAuthorizerConfiguration.java:163) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.domain.management.access.RoleMappingAdd$1.execute(RoleMappingAdd.java:76) [jboss-as-domain-management-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:624) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:502) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:285) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:280) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:277) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:288) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.server.ServerService.boot(ServerService.java:349) [jboss-as-server-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.server.ServerService.boot(ServerService.java:324) [jboss-as-server-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:250) [jboss-as-controller-7.3.0.Final-redhat-7.jar:7.3.0.Final-redhat-7]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
16:24:48,609 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry]
16:24:48,611 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
16:24:48,617 INFO [org.jboss.as.controller] (MSC service thread 1-6) JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.remoting.endpoint.management (no longer required)
16:24:48,619 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: JBoss EAP 6.2.0.Beta1 (AS 7.3.0.Final-redhat-7) stopped in 4ms
Additional info:
Note that it's not even necessary to enable the "rbac" provider. Also note that after the server crashes, it can be started just fine, suggesting that there's probably something wrong in the runtime model.
> Unable to reload server after adding role and executing :reload
> ---------------------------------------------------------------
>
> Key: WFLY-2220
> URL: https://issues.jboss.org/browse/WFLY-2220
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 8.0.0.Beta1
>
>
> Start a clean build of WildFly 8 and execute the following commands in the CLI: -
> {code}
> [standalone at localhost:9990 /connect
> [standalone at localhost:9990 /] ./core-service=management/access=authorization/role-mapping=Operator:add
> {"outcome" => "success"}
> [standalone at localhost:9990 /] :reload
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone at localhost:9990 /]
> {code}
> Results in the following error and the server shuts down: -
> {code}
> 15:15:02,275 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 15:15:02,278 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("access" => "authorization"),
> ("role-mapping" => "SuperUser")
> ]): java.lang.UnsupportedOperationException
> at java.util.Collections$UnmodifiableMap.put(Collections.java:1342) [rt.jar:1.7.0_17]
> at org.jboss.as.controller.access.management.WritableAuthorizerConfiguration.addRoleMappingImmediate(WritableAuthorizerConfiguration.java:163) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.domain.management.access.RoleMappingAdd$1.execute(RoleMappingAdd.java:76) [wildfly-domain-management-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:609) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:487) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:321) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:290) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:252) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> 15:15:02,287 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry]
> 15:15:02,290 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 15:15:02,297 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" stopped in 2ms
> {code}
> What is interesting is that the server is manually startable to something has gone wrong regarding resetting the runtime state of RBAC at the time of the reload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list