Re: Max memory allocation

2008-01-12 Thread Ralf Schuchardt
Am 11.01.2008 um 20:36 schrieb Galen Rhodes: Absolutely. First, to understand the bug open up a Terminal window and type the following: java -d64 -version Even if you're running Leopard on an Intel 64-bit processor (Core 2 Duo or Xeon) you see the following message : Ca

Re: Max memory allocation

2008-01-11 Thread Galen Rhodes
I wasn't sure so I just changed both. Also (I'm still looking for it) I assume that those files are copied from some stock template somewhere. If so you could just alter the template for those files and then you won't have to do this every time you rebuild your application. -- Galen Rhod

Re: Max memory allocation

2008-01-11 Thread Guido Neitzer
On 11.01.2008, at 12:36, Galen Rhodes wrote: To get your WebObjects application to run in 64-bit mode then you need to alter the classpath files. Once the application is built, edit the two classpath files in the application folder. If your application is named "Foo" then the two files yo

Re: Max memory allocation

2008-01-11 Thread Galen Rhodes
Absolutely. First, to understand the bug open up a Terminal window and type the following: java -d64 -version Even if you're running Leopard on an Intel 64-bit processor (Core 2 Duo or Xeon) you see the following message : Cannot run Java in 64 bit mode. Continuing in 32 b

Re: Max memory allocation

2008-01-11 Thread Galen Rhodes
Generally speaking its the same as the Java Runtime limits. That would be about 1.5GB on all older versions of Mac OS X (Tiger and older). However, if you're running Leopard on an 64-bit Intel processor then the limit is much higher. A lot higher. It could, in theory, go as high as you