Description
The description of "largest-thread-count" is
=> "The largest number of threads that have ever simultaneously been in the pool."
But the behaviour at runtime shows that it is handled similar to task-count.
If only one thread is used it will increased for every invocation until max-threads.
As result the largest-thread-count is == max-threads after a short time.
The helpful metrict to check whether the threads are exhaused is missing!
Attachments
Issue Links
- clones
-
JBEAP-11678 [GSS](7.1.0) EJB subsystem thread-pool statistics largest-thread-count is counting threads instead of show the peak of parallel use
- Closed
- is blocked by
-
WFLY-8966 EJB subsystem thread-pool statistics largest-thread-count is counting threads instead of show the peak of parallel use
- Closed