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 bit mode.
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-
b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)
Which is wrong because it should be able to run in 64-bit mode.
However, if you type in the full path to the Java library like so:
/System/Library/Frameworks/JavaVM.framework/Home/bin/java -d64 -version
Then, on Leopard running a 64-bit processor, you should see:
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-
b05-237)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_13-119, mixed mode)
For some reason you have to specify the path to the Java executable in
order for 64-bit mode to work. I don't know why except that they're
aware of the problem.
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 you need to edit are "Foo.woa/Contents/
MacOS/MacOSClassPath.txt" and "Foo.woa/Contents/MacOS/
MacOSXServerClassPath.txt".
In both files, locate the line (near the top) that reads:
# JVM == java
And change it to:
# JVM == /System/Library/Frameworks/JavaVM.framework/Home/bin/java
Then add "-d64" to your startup parameters along with something like "-
Xmx8192M".
--
Galen Rhodes
[EMAIL PROTECTED]
On Jan 11, 2008, at 2:02 PM, Jeff Schmitz wrote:
Thanks!
Can you tell me more about how to get around the path bug you
describe?
Jeff
On Jan 11, 2008, at 12:58 PM, Galen Rhodes wrote:
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 have HD space for the virtual memory. You just
have to use the -d64 command line flag along with the -Xmx
setting. Also, you'll have to tweek the application's startup
script to get around the path bug that causes the JVM to think it
can't do 64-bit mode when, in fact, it can.
But that's only for 64-bit Intel processors running Leopard. If
you're running any PowerPC processors (including the G5) then
you're stuck with the 32-bit JVM.
--
Galen Rhodes
[EMAIL PROTECTED]
On Jan 11, 2008, at 1:34 PM, Jeff Schmitz wrote:
Hello,
What is the max memory allocation you can assign to on application
instance (assuming of course you have the memory installed) on a
previous generation Xserve with Tiger Server/WO5.3? How about the
latest xserve with Leopard Server/WO5.4?
Thanks,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected]
)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/grhodes%40thissmallworld.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
