JBoss EAP 7 fails to parse request due to BadRequestException from HTTP verb handling

Solution Verified - Updated -

Issue

  • In some cases, we see 400 responses from JBoss. Enabling DEBUG logging for io.undertow.request.io revealed the following io.undertow.util.BadRequestException:
DEBUG [io.undertow.request.io] (default I/O-2) UT005014: Failed to parse request: io.undertow.util.BadRequestException
    at io.undertow.server.protocol.http.HttpRequestParser$$generated.handleHttpVerb(Unknown Source)
    at io.undertow.server.protocol.http.HttpRequestParser.handle(HttpRequestParser.java:243)
    at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:187)
    at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
    at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59)
    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:1175)
    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.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content