activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Venkatraman <>
Subject Journaled jdbc persistence and broker restarts
Date Tue, 01 Apr 2008 13:11:56 GMT

HI All,

I am using AMQ 4.1.1 with journaled jdbc persistence (which I gather is the
fastest form of persistence in 4.1.1)

I observe that when I have around 100K messages (each of size 100KB) queued
up and I try to stop the broker using a ^C it takes more then one hr to
stop. During this time, AMQ is constantly comsuming CPU.

Now if I kill AMQ during this time and then try to bring it back up, it
takes another hr to queue the 100K messages back into the queue. 

This is a serious issue for us because we have slow consumers and hence the
queue is bound to grow rapidly and we need to retain messages across broker
restarts. Any help is appreciated.

Following is the configuration and AMQ logs for these operations :

Config :

  <!-- Allows us to use system properties as variables in this configuration
file -->

    <broker brokerName="broker_vinod_server" useJmx="true" persistent="true"
    <!-- Use the following to configure how ActiveMQ is exposed in JMX -->
       <managementContext connectorPort="1099"

        <journaledJDBC journalLogFiles="5"

        <queue physicalName="sy.attribTestQ"/>

       <transportConnector name="openwire" uri="tcp://localhost:61616"

      <networkConnector name="default-nc" dynamicOnly="true"
uri="multicast://default" networkTTL="3000"/>


Logs: amq.log 
View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message