I would rate the stability a five out of ten because sometimes it gets stuck, and we have to restart it.  We often need to restart it.

In our organization, maybe close to 2,000 people used this solution.

There are stability issues with this solution. We lose connection at times. When the application is down, we have to manually patch our servers, maintain them, and restart them. This is a cumbersome manual process.

ActiveMQ has been a stable tool for us, with no downtime or critical technical issues so far.

I have not experienced any unstable situations.

The solution is fairly stable. But we are using it in Development, not in production, so I'm probably not the best judge of stability in general.

ActiveMQ is a very stable solution.

The product is very stable. We haven't had any issues so far.

We did not encounter any stability issues.

We have not had any stability issues.

There were stability issues. With a network of brokers, you get a lot of issues, especially if you have the publisher and consumer using the same channel or connection, on different topics and/or queues. It’s causing a lot of issues and weirdness.

The solution's stability needs improvement.

I would rate the tool's stability a seven-point five out of ten. The tool is highly stable.

I have not used it heavily in a production environment, but at the moment, I don't have any issues to report. 

I am currently working with some clients to investigate some stability issues they are experiencing, but it could be the result of the way it was implemented.

In terms of performance, I have not any extensive performance tests as a comparison.

I have looked at other messaging providers, and I don't think that it's any worse than any other solution available. I think that it's reasonable.

We did not encounter many stability issues.

We have not encountered any stability issues.

We have not yet encountered any stability issues.

We didn’t encounter anything that wasn't a result of our own misguided uses.

We have not encountered any stability issues.

There were no problems with stability.

We ran into various stability problems with our implementations over the years. We also ran into a few problems related to bugs.

One of the bugs was a memory leak from the KahaDB log files. As uptime accumulated, it eventually triggered one of the artificial limitations on the disk space used by KahaDB.

We have not encountered any stability issues.