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 fileserror in the logs.
When running command
netstat -anpit returns that the port is still bound to the protocol (in this case
amqpprotocol 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 [...]
artemis.logfile 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]
- Red Hat AMQ
- Red Hat Enterprise Linux (RHEL)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.