Hello Wendell- It is very difficult to assist in troubleshooting over an email list. A couple general tips:
1. Be sure app teams test non-happy path scenarios — failover, retry, redelivery, bad messages, etc. 2. Be sure app teams have Connection Factories configured with appropriate timeout settings for the network 3. Review application logs for any error messages that indicate root cause 4. Review broker logs for any error message that may point to root cause 5. Be sure the ActiveMQ broker is a reasonably current version (5.15.15 or higher) 6. Be sure the ActiveMQ client libraries are a reasonably current version Keep in mind that a restart also causes the application to reconnect to the broker. The majority of issues like this tend to be “distributed computing” related, and not broker problems. Thanks, Matt Pavlovich > On Oct 28, 2022, at 8:48 AM, Wendell Hatcher <wendellhatcher1...@gmail.com> > wrote: > > Hello, I am fairly knew to ActiveMQ troubleshooting message queues. We have > to restart our ActiveMQ services which connect to a backend muleESB almost > daily for certain queues. We try dumping the messages but the queues are > stuck and will not release the data. A restart of the services seems to > clear the queues but this occurs frequently. > > > Is there anything we can do to prevent this from happening? Troubleshooting > steps to take to narrow down why this keeps occurring as well? > > > -Wendell
