Hello,
My team runs Wildfly-26.1.2.Final. Our standalone file has this minimal property:
<subsystem xmlns="urn:jboss:domain:io:3.0">
<worker name="default"/>
<buffer-pool name="default"/>
</subsystem>
I have been tasked with investigating how our setup is affected by some attributes to the worker property, such as max-pool-size, task-max-threads, etc. The full list for our version of Wildfly is available here:
https://docs.wildfly.org/26/wildscribe/subsystem/io/worker/index.htmlUnfortunately, it seems that adding any attribute to the worker, for example max-pool-size:
<subsystem xmlns="urn:jboss:domain:io:3.0">
<worker name="default" max-pool-size="32"/>
<buffer-pool name="default"/>
</subsystem>
results in the server crashing:
JBoss Modules version 2.0.2.Final
JBoss MSC version 1.4.13.Final
JBoss Threads version 2.4.0.Final
WFLYSRV0049: WildFly Full 26.1.2.Final (WildFly Core 18.1.2.Final) starting
WFLYCTL0456: System property "logback.configurationFile" is already set in the <system-properties> section of the configuration file. The value set in the command line will be overridden by that value.
ELY00001: WildFly Elytron version 1.19.1.Final
OPVDX003: No schemas available from C:\XMProjects\jThalesServer\wildfly-26.1.2.Final\docs\schema - disabling validation error pretty printing
WFLYSRV0055: Caught exception during boot
WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone.xml
WFLYSRV0050: WildFly Full 26.1.2.Final (WildFly Core 18.1.2.Final) stopped in 8ms
I have also tried several other properties, including randomly named ones not mentioned in that link, and I get the same result. What am I doing wrong here? Any advice appreciated.
Jason