]
Tomaz Cerar commented on WFLY-6088:
-----------------------------------
worker-thread-pool configuration and mgmt operations are all deprecated.
only real thing that is supported now is <endpoint
worker="worker-reference-to-io-subsystem" />
on which you can get the runtime data.
also worker-thread-pool if configured only proxies configuration to io subsystem.
Remoting worker threads runtime current size, queue size, etc are not
visible
-----------------------------------------------------------------------------
Key: WFLY-6088
URL:
https://issues.jboss.org/browse/WFLY-6088
Project: WildFly
Issue Type: Enhancement
Components: Remoting
Affects Versions: 10.0.0.CR5
Reporter: Brad Maxwell
Assignee: David Lloyd
The remoting subsystem uses a worker-thread-pool which can be configured such as shown
below.
The runtime thread pool information is not exposed when doing read-resource:
{code}
/subsystem=remoting:read-resource(include-runtime=true, recursive=true)
{code}
{code}
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<worker-thread-pool
read-threads="1"
task-core-threads="4"
task-keepalive="60"
task-limit="16384"
task-max-threads="16"
write-threads="1"
/>
<connector name="remoting-connector" socket-binding="remoting"
security-realm="ApplicationRealm"/>
</subsystem>
{code}
In tuning and runtime diagnosis, it would be useful to see the thread pool information
such as the current size, queue-size, largest-thread-count, etc similar to the ejb3
subsystem thread pool:
{code}
/subsystem=ejb3/thread-pool=default:read-resource(include-runtime=true, recursive=true)
"result" => {
"active-count" => 0,
"completed-task-count" => 0L,
"current-thread-count" => 0,
"keepalive-time" => {
"time" => 100L,
"unit" => "MILLISECONDS"
},
"largest-thread-count" => 0,
"max-threads" => 10,
"name" => "default",
"queue-size" => 0,
"rejected-count" => 0,
"task-count" => 0L,
"thread-factory" => undefined
}
{code}