activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pp <>
Subject Re: how to save topics and messages in mysql database
Date Wed, 15 Sep 2010 11:40:13 GMT

thanks gary.
my configuration file is

    Licensed to the Apache Software Foundation (ASF) under one or more
    contributor license agreements.  See the NOTICE file distributed with
    this work for additional information regarding copyright ownership.
    The ASF licenses this file to You under the Apache License, Version 2.0
    (the "License"); you may not use this file except in compliance with
    the License.  You may obtain a copy of the License at
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

    <!-- Allows us to use system properties as variables in this
configuration file -->
        <property name="locations">
<bean id="mysql-ds"
    <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
    <property name="url"
    <property name="username" value="root"/>
    <property name="password" value="12345"/>
    <property name="poolPreparedStatements" value="true"/>

        The <broker> element is used to configure the ActiveMQ broker. 
    <broker xmlns=""
brokerName="localhost" dataDirectory="${activemq.base}/data"
			For better performances use VM cursor and small memory limit.
			For more information, see:
            Also, if your producer is "hanging", it's probably due to
producer flow control.
            For more information, see:
                <policyEntry topic=">" producerFlowControl="true"
                    <vmCursor />
                <policyEntry queue=">" producerFlowControl="true"
                  <!-- Use VM cursor for better latency
                       For more information, see:
            The managementContext is used to configure how ActiveMQ is
exposed in 
            JMX. By default, ActiveMQ uses the MBean server that is started
            the JVM. For more information, see: 
            <managementContext createConnector="false"/>

            Configure message persistence for the broker. The default
            mechanism is the KahaDB store (identified by the kahaDB tag). 
            For more information, see: 

            The systemUsage controls the maximum amount of space the broker
            use before slowing down producers. For more information, see:
                    <memoryUsage limit="20 mb"/>
                    <storeUsage limit="1 gb"/>
                    <tempUsage limit="100 mb"/>
            The transport connectors expose ActiveMQ over a given protocol
            clients and other brokers. For more information, see: 
            <transportConnector name="openwire" uri="tcp://"/>


        Uncomment to enable Camel
        Take a look at activemq-camel.xml for more details
    <import resource="camel.xml"/>

        Enable web consoles, REST and Ajax APIs and demos
        Take a look at activemq-jetty.xml for more details 
    <import resource="jetty.xml"/>

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

View raw message