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="http://activemq.org/config/1.0";>
<!-- 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
