Troubleshooting & Optimizing mod_jk

Solution Verified - Updated -

Issue

  • There are errors in the mod_jk.log file such as:
    Tomcat is down or refused connection
    [error] ajp\_send\_request::jk\_ajp\_common.c  (1585): (node2) connecting to  backend failed. Tomcat is probably not started or is listening on the  wrong port (errno=110)
    [error] ajp\_send\_request::jk\_ajp\_common.c (1467): (node2) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
    [error] ajp_send_request::jk_ajp_common.c (1630): (node2) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=113)
  • There are apparent hangs where the webpage will just sit there and not respond or error out.
  • mod_jk is operating very slowly
  • Web requests are freezing, hanging, or very slow to respond

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.x
    • 6.x
  • Red Hat JBoss Enterprise Web Server (EWS)
  • mod_jk 1.2.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