activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: Retrieve number of pending messages in the queue
Date Thu, 16 Sep 2010 22:20:37 GMT
On Thu, 2010-09-16 at 15:07 -0700, lopan wrote:
> Here is the activemq.xml file:
> 
> <beans xmlns="http://www.springframework.org/schema/beans"
> xmlns:amq="http://activemq.apache.org/schema/core"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd">
> - <!--  Allows us to use system properties as variables in this
> configuration file 
>   --> 
> - <bean
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> - <property name="locations">
>   <value>file:${activemq.base}/conf/credentials.properties</value> 
>   </property>
>   </bean>
> - <!--  
>         The <broker> element is used to configure the ActiveMQ broker. 
>     
>   --> 
> - <broker xmlns="http://activemq.apache.org/schema/core"
> brokerName="localhost" dataDirectory="${activemq.base}/data"
> destroyApplicationContextOnStop="true">
> - <!-- 			For better performances use VM cursor and small memory limit.
> 			For more information, see:
>             
>             http://activemq.apache.org/message-cursors.html
>             
>             Also, if your producer is "hanging", it's probably due to
> producer flow control.
>             For more information, see:
>             http://activemq.apache.org/producer-flow-control.html
>         
>   --> 
> - <destinationPolicy>
> - <policyMap>
> - <policyEntries>
> - <policyEntry topic=">" producerFlowControl="true" memoryLimit="1mb">
> - <pendingSubscriberPolicy>
>   <vmCursor /> 
>   </pendingSubscriberPolicy>
>   </policyEntry>
> - <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
> - <!--  Use VM cursor for better latency
>                        For more information, see:
>                        
>                        http://activemq.apache.org/message-cursors.html
>                        
>                   <pendingQueuePolicy>
>                     <vmQueueCursor/>
>                   </pendingQueuePolicy>
>                   
>   --> 
>   </policyEntry>
>   </policyEntries>
>   </policyMap>
>   </destinationPolicy>
> - <!--  
>             The managementContext is used to configure how ActiveMQ is
> exposed in 
>             JMX. By default, ActiveMQ uses the MBean server that is started
> by 
>             the JVM. For more information, see: 
>             
>             http://activemq.apache.org/jmx.html 
>         
>   --> 
> - <managementContext>
>   <managementContext createConnector="false" /> 
>   </managementContext>
> - <!--  
>             Configure message persistence for the broker. The default
> persistence
>             mechanism is the KahaDB store (identified by the kahaDB tag). 
>             For more information, see: 
>             
>             http://activemq.apache.org/persistence.html 
>         
>   --> 
> - <persistenceAdapter>
>   <kahaDB directory="${activemq.base}/data/kahadb" /> 
>   </persistenceAdapter>
> - <!--             The systemUsage controls the maximum amount of space the
> broker will 
>             use before slowing down producers. For more information, see:
>             
>             http://activemq.apache.org/producer-flow-control.html
>              
>         <systemUsage>
>             <systemUsage>
>                 <memoryUsage>
>                     <memoryUsage limit="20 mb"/>
>                 </memoryUsage>
>                 <storeUsage>
>                     <storeUsage limit="1 gb"/>
>                 </storeUsage>
>                 <tempUsage>
>                     <tempUsage limit="100 mb"/>
>                 </tempUsage>
>             </systemUsage>
>         </systemUsage>
> 		
>   --> 
> - <!--  
>             The transport connectors expose ActiveMQ over a given protocol
> to
>             clients and other brokers. For more information, see: 
>             
>             http://activemq.apache.org/configuring-transports.html 
>         
>   --> 
> - <transportConnectors>
>   <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" /> 
>   </transportConnectors>
> - <plugins>
>   <statisticsBrokerPlugin /> 
>   </plugins>
>   </broker>
> - <!--  
>         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" /> 
>   </beans>

Try adding in the plugins definition in alphabetical order with respect
to the other configuration items.  In 5.4.0 the order matters.

Regards

-- 
Tim Bish

Open Source Integration: http://fusesource.com

Follow me on Twitter: http://twitter.com/tabish121
My Blog: http://timbish.blogspot.com/


Mime
View raw message