Red Hat AMQ 7.x process frozen with message error "Root exception is java.net.SocketException: Too many open files"

Solution Verified - Updated -

Issue

  • The clients are not able to produce or consume any messages from the Red Hat AMQ Broker because the process is hung with the java.net.SocketException: Too many open files error in the logs.

  • When running command netstat -anp it returns that the port is still bound to the protocol (in this case amqp protocol on port 61616), even when the server is already frozen, so even with failover configured it does not work as expected:

    # netstat -anp
    
    [...]
    tcp        0      0 10.28.100.7:61616       0.0.0.0:*               LISTEN
    [...]
    
  • The artemis.log file is showing error messages like the following:

    ERROR [org.apache.activemq.artemis.core.server] AMQ224084: Failed to open context: javax.naming.CommunicationException:... [Root exception is java.net.SocketException: Too many open files]
    

Environment

  • Red Hat AMQ
    • 7.x
  • Red Hat Enterprise Linux (RHEL)
    • 7.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