The APR connector can crash after a CLI reload. The AprEndpoint destroys the APR serversock pool when it is stopped by the reload, but it doesn't specifically tear down every keepalive connection. Thus prior keepalive connections get to last across the reload in a likely bad state, allowing for a crash when those old connections are reused after the reload. In a conventional shutdown, the lack of that clean up isn't generally concerning since JBoss stops then anyway. But the reload can allow for unaccounted for issues.
Examples of the crash points seen after a reload: Stack: [0x00007f9055d44000,0x00007f9055e45000], sp=0x00007f9055e43748, free space=1021k Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.apache.tomcat.jni.Socket.sendb(JLjava/nio/ByteBuffer;II)I+0 j org.apache.coyote.ajp.AjpAprProcessor.process(J)Lorg/apache/tomcat/util/net/AprEndpoint$Handler$SocketState;+123 j org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(J)Lorg/apache/tomcat/util/net/AprEndpoint$Handler$SocketState;+22 j org.apache.tomcat.util.net.AprEndpoint$Worker.run()V+167 j java.lang.Thread.run()V+11 v ~StubRoutines::call_stub Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.apache.tomcat.jni.Socket.recvbb(JII)I+0 j org.apache.coyote.ajp.AjpAprProcessor.readt(IZ)Z+112 j org.apache.coyote.ajp.AjpAprProcessor.readMessage(Lorg/apache/coyote/ajp/AjpMessage;ZZ)Z+14 j org.apache.coyote.ajp.AjpAprProcessor.process(J)Lorg/apache/tomcat/util/net/AprEndpoint$Handler$SocketState;+73 j org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(J)Lorg/apache/tomcat/util/net/AprEndpoint$Handler$SocketState;+22 j org.apache.tomcat.util.net.AprEndpoint$SocketWithOptionsProcessor.run()V+76
Triage Feb 20: closed as can't fix.