JBoss periodically hits "Can't read node" error when proxying over http with mod_cluster

Solution Verified - Updated -

Issue

  • We periodically see errors like the following and requests fail at the httpd/mod_cluster layer when proxying over http with mod_cluster 1.3:
ERROR [ContainerBackgroundProcessor[StandardEngine[jboss.web]]] MODCLUSTER000042: Error MEM sending STATUS command localhost/127.0.0.1:6666, configuration will be reset: MEM: Can't read node

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 6.x
    • 7.x
  • JBoss Web Server (JWS) 3.x
  • JBoss Core Services
  • httpd 2.4.x
  • mod_cluster 1.3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.