Number of remoting "endpoint" threads growing in EAP when JMX uri is incorrect
Issue
- Customised JBoss Monitoring tool written in Java using JMX, when the JMX uri is incorrect, the number of remoting "endpoint" threads increases after the test has finished. The threads have the names
- "Remoting "endpoint" I/O-1"
- "Remoting "endpoint" task-1"
- "Remoting "endpoint" Accept"
Environment
- JBoss Enterprise Application Platform (EAP)
- 7.0.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.