Thanks for reply.
I haven't investgate JVM yet.
I'm using AMQ as follows conditions, is there a factor that is likely to
take time?
Conditions:
* Using MQTT (QoS=2)
* MQTT Client is Eclipse Paho 1.0.0
* Subscriber's CleanSession is false.
* Number of Subscribers is 1 over.
* Number of To
Anytime a JVM process (such as the ActiveMQ broker) is slow, my
recommendation is to use JVisualVM to perform CPU sampling against the
process to find out where the time is being spent.
20 minutes to shut down the process is a very long time, so I'll be
interested to hear what you discover via tha
I am now using ActiveMQ 5.13.1.
When I tried to stop ActiveMQ, it cost more than 20 minutes.
By checking the activemq.log, it looks like that "uptime XX minutes" were
not outputted and it costs time when trying to stop KahaDB.
Normal:
INFO | Stopping async topic tasks
INFO | Stopped KahaDB
