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://ac
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:
http://activemq.apache.org/schema/core";
brokerName="localhost" dataDirectory="${activemq.data}" useJmx="false"
advisor
We have tried with java Update 181 and it still ran out of memory. Could you
please help us to provide some suggestion on this.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi All,
Yes, we have configured the limits on memory usage in the broker settings.
We also checked the heap dump and found that still 500 MB free space
available. So what could you be the reason for OutOfMemoryError in activeMQ
Also we are monitoring the AMQ queues and there is no pending mes
We have LiveTransfer application that use ActiveMQ to transfer data from
Production database to operational Database
Application is getting issue for every 50+ days i.e. OutOfMemoryError in
activeMQ and LT gets stopped. After restarting the AMQ services, it will
resume the transfer.
INFO |
