On 29/09/2010 14:53, Hans Magne Helland wrote: > Thanks for the answers. > >> 1048 is an unusual value; are you reporting the numbers accurately? >> Shouldn't there be an MB on the end of each? Note that it's usually better >> to set the >> initial and maximum to the same value for server environments. > > This was copied from the test server, were I tried to find the memory > limit where tomcat service would not start. I will set both to 1024mb, > thanks :) > >> Unless you're referring to native code inside your webapps, the above >> statement makes no sense. >> If you do have native code, then a simple recompile will allow you to use >> it with a 64-bit JVM. > > This tomcat server is running an ARS Remedy Mid-Tier application > (version 7.5), the requirements from BMC on this version is that it > must be a 32bit tomcat install using a 32bit java. Luckely the ARS 7.6 > version will fully support 64b java and tomcat. > > So 1024mb looks to be the limit on a 32bit java/tomcat install?
Just so it's clear: Tomcat is neither 32bit nor 64bit. There are additional native components for which the bits matter, but Tomcat itself is just Java. p
0x62590808.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
