activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandeep Chayapathi <>
Subject Re: stopping master bridge, negociation timeout & out of memory exceptions
Date Thu, 18 Jan 2007 17:28:36 GMT

Sandeep Chayapathi wrote:
> 1. usage manager reference
> (
> says, "limit" property sets memory limit in bytes. I have switched to
> using "limitMb" property instead

Activemq 4.1 doesn't recognize "limitMb" as a usageManager's property.
Throws as "
Bean property 'limitMb' is not writable or has an invalid setter method"

And Im not sure if "limit" takes values in MB either, so I have moved back
to setting values in bytes.

Sandeep Chayapathi wrote:
> 2. In case "limit" of "2048 MB" was correct, the ACTIVEMQ_OPTS had max
> memory pool (-Xmx) as 512. I have switched to 4096MB (big iron server
> yay!)

This definitely seems to help

Sandeep Chayapathi wrote:
> 3. few threads indicated multicast transport could be the culprit, I
> have removed the auto discover mode (multicast discovery) for now.

Not sure if "multicast discovery" is root cause of the problem I faced.

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

View raw message