AJP Connections which status are CLOSE_WAIT never disappear.

Solution In Progress - Updated -

Issue

When org.apache.coyote.ajp.DEFAULT_CONNECTION_TIMEOUT option apply to EAP side, idle AJP connections are disconnected by EAP.
Then, the status of connections on EAP side are changed to FIN_WAIT and sometimes later it is gone. However, the other side(apache) are changed to CLOSE_WAIT but never disappear.

Is it normal? Is there a way to control it with some configuration?

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 6.3.3

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