It's probably also worth considering whether you're giving the JVM (and the machine) enough RAM for the amount of data you're asking it to hold in memory.
Tim On Mon, Feb 7, 2022, 7:47 PM Matt Pavlovich <mattr...@gmail.com> wrote: > Hello Karl- > > Those error messages are usually indicative of a garbage collection (GC) > tuning problem at the JVM level. On any busy system running Java, the > default GC settings may not force garbage collection frequently enough in > order to keep memory resources available. > > I suggest you look into garbage collection logging and GC tuning options > for your version of the JDK. > > Thanks, > Matt > > > On Feb 7, 2022, at 2:57 PM, Nordstrom, Karl <k...@psu.edu> wrote: > > > > Hello activemq users, > > > > We are running v5.16.3 on our amq dev nodes and hit these errors today. > Has anybody else encounter these? The heap size on dev is 1G while it's 4G > on acceptance. I wonder if 5.16.3 requires more space than 5.15.12 did? > > > > 2022-02-07 15:22:39,325 | ERROR | JobScheduler: JMS Caught exception in > mainloop | org.apache.activemq.store.kahadb.scheduler.JobSchedulerImpl | > JobScheduler:JMS > > java.lang.OutOfMemoryError: GC overhead limit exceeded > > > > 2022-02-07 15:22:45,761 | ERROR | Checkpoint failed | > org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal > Checkpoint Worker > > java.lang.OutOfMemoryError: GC overhead limit exceeded > > > > > > --- > > > > Karl Nordström > > > > Systems Administrator > > > > Penn State IT | Application Platforms > >
