Return-Path: 
 <users-return-13412-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 50095 invoked from network); 1 Apr 2008 13:12:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 1 Apr 2008 13:12:29 -0000
Received: (qmail 37185 invoked by uid 500); 1 Apr 2008 13:12:28 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 36861 invoked by uid 500); 1 Apr 2008 13:12:28 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 36852 invoked by uid 99); 1 Apr 2008 13:12:28 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 06:12:28 -0700
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 13:11:35 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1JggHM-0001Ci-31
	for users@activemq.apache.org; Tue, 01 Apr 2008 06:11:56 -0700
Message-ID: <16418415.post@talk.nabble.com>
Date: Tue, 1 Apr 2008 06:11:56 -0700 (PDT)
From: Vinod Venkatraman <vinodv26@gmail.com>
To: users@activemq.apache.org
Subject: Journaled jdbc persistence and broker restarts
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: vinodv26@gmail.com
X-Virus-Checked: Checked by ClamAV on apache.org


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 :
<beans>

  <!-- Allows us to use system properties as variables in this configuration
file -->
  <bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>

    <broker brokerName="broker_vinod_server" useJmx="true" persistent="true"
xmlns="http://activemq.org/config/1.0">
    <!-- Use the following to configure how ActiveMQ is exposed in JMX -->
    <managementContext>
       <managementContext connectorPort="1099"
jmxDomainName="org.apache.activemq1"/>
    </managementContext>

	<persistenceAdapter>
        <journaledJDBC journalLogFiles="5"
dataDirectory="${activemq.base}/../journal-backup/activemq-data/broker1_slave"/>
      
    </persistenceAdapter>	

    <destinations>
        <queue physicalName="sy.attribTestQ"/>
    </destinations>

    <transportConnectors>
       <transportConnector name="openwire" uri="tcp://localhost:61616"
discoveryUri="multicast://default"/>
    </transportConnectors>

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

  </broker>
</beans>

Logs:
http://www.nabble.com/file/p16418415/amq.log amq.log 
-- 
View this message in context: http://www.nabble.com/Journaled-jdbc-persistence-and-broker-restarts-tp16418415s2354p16418415.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.