[jboss-jira] [JBoss JIRA] (WFLY-5045) Undertow mod_cluster CLI: IllegalArgumentException: value is null on modcluster:read-resource
Michal Karm Babacek (JIRA)
issues at jboss.org
Mon Aug 10 11:50:03 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Karm Babacek reopened WFLY-5045:
---------------------------------------
It appears still broken: *WildFly Full 10.0.0.Beta2-SNAPSHOT*, HEAD:{{f4c6059e42d2}}, *Undertow 1.3.0.Beta7-SNAPSHOT*, HEAD:{{c191afa9f}}. It blocks automation from verifying several other issues.
{noformat}
11:42:36,292 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
("subsystem" => "undertow"),
("configuration" => "filter"),
("mod-cluster" => "modcluster"),
("balancer" => "mycluster"),
("node" => "jboss-eap-7.0-2")
]): java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.addChild(ModelValue.java:128)
at org.jboss.dmr.ModelNode.add(ModelNode.java:1239)
at org.jboss.dmr.ModelNode.add(ModelNode.java:1016)
at org.wildfly.extension.undertow.filters.ModClusterNodeDefinition$19.handleNode(ModClusterNodeDefinition.java:302)
at org.wildfly.extension.undertow.filters.ModClusterNodeDefinition$AbstractNodeOperation.execute(ModClusterNodeDefinition.java:343)
at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174)
at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137)
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:248)
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AvailableResponseWrapper.execute(GlobalOperationHandlers.java:701)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:846)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:637)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:362)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1272)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:394)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:207)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:129)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:151)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:147)
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:92)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:147)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
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}
Isn't there anything fishy about the command used in Setup in Description?
> Undertow mod_cluster CLI: IllegalArgumentException: value is null on modcluster:read-resource
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-5045
> URL: https://issues.jboss.org/browse/WFLY-5045
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Alpha6
> Environment: EAP 7.0.0.DR7, Undertow 1.3.0.Beta4
> Reporter: Michal Karm Babacek
> Assignee: Stuart Douglas
> Priority: Blocker
> Fix For: 10.0.0.Beta1
>
>
> *Undertow 1.3.0.Beta3*, *EAP 7.0.0.DR6* worked perfectly with {{modcluster:read-resource}} recursive operations:
> h3. Setup
> # Add socker binding: {{/socket-binding-group=standard-sockets/socket-binding=mod-cluster-adv:add(multicast-address=224.0.1.105,port=65530)}}
> # Configure mod_cluster proxy: {{/subsystem=undertow/configuration=filter/mod-cluster=modcluster:add(advertise-frequency=10000,advertise-path=/,advertise-protocol=http,advertise-socket-binding=mod-cluster-adv,management-socket-binding=http,management-access-predicate=undefined,broken-node-timeout=10,cached-connections-per-thread=5,connection-idle-timeout=60,connections-per-thread=10,health-check-interval=10000,max-request-time=-1,request-queue-size=10,security-key=undefined,security-realm=undefined,worker=default)}}
> # Add mod_cluster filter: {{/subsystem=undertow/server=default-server/host=default-host/filter-ref=modcluster:add()}}
> # As soon as worker connects: {noformat}UT005053: Registering node localhost, connection: ajp://karm.brq.redhat.com:8019/?#
> UT005045: Registering context /clusterbench, for node localhost{noformat}, we try to list the configuration:
> # List configuration including runtime recursively: {{/subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100)}}
> h3. Error
> The output of the last aforementioned command with *EAP 7.0.0.DR6, Undertow 1.3.0.Beta3* is:{noformat}
> {
> "outcome" => "success",
> "result" => {
> "advertise-frequency" => 10000,
> "advertise-path" => "/",
> "advertise-protocol" => "http",
> "advertise-socket-binding" => "mod-cluster-adv",
> "broken-node-timeout" => 10,
> "cached-connections-per-thread" => 5,
> "connection-idle-timeout" => 60,
> "connections-per-thread" => 10,
> "health-check-interval" => 10000,
> "management-access-predicate" => undefined,
> "management-socket-binding" => "http",
> "max-request-time" => -1,
> "request-queue-size" => 10,
> "security-key" => undefined,
> "security-realm" => undefined,
> "worker" => "default",
> "balancer" => {"mycluster" => {"node" => {"localhost" => {
> "load" => 81,
> "status" => "NODE_UP",
> "context" => {"/clusterbench" => {
> "requests" => 0,
> "status" => "enabled"
> }}
> }}}}
> }
> }{noformat} whereas with *EAP 7.0.0.DR7, Undertow 1.3.0.Beta4*; it is: {noformat}ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("subsystem" => "undertow"),
> ("configuration" => "filter"),
> ("mod-cluster" => "modcluster"),
> ("balancer" => "mycluster")
> ]): java.lang.IllegalArgumentException: value is null
> at org.jboss.dmr.ModelNode.<init>(ModelNode.java:162)
> at org.wildfly.extension.undertow.filters.ModClusterBalancerDefinition$3.handleNode(ModClusterBalancerDefinition.java:117)
> at org.wildfly.extension.undertow.filters.ModClusterBalancerDefinition$AbstractBalancerOperation.execute(ModClusterBalancerDefinition.java:173)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174)
> at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:248)
> at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AvailableResponseWrapper.execute(GlobalOperationHandlers.java:701)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:841)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:632)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:357)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1235)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:223)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:207)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:129)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:151)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:147)
> 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:92)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:147)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
> 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}It is noteworthy that *until* any worker joins the balancer, the operation works just fine (DR7, Beta4): {noformat}{
> "outcome" => "success",
> "result" => {
> "advertise-frequency" => 10000,
> "advertise-path" => "/",
> "advertise-protocol" => "http",
> "advertise-socket-binding" => "mod-cluster-adv",
> "broken-node-timeout" => 10,
> "cached-connections-per-thread" => 5,
> "connection-idle-timeout" => 60,
> "connections-per-thread" => 10,
> "health-check-interval" => 10000,
> "management-access-predicate" => undefined,
> "management-socket-binding" => "http",
> "max-request-time" => -1,
> "request-queue-size" => 10,
> "security-key" => undefined,
> "security-realm" => undefined,
> "use-alias" => true,
> "worker" => "default",
> "balancer" => undefined
> }
> }{noformat}
> I see this issue as a {color:red}Blocker{color}, because it not only breaks all current test automation but also renders the Undertow mod_cluster proxy CLI hardly usable for any administration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list