Http11NioProtocol connector does not count currentThreadCount and currentThreadsBusy

Environment

• Red Hat JBoss Enterprise Application Platform
  • 6.3.x

Issue

• Using WebSocket and monitoring MBean jboss.web:type=ThreadPool under the following settings.

  /system-property=org.apache.tomcat.util.ENABLE_MODELER:add(value=true)
  /subsystem=web/connector=http:write-attribute(name=protocol,value=org.apache.coyote.http11.Http11NioProtocol)
  

  While those thread metrics are always zeros.

  jboss.web:type=ThreadPool,name=http--0.0.0.0-8080
      currentThreadCount : 0
      currentThreadsBusy : 0
  

Resolution

• Configure a custom executor thread pool, which can be monitored via CLI to some extent per Creating and Monitoring Custom Executor for AJP or Http Connectors in EAP6

Root Cause

• NIO uses a different internal executor that does not expose thread stats
  • This content is not included.BZ-1203510

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.