ll want to create a network.
>
> 2009/10/17 tejeswara
>
>>
>> Gary,
>>
>> In my config file I have multicast in both these entries. Which one you
>> think possibly causing this memory leak?. We plan to have failover broker
>> so
>> we may ne
do you need multicast discovery on
> your transport connector? I wonder if it is possible you are seeing
> https://issues.apache.org/activemq/browse/AMQ-2283 which resulted in an
> leak
> of discovery threads? Removing the discoveryUri will work around it.
>
> 2009/10/13 tejeswa
tivemq.xml? It looks like you need to restrict the
> memory usage of the broker and have it spool messages to disk when the
> memory limits are reached. See some additional detail at
> http://activemq.apache.org/javalangoutofmemory.html#java.lang.OutOfMemory-SpoolingMessagestoDisk
> *
Our broker is running on Linux (RHEL4 box) and after 1 or 2 days I see below
error in logs.
Note that, below values are set in bin/activemq in out test lab:
if [ -z "$ACTIVEMQ_OPTS" ] ; then
ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true"
fi
I tried to stress test bro
