[jboss-jira] [JBoss JIRA] (WFCORE-2314) Incorrectly closed header results in not helping IllegalArgumentException with null message
Brian Stansberry (JIRA)
issues at jboss.org
Mon Feb 20 22:18:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved JBEAP-8976 to WFCORE-2314:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2314 (was: JBEAP-8976)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
(was: User Experience)
Affects Version/s: (was: 7.1.0.DR11)
> Incorrectly closed header results in not helping IllegalArgumentException with null message
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-2314
> URL: https://issues.jboss.org/browse/WFCORE-2314
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Reporter: Radim Hatlapatka
> Assignee: Brian Stansberry
> Labels: user_experience
>
> Calling {{/core-service=management/security-realm=bbb:add(){allow-resource-service-restart=true)}} (notice incorrectly closed allow-resource-service-restart with ")" instead of "}" results in
> {noformat}
> [standalone at localhost:9990 /] /core-service=management/security-realm=bbb:add(){allow-resource-service-restart=true)
> {
> "outcome" => "failed",
> "failure-description" => "java.lang.IllegalArgumentException:null"
> }
> {noformat}
> with this message in server.log:
> {noformat}
> 14:20:12,440 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 10) WFLYCTL0403: Unexpected failure during execution of the following operation(s): [{
> "address" => [
> ("core-service" => "management"),
> ("security-realm" => "bbb")
> ],
> "operation" => "add",
> "operation-headers" => {
> "allow-resource-service-restart" => "true)",
> "caller-type" => "user",
> "access-mechanism" => "NATIVE"
> }
> }]: java.lang.IllegalArgumentException
> at org.jboss.dmr.StringModelValue.asBoolean(StringModelValue.java:157)
> at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:267)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:346)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:240)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:193)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:212)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:185)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157)
> 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)
> {noformat}
> The IllegalArgumentException should point in the message what argument is incorrect and what is wrong. Printing only null doesn't help much.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list