Re: A question about memory usage & jvm

More precisely, the 70% is for within the allocated heap the memory activemq will use for the memory store. ActiveMQ has its own data structures unrelated to the memory store, which consume heap space from the JVM above and beyond what is used for the memory store. But the overall explanation is ex

Re: LevelDB gets corrupted and Ports are not up when when activemq is stopped on servers

A three-broker master-slave cluster using shared-filesystem KahaDB will work, provided that you have a supported shared filesystem (i.e. NFS v4) that's accessible to all brokers. Tim On Jul 2, 2017 11:02 PM, "Vidu" wrote: > We are using ActiveMQ version: 5.13.2 .Will moving to kahaDB instead of

Re: A question about memory usage & jvm

The Java process will at the os level which is what you output from what I can tell, will be allocated 6gb if that's what you set the heap size to (Java will always actually use a little more than just the heap for bits like offheap, classes (permgen) and process overhead) The 70% is for within

A question about memory usage & jvm

Hello, I'm a little new about activemq. We allocated 6gb jvm memory for activemq and in the activemq.xml file we set memory usage for jvm %70 percent.In this case it's supposed to use ( 6gb = 6144 mb ) 61,44 * 70 = 4.3 gb if i'm correct ?

Re: PooledConnectionFactory: createConnection results in log entry "Successfully connected to ..."

Hi Jochen Could I suggest maybe looking at the test cases how they're using it and see what maybe different in your code? In particular look at testConnectionsArePooled https://github.com/apache/activemq/blob/master/activemq-jms-pool/src/test/java/org/apache/activemq/jms/pool/PooledConnectionFa