I can't really say if your proposed configuration is "wise" or not since I
don't know all the details of your use-case. However, I can say a few
things conclusively...
First, the global-max-size is measured in bytes so using 4096 will only
give you 4KB of space. If you actually want 4 gigabytes th
I see. With 16G on the machine, is this a wise setup?
-Xms1024M -Xmx8G
4096
On Wed, Jan 20, 2021 at 1:28 PM Justin Bertram wrote:
> > I don't have max-size-bytes or global-max-size set. However, according to
> the comments in the broker.xml file, global-max-size defaults to half of
> -Xmx, so
> I don't have max-size-bytes or global-max-size set. However, according to
the comments in the broker.xml file, global-max-size defaults to half of
-Xmx, so shouldn't Artemis start using the page file after it uses 1G?
Yes. However, given a few recent issues like ARTEMIS-3021 [1] and
ARTEMIS-3061
Hi Justin,
There is 16GB of memory on the VM. And I have JVM memory set to -Xms512M
-Xmx2G in the artemis.profile file, so I can increase those.
I don't have max-size-bytes or global-max-size set. However, according to
the comments in the broker.xml file, global-max-size defaults to half of
-Xmx,
> java.lang.OutOfMemoryError: Java heap space
My guess is that you were approaching your heap limit which caused the
preceding issues. Once you hit an OutOfMemoryError then in my experience
all bets are off so to speak and you need to restart the broker.
It's not clear why you couldn't connect to
