mod_cluster returns 404s following the restart of a crashed or killed JBoss node
Issue
- If a JBoss node is not gracefully shutdown (if it crashed or was killed), then we see some 404s from mod_cluster when that node is restarted. It looks like mod_cluster starts sending requests to the restarting JBoss node before the apps have deployed.
- Why JBoss EAP instances will not rejoin mod_cluster after its restart?
Environment
- JBoss Enterprise Application Platform (EAP)
- JBoss Enterprise Web Server (EWS)
- Apache httpd
- mod_cluster
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
