Abrupt HTTP2 connection close after updating to EAP 7.2.9 or 7.3.2+

Solution Verified - Updated -

Issue

  • After updating to EAP 7.2.9 or 7.3.2+, we see some requests consistently fail over HTTP2 and get no response from JBoss. The connection is abruptly closed and we see the following exception logged at a DEBUG level:
DEBUG [io.undertow.request.io] (default I/O-3) Sending rststream on channel Http2Channel peer 127.0.0.1:60903 local /127.0.0.1:8443[ No Receiver [] -- [] -- []] stream 85: java.nio.channels.ClosedChannelException
    at io.undertow.protocols.http2.Http2Channel.sendRstStream(Http2Channel.java:1057)
    at io.undertow.server.protocol.http2.Http2ReceiveListener.handleRequests(Http2ReceiveListener.java:145)
    at io.undertow.server.protocol.http2.Http2ReceiveListener.handleEvent(Http2ReceiveListener.java:125)
    at io.undertow.server.protocol.http2.Http2ReceiveListener.handleEvent(Http2ReceiveListener.java:68)
    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:952)
    at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:932)
    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
    at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1211)
    at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
    at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 7.2.9
    • 7.3.2+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions