1 Reply Latest reply on Aug 28, 2016 2:04 PM by Oluwasegun Diyan

    Getting an error MODCLUSTER000043, not sure what to do.

    Anthony Galati Newbie

      I am a developer that uses JBOSS EAP 6.2  in a clustered environment with 2 apache servers and a load balancer in front of that.


      I am see the following error a lot on not sure where to point the System Admins too.


      [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000043: Failed to send STATUS to java.net.SocketTimeoutException: Read timed out


      What does this error mean?

        • 1. Re: Getting an error MODCLUSTER000043, not sure what to do.
          Oluwasegun Diyan Newbie

          Hi. I'm experiencing the same exception and was wondering if you ever got to resolve this?


          I have a domain + Apache + Modcluster with several hosts. I started getting this error the moment I refactored some slow processes to run asynchronously as opposed to their former synchronous architecture by using the @asynchronous annotation. I'm guessing Wildfly is spinning quite a huge number of threads to cater for the number of jobs being produced and is somehow causing the send status of the node to timeout.


          Please advise.