Awesome Gary, this was exactly what I was looking for. Thanks again!
On May 18, 2012, at 10:29 AM, Gary Tully wrote:
> it is totally dependent on your disk size, when a limit is reached,
> the next add will block.
> The defaults from[1] are:
> systemUsage.getMemoryUsage().setLimit(1024 * 1024
it is totally dependent on your disk size, when a limit is reached,
the next add will block.
The defaults from[1] are:
systemUsage.getMemoryUsage().setLimit(1024 * 1024 * 64); // Default 64Meg
systemUsage.getTempUsage().setLimit(1024L * 1024 * 1000 * 50); // 50 Gb
systemUsage.getStoreUsage
Many thanks Gary! Do you have recommendations for the storeUsage and tempUsage
limits given that our max journal file size is 32mb? How did this work in
5.4.0?
On May 18, 2012, at 9:19 AM, Gary Tully wrote:
> inline
>
> On 18 May 2012 05:24, Geoffrey Arnold wrote:
>> We are upgrading from A
inline
On 18 May 2012 05:24, Geoffrey Arnold wrote:
> We are upgrading from AMQ 5.4.0 to 5.6.0, and noticed two issues right off
> the bat:
>
> - The "activemq-all-5.6.0.jar" library is now bundled with the SLF4J Log4J
> binding, trumping the JDK 1.4 binding already in our classpath. As a
> w
We are upgrading from AMQ 5.4.0 to 5.6.0, and noticed two issues right off the
bat:
- The "activemq-all-5.6.0.jar" library is now bundled with the SLF4J Log4J
binding, trumping the JDK 1.4 binding already in our classpath. As a
workaround we have switched to using the individual libraries (act
