Issue

• We changed our http management interface to use https. Now accessing the console is much slower. We consistently see a ~30 second delay. Thread dumps show the console access hanging here reading the request from the client:

"HttpManagementService-threads - 1" prio=10 tid=0x00007faa6c2e0800 nid=0x2cb7 runnable [0x00007faaa431c000]
   java.lang.Thread.State: RUNNABLE
    at sun.nio.ch.FileDispatcher.read0(Native Method)
    at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
    at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
    at sun.nio.ch.IOUtil.read(IOUtil.java:171)
    at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:245)
    - locked <0x00000000e9b037e8> (a java.lang.Object)
    at org.jboss.sun.net.httpserver.SSLStreams$EngineWrapper.recvAndUnwrap(SSLStreams.java:340)
    - locked <0x00000000ea0f6a68> (a java.lang.Object)
    at org.jboss.sun.net.httpserver.SSLStreams.recvData(SSLStreams.java:415)
    at org.jboss.sun.net.httpserver.SSLStreams$InputStream.read(SSLStreams.java:530)
    at org.jboss.sun.net.httpserver.SSLStreams$InputStream.read(SSLStreams.java:599)
    at org.jboss.sun.net.httpserver.Request.readLine(Request.java:86)
    at org.jboss.sun.net.httpserver.Request.<init>(Request.java:56)
    at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:571)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    at org.jboss.threads.JBossThread.run(JBossThread.java:122)

• TCP dumps also confirm JBoss is waiting on the client as once it receives some delayed packets from the client this thread progresses.