WFLYCTL0013: Operation ("apply-remote-domain-model") failed - address: ([]): java.lang.IllegalArgumentException: Parameter 'step' may not be null

[Olivier Masseau]

Hello,

This morning my slave node could not connect anymore to the deomain controller for an unknown reason. I cannot understand why.

I get this in loops in the host-controller.log of the slave :

2023-11-08 08:54:55,753 ERROR [org.jboss.as.host.controller] (Host Controller Service Threads - 3515) WFLYHC0143: Failed to apply domain-wide configuration from master host controller. Operation outcome: failed. Failure description "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: Parameter 'step' may not be null"

2023-11-08 08:54:55,754 WARN  [org.jboss.as.host.controller] (Host Controller Service Threads - 1113) WFLYHC0146: Could not discover master using discovery option StaticDiscovery{protocol=remote+http,host=172.19.196.143,port=9990}. Error was: 1-$-

2023-11-08 08:54:55,754 WARN  [org.jboss.as.host.controller] (Host Controller Service Threads - 1113) WFLYHC0147: No domain controller discovery options remain.

2023-11-08 08:55:10,755 INFO  [org.jboss.as.host.controller] (Host Controller Service Threads - 1113) WFLYHC0150: Trying to reconnect to master host controller.

2023-11-08 08:55:10,915 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 3517) WFLYCTL0013: Operation ("apply-remote-domain-model") failed - address: ([]): java.lang.IllegalArgumentException: Parameter 'step' may not be null

    at org.wildf...@1.5.4.Final//org.wildfly.common.Assert.checkNotNullParamChecked(Assert.java:71)

    at org.wildf...@1.5.4.Final//org.wildfly.common.Assert.checkNotNullParam(Assert.java:49)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractOperationContext.addStep(AbstractOperationContext.java:316)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractOperationContext.addStep(AbstractOperationContext.java:301)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractOperationContext.addStep(AbstractOperationContext.java:268)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.domain.controller.operations.SyncServerStateOperationHandler$1.execute(SyncServerStateOperationHandler.java:121)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1040)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:779)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:537)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.DomainModelControllerService.access$1300(DomainModelControllerService.java:211)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor$1.lambda$apply$0(DomainModelControllerService.java:1460)

    at org.jboss.a...@15.0.1.Final//org.jboss.as.controller.access.InVmAccess.runInVm(InVmAccess.java:63)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor$1.apply(DomainModelControllerService.java:1460)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor$1.apply(DomainModelControllerService.java:1457)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.SecurityActions$Execution$1.execute(SecurityActions.java:77)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.SecurityActions.privilegedExecution(SecurityActions.java:47)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:1463)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.RemoteDomainConnectionService.applyRemoteDomainModel(RemoteDomainConnectionService.java:603)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.RemoteDomainConnectionService.access$1200(RemoteDomainConnectionService.java:138)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.RemoteDomainConnectionService$3.applyDomainModel(RemoteDomainConnectionService.java:546)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.RemoteDomainConnection.applyDomainModel(RemoteDomainConnection.java:327)

    at org.jboss.as.h...@15.0.1.Final//org.jboss.as.host.controller.RemoteDomainConnection$RegisterSubsystemsRequest$1.execute(RemoteDomainConnection.java:470)

    at org.jboss....@15.0.1.Final//org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)

    at org.jboss....@15.0.1.Final//org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)

    at org.jbos...@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)

    at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)

    at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)

    at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)

    at java.base/java.lang.Thread.run(Thread.java:834)

    at org.jbos...@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)

The master is up and running well.

Calling the console of the domain (http://172.19.196.143:9990/) through a browser on the slave machine works so it is not a network problem.

[Olivier Masseau]

Note: Running Wildfly 23.

[Yeray Borges Santana]

Hello Oliver,

Likely you could be hitting https://issues.redhat.com/browse/WFCORE-6375 which was released with WildFly 30.0.0.Final.

It could happen if you have restarted your Domain Controller and you have made changes that need to be synchronized when the secondary hosts are joining back to the domain. 

If so, the mitigation is to avoid having managed servers stopped on your secondary hosts when they are registering into the domain or avoid redeployments and instead undeploy and deploy your applications.

Hope it helps,

Regards

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/21fdfea8-cc25-4eee-b959-4eb376359d30n%40googlegroups.com.