![]() However if you use a 32 bits version of Java Tomcat will be installed as a 32 bits application. This mean that installer will use the "Program Files" folder as the default installation directory and the entry for the Tomcat service in the windows registry will be placed in "HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation". If you installed a 64 bits version the default installation directory for the Tomcat will be installed as a 64 bits application. On a 64 bits system you can install either a Java 32 bits version or a Java 64 bits version. ![]() In a 32 bits system you can only install the 32 bits Java version. In any case, it doesn't matter if you have installed Java in the 32bits or 64bits version however depending on the Java version you have installed it will install the Windows service wrapper for 32 or 64 bits. This is because Tomcat itself is a java application and it is platform independent (the Java VM is what will be 32bits or 64bits). I have googled this for a long time and apparently it has to do with the way the operating system itself (in this case windows, be it windows server 2008 std, 2008 r2, or win10 etc) handles per process memory limitations and thread memory allocations that by default only allow around 1.5 to 2 g of ram per process and that this is what is constraining the tomcat apache jvm and not the programs itself.īut if this is indeed an OS difference, I checked on my original 32bit server2008 std, the one that I did P2V, and it didn't have anything special set in the boot.As Pierre mentions there is only one installer available from that will work on both 32bits and 64bits in the Tomcat official site. so the wall is around 1GB.Īs a test, I installed the tomcat (zip extract, not using msi or exe installer) to my own client workstation laptop running the latest windetc and once again I hit the 1GB wall and cannot even get it to go up to 1.6GB, even though I have like 16GB ram on my laptop machine. Long story short, from a fresh VM, on this box I'm only able to set a max total ram in tomcatw as around 1000 m (1GB) and if I set anymore it will not start, as in I cannot get tomcat service to start. So my thinking was since I have to stay on 32-bit of tomcat and 32-bit of Java JVM anyhow (long story.) that it might be better to put it in a 64-bit OS (server 2008r2) rather than the standard 32bit of server 2008. 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. ![]() I'm upgrading the server to windows server 2008 r2 64bit and instead of doing an inplace, I'm just building another one up and doing parallel side by side, and its a fresh VM from the start, no p2v stuff. I have an application on tomcat that used to be on a physical windows server 2008 standard 32-bit which I p2v'd with vmware converter over as a VM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |