Extra info would help here - Add info below

[robbinmav]

Document: Thread pool tuning
http://openliberty.io/docs/latest/thread-pool-tuning.html

"However, in rare cases, you might need to explicitly configure an executor element and adjust the coreThreads and maxThreads attributes to particular values in your server.xml file."

This doesn't tell me how to gain information about the thread pool usage so I can assess what the values should be.

this needs to have a similar function to the output that the tWAS code sets when the thread heatbeat monitoring is configured:

Configuring the Websphere Thread Pool statistics to log key thread counts and their status

Servers > Application Servers > Server Name > Troubleshooting > Logging and Tracing > Configuration > General Properties > Log Level Detail

:Runtime.ThreadMonitorHeartbeat=detail

Having this information would help administrators understand the thread usage and the resource implications e.g. amount of RAM requred.

The thread pools stats would need to be provided as its own option e.g. administrators should not need to wade through lots of other log/debug information to see these statistics

[dmuelle]

Thanks for this feedback @robbinmav. We don't currently have a comparable setting for Liberty so this would be an enhancement to the product rather than the docs.

I can transfer this as a feature request to the main https://github.com/OpenLiberty/open-liberty/ repo. Any more info about what you would like to see would be helpful, given that there aren't separate thread-pools to manage as in tWAS