On 1/3/2019 6:40 PM, ark...@tutanota.com wrote:
The strange part is I was able to set a max memory in the tomcat9w.exe
configuration tool to about 1600 Megabytes and that was the hitting of the wall
on that setup (the original physical one that I p2v'd to a VM), I can set less
ram, but I cannot set it more than 1600 otherwise when I try to start the
tomcat service in services.msc it will just crap outs.
Tomcat itself is not 32 bit or 64 bit. It is *Java* that determines this.
If you have a 32-bit Java, then that Java cannot address more than 2GB
of memory, and this likely includes memory that Java requires beyond the
Java heap size itself. This is a limitation that can only be overcome
by running a 64-bit Java. Naturally this requires a 64-bit operating
system, which requires a 64-bit CPU.
For the server side, readily available Intel processors have been all
64-bit since 2005. For the client side, readily available Intel
processors have been all 64-bit since 2006. If you've purchased a
computer in the last ten years, it is virtually guaranteed to have
64-bit hardware.
I think it was either Java 9 or Java 10 where Oracle stopped making
32-bit versions easy to find.
Run a 64-bit Java. You won't have any memory limits.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
