-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
Caldarale, Charles R wrote: >> From: Christopher Schultz [mailto:[EMAIL PROTECTED] >> Subject: Re: [OT]Re: Is better one or more Tomcat instances >> per machine >> >> The fact remains that you can't allocate a VM heap bigger than around >> 1750MB on my 32-bit, 2.6 Linux kernel. Why not? > > You have to wait for a full moon... :) It looks like the problem could be due to a number of different issues, which is why everyone argues about "the" cause. It is /not/ endemic of 32-bit JVMs: it's apparently the fault of the OS. Running a 32-bit JVM on a 64-bit OS (while kinda silly) should allow you to allocate a heap much closer to the 4GB real limit on 32-bit-based processes. It's also /not/ the fault of the hardware. 32-bit pointer = 32-bit addressable process space. If the OS doesn't allow you get all of that, then it's the OSs fault, not the hardware. It's OS dependent, and it is kernel option dependent, which is why nobody can nail down the answer. There are simply too many configurations out there to be able tp predict why this problem occurs on /your/ system. I suppose you could find out exactly why, but it would take a long time and you efforts are better spent upgrading to an OS and JVM that can access more memory in the first place. It appears that if this is happening to you, there is little you can do about it short of re-compiling your kernel with different process-memory options (such as 2/2 versus 3/1 address splitting). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+CRn9CaO5/Lv0PARAuzcAJ9EwelMp52otOw+t0j7XD9IDvMGyQCgn2Vv ykxFrl5q3p6r45DpguNF6Wc= =5FHT -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
