Have you configured limits on memory usage in the broker settings? You need to look at a heap dump and see exactly where the memory is being used (if it's messages on a destination, in prefetch etc).
Some general info about OOM and how to prevent it: https://activemq.apache.org/javalangoutofmemory.html On Mon, Nov 25, 2019 at 10:38 AM sainath <skya...@ra.rockwell.com.invalid> wrote: > 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 | jvm 1 | 2019/09/06 00:56:34 | java.lang.OutOfMemoryError: Java > heap space > INFO | jvm 1 | 2019/09/06 00:56:34 | Dumping heap to > D:\RockwellSoftware\heap_log\java_pid5216.hprof ... > INFO | jvm 1 | 2019/09/06 00:56:58 | Heap dump file created [4259842078 > bytes in 23.626 secs] > ---- > > Due to this issue we found data missing between Production database to > operational Database. > > Currently activemq memory set to 4 GB. We continuously monitor AMQ memory > using JConsole and found memory is consuming more than i.e. 2.8 GB > > This system is only dedicated for AMQ and Live transfer > > AactiveMQ version-5.14.1 > > JDK version : 1.8 Update 60 > > Could you please help to provide the root cause and fix on the issue. > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
