Wildfly 26: enable worker attributes in io subsystem

392 views
Skip to first unread message

Iason Filippou

unread,
Jan 10, 2024, 7:50:02 AM1/10/24
to WildFly
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.html

Unfortunately, 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

Iason Filippou

unread,
Jan 11, 2024, 5:15:51 AM1/11/24
to WildFly
Forgive me for following up, but I have some new information. After creating a fresh worker instance:

<worker name="newWorker" core-pool-size="32"/>

I restarted my server and got the message:

Message: WFLYCTL0376: Unexpected attribute 'core-pool-size' encountered. Valid attributes are: 'io-threads, task-keepalive, task-core-threads, task-max-threads, stack-size, name'

I'm wondering whether there's a discrepancy in the documentation for the attributes supported by io subsystem workers in version 26 as dictated here: https://docs.wildfly.org/26/wildscribe/subsystem/io/worker/index.html 

Otherwise, is there any way for me to adjust the properties core-pool-size, io-thread-count, max-pool-size and busy-task-thread-count.

Thank you.

Bartosz Baranowski

unread,
Jan 18, 2024, 4:59:35 AM1/18/24
to WildFly

Iason Filippou

unread,
Jan 22, 2024, 8:45:02 AM1/22/24
to Bartosz Baranowski, wil...@googlegroups.com
It actually turns out that some of the properties mentioned in the description are read-only. For example, io-thread-count is a read-only attribute with the corresponding write-enabled attribute being io-threads, and max-pool-size maps to task-max-threads. I have been able to make my use-case work by using the appropriate write-enabled attributes.



--
You received this message because you are subscribed to a topic in the Google Groups "WildFly" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wildfly/PKJugwU2kqw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/d1e9a302-2c6d-40d7-846c-f33365c5a511n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages