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 that investigation. Tim On Wed, Mar 7, 2018 at 10:15 PM, t-watana <watanabe.tak...@jp.fujitsu.com> wrote: > 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 > INFO | Apache ActiveMQ 5.13.1 (broker0, > ID:VM023666-42447-1520313521387-0:1) uptime 44 minutes > INFO | Apache ActiveMQ 5.13.1 (broker0, > ID:VM023666-42447-1520313521387-0:1) is shutdown > > Abnormal: > INFO | Stopping async topic tasks > INFO | Stopped KahaDB > > Could you kindly inform me that what caused the above phenomenon? > > Thanks a lot. > > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
