On 28.05.2010 05:12, Leon Kolchinsky wrote:
Hello Jung,
Thanks for your insights. Learning some new stuff about Java every day ;)
I've read this nice blog -
http://www.talkingtree.com/blog/index.cfm/2006/4/28/Understanding-HotSpot-in-Plain-English
(
UNDERSTANDING HOTSPOT IN PLAIN
ENGLISH<http://www.talkingtree.com/blog/index.cfm/2006/4/28/Understanding-HotSpot-in-Plain-English>
)
Now I can see how to avoid those HotSpot compilation errors and eventual JVM
crashes.
I could use -Xint option to force "interpretedmode execution only"
like this:
# cat /srv/tomcat/bin/setenv.sh
export JAVA_HOME=/srv/jdk
export PATH="${PATH}:${JAVA_HOME}/bin/"
CATALINA_OPTS="-Xint -Xms512m -Xmx1024m -XX:MaxPermSize=512m $JAVA_OPTS
-Djava.awt.headless=true "
What are you saying?
Am I right?
As Chuck and others have stated: "-Xint" is not really a good solution.
You definitely want HotSpot and only work around your special problem.
Disabling HotSpot is very negative for performance and not something you
can get forward with.
Yes: file a bug!
-client: As Chuck wrote it might not be available or 64Bit VMs. So take
the commandline parameters and add -version and check what the output
is, i.e. if there is any diference between -server and -client.
Otherwise don't be surprised that it doesn't help.
I really suggest you go the way of disabling special compilations. Only
that way you learn about your real problem. Is it only a few methods
that you need to disable for compilation, or is it many methods, so that
there is a bigger problem underneath.
And don't forget to try other JVM patch versions (older or newer).
HotSpot compiler bug fixes (and possibly regressions) are frequent in
the release notes for the JVM.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
