activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ConstantChange <>
Subject Re: Absolutely NO persistence please
Date Mon, 13 Aug 2007 15:06:14 GMT


That did the job. Thanks!
Just so you know that I am not an idiot, please spare one more minute and
look at my configuration (i used this new aproach, embedding non-spring xml
into spring (as suggested by apache.activemq):

>From my point of view, this should actually do exactly what your config

<amq:broker persistent="false" 
  			  id="broker" >

	   <amq:managementContext createConnector="false"/>
      <amq:usageManager id="memory-manager" limit="50"/>

Now why tf did that not work?

Anyway, thanks a lot!!


Gaurav Hariani wrote:
> My needs are similar to yours and I don't see any derby/journal activity.
> I'm using ActiveMQ 4.1.1 with the following basic activemq.xml config.
> Gaurav
> ---
> <beans>
>   <bean 
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
>   <broker brokerName="localhost" useJmx="true" persistent="false" 
> xmlns="">
>     <!--  Increase to 64 MB Use the following to set the broker memory 
> limit -->
>     <memoryManager> 
>         <usageManager id="memory-manager" limit="64 MB"/>
>     </memoryManager>
>     <!-- Use the following to configure how ActiveMQ is exposed in JMX -->
>     <managementContext>
>        <managementContext connectorPort="1099" 
> jmxDomainName="org.apache.activemq"/>
>     </managementContext>
>     <transportConnectors>
>        <transportConnector name="openwire" uri="tcp://localhost:61616"/>
>     </transportConnectors>
>   </broker>
> </beans>
> ConstantChange wrote:
>> Hi!
>> (I really tried to figure this out by finding other threads and reading
>> documentation, but unfortunately I did not get further hat way.)
>> We use ActiveMQ to create concurrent tasks doing some stuff in a parallel
>> manner for performance reasons. Now, in our case we dont need ANY
>> persistence whatsoever. Messages by avg. will live for around 3-10
>> seconds,
>> and if they take longer they are not needed anymore.
>> Now, the obvious thing to do is turning persistence off with the
>> "persistence=false" attribute in the broker. But this does not prevent
>> ActiveMQ from starting up the Derby Journal thing. Why is that? In all
>> the
>> other threads seemingly related to this the people either wanted only
>> journaling or only jdbc persistence, but I dont want any of those!! How
>> can
>> I archieve that?
>> (Or is the journal not an optional thing because its used as kind of
>> cache
>> so the memory does not overflow?)
>> Thanks very very much!
>> Cheers,
>> CC

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

View raw message