You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by andrewh <an...@plaintalkit.com> on 2008/07/08 18:02:35 UTC

ActiveMQ Disk usage

Hi, I know this has come up before but I'm positive we are consuming as much
as we're producing (if not slightly less), and disk is filling in the order
of 15Gb over three days. I would really appreciate some pointers from more
experienced users.

Has anyone experienced problems with disk usage that they have solved
privately? Can anyone spot obvious problems with the config below?

Much appreciated,

Andrew


Setup:
Ubuntu Server 6.06 - kernel 2.6.15-26-amd64
ACTIVEMQ_HOME=/usr/local/fuse-message-broker-5.0.0.11
JAVA_HOME=/usr/local/jdk1.6.0_06

Config (sanitised):

<beans
  xmlns="http://www.springframework.org/schema/beans"
  xmlns:amq="http://activemq.org/config/1.0"
  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.org/config/1.0
http://activemq.apache.org/schema/activemq-core.xsd
  http://activemq.apache.org/camel/schema/spring
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

  <!-- Allows us to use system properties as variables in this configuration
file -->
  <bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
  
  <broker xmlns="http://activemq.org/config/1.0" brokerName="server"
useJmx="true" dataDirectory="${activemq.base}/data" persistent="true">
  
    <!-- The transport connectors ActiveMQ will listen to -->
    <transportConnectors>
       <transportConnector name="openwire" uri="tcp://localhost:61616"/>
	<transportConnector name="stomp" uri="tcp://localhost:61617"/>
    </transportConnectors>

    <networkConnectors>
	</networkConnectors>

    <destinations>
      <queue physicalName="Company1.Media.Company1.DepartmentB" />
      <queue physicalName="Company1.Media.Company1.ProductC" />
      <queue physicalName="Company1.Media.Company1.ProductCTest" />
      <queue physicalName="Company1.Media.DepartmentC.Alerts" />
      <queue physicalName="Company1.Media_All.Company1.ProductC" />
      <queue physicalName="Company1.Media_All.Company1.DepartmentB" />
      <queue physicalName="Company1.ProductA.Company1.DepartmentB" />
      <queue physicalName="Company1.ProductA.Project1.ProductA" />
      <queue physicalName="Company1.ProductA_All.Company1.DepartmentB" />
      <queue physicalName="Company1.ProductB.Company1.DepartmentB" />
      <queue physicalName="Company1.ProductB.Company1.Test" />
      <queue physicalName="Company1.ProductB.Project1.DepartmentA" />
    </destinations> 
 
    <destinationInterceptors>
      <virtualDestinationInterceptor>
        <virtualDestinations>
          <compositeQueue name="Company1.Media">
            <forwardTo>
              <queue physicalName="Company1.Media.Company1.ProductC" />
              <queue physicalName="Company1.Media.Company1.ProductCTest" />
              <queue physicalName="Company1.Media.DepartmentC.Alerts" />
            </forwardTo>
          </compositeQueue>
          <compositeQueue name="Company1.Media_All">
            <forwardTo>
            </forwardTo>
          </compositeQueue>
          <compositeQueue name="Company1.ProductA">
            <forwardTo>
              <queue physicalName="Company1.ProductA.Company1.DepartmentB"
/>
              <queue physicalName="Company1.ProductA.Project1.ProductA" />
            </forwardTo>
          </compositeQueue>
          <compositeQueue name="Company1.ProductA_All">
            <forwardTo>
            </forwardTo>
          </compositeQueue>
          <compositeQueue name="Company1.ProductB">
            <forwardTo>
              <queue physicalName="Company1.ProductB.Company1.DepartmentB"
/>
              <queue physicalName="Company1.ProductB.Company1.Test" />
              <queue physicalName="Company1.ProductB.Project1.DepartmentA"
/>
            </forwardTo>
          </compositeQueue>
        </virtualDestinations>
      </virtualDestinationInterceptor>
    </destinationInterceptors>  

    <!-- Use the following if you wish to configure the journal with JDBC
-->
   
    <persistenceAdapter>
        <amqPersistenceAdapter /> 
    </persistenceAdapter>
    

    <managementContext>
	<managementContext connectorPort="1099"
jmxDomainName="org.apache.activemq"/>
    </managementContext>
    

  <systemUsage>
            <systemUsage>
                <memoryUsage>
                    <memoryUsage limit="1 gb"/>
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="2 gb" name="amq-store"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="1 gb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>


  </broker>



  <!-- lets create a command agent to respond to message based admin
