EAP 7 Undertow/XNIO max-connections behavior changes since EAP 7.0.4

Solution Unverified - Updated -

Issue

  • The following max-connections and tcp-backlog are configured in http-listener inside undertow subsystem in EAP 7:

    <http-listener name="default" socket-binding="http" redirect-socket="https" max-connections="100" tcp-backlog="100"/>
    
  • As far as I tested, the behavior is different after EAP 7.0.4 or later:

    • Until EAP 7.0.3, a new connection which exceeds max-connections is queued in the TCP backlog which size is specified by tcp-backlog.
    • Since EAP 7.0.4, EAP 7 does not queue a new connection which exceeds max-connections but it immediately closes the exceeded connections.

What caused this behavior change?

Environment

  • Red Hat 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