-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.CR2
When adding an property with invalid name to the remoting connector and subsequent reload, the server fails to start.
See server stack-trace:
2017-09-27 15:23:08,755 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "remoting"), ("connector" => "bbb") ]): java.lang.IllegalArgumentException: XNIO000005: No such field named "bbb" in class org.xnio.Options at org.xnio.Option.fromString(Option.java:157) at org.jboss.as.remoting.ConnectorUtils.addOptions(ConnectorUtils.java:164) at org.jboss.as.remoting.ConnectorUtils.getFullOptions(ConnectorUtils.java:82) at org.jboss.as.remoting.ConnectorAdd.launchServices(ConnectorAdd.java:82) at org.jboss.as.remoting.ConnectorAdd.performRuntime(ConnectorAdd.java:78) at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337) at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:976) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:446) at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:386) 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:748) at org.jboss.threads.JBossThread.run(JBossThread.java:320)
- clones
-
WFCORE-3908 Server fails to start after setting invalid property of remoting connector
- Resolved
- is incorporated by
-
JBEAP-14910 (7.1.z) Upgrade WildFly Core to 3.0.17.Final-redhat-1
- Closed