[
https://issues.jboss.org/browse/WFLY-3364?page=com.atlassian.jira.plugin....
]
Tomaz Cerar commented on WFLY-3364:
-----------------------------------
This is correct attribute and it not ignored. There is just some special handling of this
configuration in case version xsd used is 1.0 and upon upgrading it to 1.1 does some
calculation for new defaults.
But in any case behavior you are describing is not part of it.
Can you try CR2 which has some more improvements in this area.
as general guideline, since 8.1 we try to smart calculate thread pool sizes for workers
based on core count you have in your machine.
Also currently task-core-thread setting is not really properly applied, as pool size is
directly filled up to task-max-threads so no need for setting it.
There is no way to change "task-core-threads"
---------------------------------------------
Key: WFLY-3364
URL:
https://issues.jboss.org/browse/WFLY-3364
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: IO
Affects Versions: 8.1.0.CR1
Environment: Ubuntu 14.04
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Reporter: Jay Xu
Assignee: Tomaz Cerar
I tried to change the value of "task-core-threads" in web admin console to 128,
but after restart it is set back to the default value 2. I searched in standalone.xml and
didn't found any "128" in it.
Then I guessed and tried to add an attribute "task-core-threads" in the work
config xml but that made wildfly fail to start with an error like "worker node
doesn't have attribute task-core-threads":
{code:xml}
<worker name="default" io-threads="8"
task-max-threads="512" task-core-threads="128"/>
{code}
So, "task-core-threads" is just a fake? My app server now meets a performance
bottleneck for http connections, how to change task-core-threads's value?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)