Can you try version 5.13.2 and see if that helps? There was a performance
bug related to durables (AMQ-6158) in KahaDB that was fixed which might
help here.
On Tue, Mar 29, 2016 at 12:17 AM, Shobhana <shobh...@quickride.in> wrote:
> I enabled debug logs to see what was happening when AMQ could not send ACK
> within 30 secs. I started the AMQ broker on 28-Mar around 17:40 and to my
> surprise, I find that the server startup is still going on even now at
> 29-Mar 09:30 (~16 hours!!). I see a lot of following messages in the logs :
>
> 2016-03-28 18:36:25,340 | DEBUG | PrimaryBroker adding destination:
> topic://33ConcurrentTopicCreator410 |
> org.apache.activemq.broker.region.AbstractRegion | main
> 2016-03-28 18:36:25,347 | DEBUG | Restoring durable subscription:
> SubscriptionInfo {subscribedDestination =
> topic://33ConcurrentTopicCreator410, destination =
> topic://33ConcurrentTopicCreator410, clientId = 3ConcurrentTopicCreator,
> subscriptionName = AT_LEAST_ONCE:33ConcurrentTopicCreator410, selector =
> null, noLocal = false} | org.apache.activemq.broker.region.TopicRegion |
> main
> 2016-03-28 18:36:25,350 | DEBUG | PrimaryBroker adding destination:
> topic://33ConcurrentTopicCreator409 |
> org.apache.activemq.broker.region.AbstractRegion | main
> 2016-03-28 18:36:25,357 | DEBUG | Restoring durable subscription:
> SubscriptionInfo {subscribedDestination =
> topic://33ConcurrentTopicCreator409, destination =
> topic://33ConcurrentTopicCreator409, clientId = 3ConcurrentTopicCreator,
> subscriptionName = AT_LEAST_ONCE:33ConcurrentTopicCreator409, selector =
> null, noLocal = false} | org.apache.activemq.broker.region.TopicRegion |
> main
> 2016-03-28 18:36:25,360 | DEBUG | PrimaryBroker adding destination:
> topic://33ConcurrentTopicCreator408 |
> org.apache.activemq.broker.region.AbstractRegion | main
> 2016-03-28 18:36:25,367 | DEBUG | Restoring durable subscription:
> SubscriptionInfo {subscribedDestination =
> topic://33ConcurrentTopicCreator408, destination =
> topic://33ConcurrentTopicCreator408, clientId = 3ConcurrentTopicCreator,
> subscriptionName = AT_LEAST_ONCE:33ConcurrentTopicCreator408, selector =
> null, noLocal = false} | org.apache.activemq.broker.region.TopicRegion |
> main
> 2016-03-28 18:36:25,370 | DEBUG | PrimaryBroker adding destination:
> topic://33ConcurrentTopicCreator403 |
> org.apache.activemq.broker.region.AbstractRegion | main
> 2016-03-28 18:36:25,377 | DEBUG | Restoring durable subscription:
> SubscriptionInfo {subscribedDestination =
> topic://33ConcurrentTopicCreator403, destination =
> topic://33ConcurrentTopicCreator403, clientId = 3ConcurrentTopicCreator,
> subscriptionName = AT_LEAST_ONCE:33ConcurrentTopicCreator403, selector =
> null, noLocal = false} | org.apache.activemq.broker.region.TopicRegion |
> main
> 2016-03-28 18:36:25,380 | DEBUG | PrimaryBroker adding destination:
> topic://33ConcurrentTopicCreator402 |
> org.apache.activemq.broker.region.AbstractRegion | main
> 2016-03-28 18:36:25,387 | DEBUG | Restoring durable subscription:
> SubscriptionInfo {subscribedDestination =
> topic://33ConcurrentTopicCreator402, destination =
> topic://33ConcurrentTopicCreator402, clientId = 3ConcurrentTopicCreator,
> subscriptionName = AT_LEAST_ONCE:33ConcurrentTopicCreator402, selector =
> null, noLocal = false} | org.apache.activemq.broker.region.TopicRegion |
> main
>
> There are 89000+ instances of "PrimaryBroker adding destination:" and
> "Restoring durable subscription:"
>
> If I enable only INFO log level, broker starts up within a few minutes, but
> if DEBUG is enabled, why does it take so long? Will writing debug message
> to
> the log take so much more time?
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-with-KahaDB-as-persistent-store-becomes-very-slow-almost-unresponsive-after-creating-large-s-tp4709985p4710008.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
