Troubleshooting Amazon MQ
This section describes common issues you might encounter when using Amazon MQ brokers, and the steps you can take to resolve them.
Contents
- Troubleshooting: General
- Troubleshooting: Amazon MQ for ActiveMQ
- I can't see general or audit logs for my broker in CloudWatch Logs even though I’ve activated logging.
- After broker restart or maintenance window, I can't connect to my broker even though the status is RUNNING. Why?
- I see some of my clients connecting to the broker, while others are unable to connect.
- I'm seeing exception org.apache.jasper.JasperException: An exception occurred processing JSP page on the ActiveMQ console when performing operations.
- Troubleshooting: Amazon MQ for RabbitMQ
- Troubleshooting: Amazon MQ action required codes
-
Amazon MQ for RabbitMQ: High memory alarm
- Diagnosing high memory alarm using the RabbitMQ web console
- Diagnosing high memory alarm using Amazon MQ metrics
- Addressing high memory alarm
- Reducing the number of connections and channels
- Addressing paused queue synchronizations in cluster deployments
- Addressing restart loops in single-instance brokers
- Preventing high memory alarms
- Amazon MQ for RabbitMQ: Invalid Amazon Key Management Service Key
- Amazon MQ for ActiveMQ: Deleted Elastic Network Interface alarm
- Amazon MQ for ActiveMQ: Broker Out Of Memory alarm
- Amazon MQ for RabbitMQ: Disk limit alarm
-
Amazon MQ for RabbitMQ: High memory alarm