commands on the ActiveMQ.Agent topic -->
  <commandAgent xmlns="http://activemq.org/config/1.0"/>


  <!-- An embedded servlet engine for serving up the Admin console -->
  <jetty xmlns="http://mortbay.com/schemas/jetty/1.0">
    <connectors>
      <nioConnector port="8161" />
    </connectors>

    <handlers>
      <webAppContext contextPath="/admin"
resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true" />
    </handlers>
  </jetty>
</beans>


-- 
View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18342711.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: ActiveMQ Disk usage

Posted by Rob Davies <ra...@gmail.com>.
Good advice!

On 11 Jul 2008, at 17:25, andrewh wrote:

>
> Solved. We have a queue that had no consumers, so messages from that  
> queue
> were in the journal, but unfortunately all the data inbetween these  
> messages
> is retained, due to how the journal indexes (I presume). Purging  
> this queue
> brings the journal size back down.
>
> Moral of story - audit your queues! :)
>
> Cheers,
>
> Andrew
>
>
>
> rajdavies wrote:
>>
>> Hi Andrew - will have a look
>> btw - who did you have training with ?
>>
>> cheers,
>>
>> Rob
>>
> -- 
> View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18407464.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Re: ActiveMQ Disk usage

Posted by andrewh <an...@plaintalkit.com>.
Solved. We have a queue that had no consumers, so messages from that queue
were in the journal, but unfortunately all the data inbetween these messages
is retained, due to how the journal indexes (I presume). Purging this queue
brings the journal size back down.

Moral of story - audit your queues! :)

Cheers,

Andrew



rajdavies wrote:
> 
> Hi Andrew - will have a look
> btw - who did you have training with ?
> 
> cheers,
> 
> Rob
> 
-- 
View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18407464.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: ActiveMQ Disk usage

Posted by andrewh <an...@plaintalkit.com>.
Hi Rob, that's much appreciated. The training was with your good selves at
IONA :)

Best,

Andrew


rajdavies wrote:
> 
> Hi Andrew - will have a look
> btw - who did you have training with ?
> 
> cheers,
> 
> Rob
> 

-- 
View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18380795.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: ActiveMQ Disk usage

Posted by Rob Davies <ra...@gmail.com>.
Hi Andrew - will have a look
btw - who did you have training with ?

cheers,

Rob

On 10 Jul 2008, at 11:13, andrewh wrote:

>
>
>
> andrewh wrote:
>>
>>
>>
>> andrewh wrote:
>>>
>>>
>>> [snip...]
>>>
>>>
>>
>> https://issues.apache.org/activemq/browse/AMQ-1786
>>
>> I think I could be experiencing this issue. It is the
>> $ACTIVEMQ_HOME/data/brokername/journal folder that is filling up.  
>> Still,
>> any comments on my config are appreciated.
>>
>> Rgds,
>>
>> Andrew
>>
>
> Can someone in a position to know please respond to this issue? I  
> would just
> like to know what is the status of this problem with journals, and  
> whether I
> can take some action such as disable journalling?
>
> Sorry to sound impatient but we would like to crack on using this  
> technology
> and this is a major blocker. We have shelled out for training so we  
> have
> tried to contribute to the project in some fashion.
>
> Thank you,
>
> Andrew
>
> -- 
> View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18379764.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Re: ActiveMQ Disk usage

Posted by andrewh <an...@plaintalkit.com>.


andrewh wrote:
> 
> 
> 
> andrewh wrote:
>> 
>> 
>> [snip...]
>> 
>> 
> 
> https://issues.apache.org/activemq/browse/AMQ-1786
> 
> I think I could be experiencing this issue. It is the
> $ACTIVEMQ_HOME/data/brokername/journal folder that is filling up. Still,
> any comments on my config are appreciated.
> 
> Rgds,
> 
> Andrew
> 

Can someone in a position to know please respond to this issue? I would just
like to know what is the status of this problem with journals, and whether I
can take some action such as disable journalling?

Sorry to sound impatient but we would like to crack on using this technology
and this is a major blocker. We have shelled out for training so we have
tried to contribute to the project in some fashion.

Thank you,

Andrew

-- 
View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18379764.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: ActiveMQ Disk usage

Posted by andrewh <an...@plaintalkit.com>.


andrewh wrote:
> 
> 
> [snip...]
> 
> 

https://issues.apache.org/activemq/browse/AMQ-1786

I think I could be experiencing this issue. It is the
$ACTIVEMQ_HOME/data/brokername/journal folder that is filling up. Still, any
comments on my config are appreciated.

Rgds,

Andrew
-- 
View this message in context: http://www.nabble.com/ActiveMQ-Disk-usage-tp18342711p18343816.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.