You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@activemq.apache.org by t-watana <wa...@jp.fujitsu.com> on 2018/03/08 05:15:15 UTC

It costs time when stopping ActiveMQ

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

Re: It costs time when stopping ActiveMQ

Posted by t-watana <wa...@jp.fujitsu.com>.

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 10000 over. 
* Number of Topics is 10000 over. 







--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: It costs time when stopping ActiveMQ

Posted by Tim Bain <tb...@alumni.duke.edu>.

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 <wa...@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
>