You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by sainath <sk...@ra.rockwell.com.INVALID> on 2020/06/01 13:44:10 UTC
Re: OutOfMemoryError in activeMQ and applcation gets stopped
Hi All,
We disabled JMX and advisories, this seems to fix the memory issue.
In the ActiveMQ.xml file we
Added these flags useJmx="false" and advisorySupport="false"
eg:
<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="localhost" dataDirectory="${activemq.data}" useJmx="false"
advisorySupport="false">
For any clients we added jms.watchTopicAdvisories=false
eg:
loaderBrokerURL=failover\:(tcp\://localhost\:61616)?jms.watchTopicAdvisories=false
Has anyone had to do this or understand why this would help? Is there a bug
with these components that’s causing a memory leak?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: OutOfMemoryError in activeMQ and applcation gets stopped
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi,
What ActiveMQ did you test ?
Regards
JB
> Le 2 juin 2020 à 17:26, sainath <sk...@ra.rockwell.com.INVALID> a écrit :
>
> We tried just JMX which made a big difference but it seems that advisories
> still had some effect and decided to be safe and disabled both. If someone
> is able to read heap dumps we would be more than happy to collect them to
> verify what if any objects are being retained.
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: OutOfMemoryError in activeMQ and applcation gets stopped
Posted by sainath <sk...@ra.rockwell.com.INVALID>.
We tried just JMX which made a big difference but it seems that advisories
still had some effect and decided to be safe and disabled both. If someone
is able to read heap dumps we would be more than happy to collect them to
verify what if any objects are being retained.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: OutOfMemoryError in activeMQ and applcation gets stopped
Posted by Tim Bain <tb...@alumni.duke.edu>.
Does disabling one but not both of those things also fix the problem? Or is
the problem only eliminated if both are disabled?
Tim
On Mon, Jun 1, 2020, 7:44 AM sainath <sk...@ra.rockwell.com.invalid>
wrote:
> Hi All,
>
> We disabled JMX and advisories, this seems to fix the memory issue.
>
> In the ActiveMQ.xml file we
>
> Added these flags useJmx="false" and advisorySupport="false"
>
> eg:
>
> <broker xmlns="http://activemq.apache.org/schema/core"
> brokerName="localhost" dataDirectory="${activemq.data}" useJmx="false"
> advisorySupport="false">
>
> For any clients we added jms.watchTopicAdvisories=false
>
> eg:
>
> loaderBrokerURL=failover\:(tcp\://localhost\:61616)?jms.watchTopicAdvisories=false
>
> Has anyone had to do this or understand why this would help? Is there a
> bug
> with these components that’s causing a memory leak?
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>