-
Enhancement
-
Resolution: Done
-
Major
-
2.0.7.Final
-
None
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:
/subsystem=remoting:read-resource(include-runtime=true, recursive=true)
<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>
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:
/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 }
- is blocked by
-
WFCORE-2135 Upgrade xnio to 3.4.3.Final
-
- Resolved
-
- is related to
-
WFLY-11255 EE Concurrency Utilities Managed Executors / Thread Pool runtime stats
-
- Closed
-
