Customer wrote a monitoring tool for JBoss which uses JMX, his env is EAP 7.0.6. When the jmx url is set to an invalid port, we are noticing the number of threads growing in EAP as the test run over the time. I can replicate his issue on my machine. The threads are

"Remoting "endpoint" I/O-1"
"Remoting "endpoint" task-1"
"Remoting "endpoint" Accept"

For example:

"Remoting "endpoint" Accept" #878 daemon prio=5 os_prio=0 tid=0x00007fe6dc1cf800 nid=0x4c2f runnable [0x00007fe66fbfe000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)

• locked <0x00000000e6f3a1f8> (a sun.nio.ch.Util$3)
• locked <0x00000000e6f3a1e8> (a java.util.Collections$UnmodifiableSet)
• locked <0x00000000e6f3a0d0> (a sun.nio.ch.EPollSelectorImpl)
  at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
  at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
  at org.xnio.nio.WorkerThread.run(WorkerThread.java:515)

for the 200 loop, I can see 798 live threads, and 616 Daemon threads in JBoss.

The test scripts are:

run_test.sh is

for i in

; do curl -H "Content-Type: application/json" -X POST --data-binary "@jbmonitorRequestdata.txt" test1.redhat.com:8080/infra.jbossmonitor-0.0.4/beaninfo; done

and the jbmonitorRequestdata.txt is

[
{
"user": "admin",
"password": "password",
"url": "service:jmx:remote+http://test1.redhat.com:1990",
"measurements":

,
"tags":

}
]

I will attach the customer code to this jira