<systemUsage>
<systemUsage sendFailIfNoSpace="true">
<memoryUsage>
<memoryUsage limit="1450"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="10 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="10 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
I think I know why it is so big. I have quite a few queues and each one has
quite a capacity on it now. So it just all adds up. Maybe there isn't a
problem after all. By tweaking the JVM params slightly I got the broker to
come up and stay up.
-----
Regards,
Andrew Marlow
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Memory-usage-for-the-broker-is-more-than-the-maximum-available-for-the-JVM-tp4671330p4671341.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
