mod_cluster throws 'Can't read node' error during long startup

Solution Verified - Updated -

Issue

  • During long start ups (over 5 minutes), mod_cluster throws the following error:

    ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Error [MEM: MEM: Can't read node: {4}] sending command STATUS to proxy localhost/127.0.0.1:6666, configuration will be reset

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 6
    • 7
    • 8
  • mod_cluster

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