I wrote:
In resolving the crisis over the customer box on which Tomcat wasn't starting, I found that the "catalina.sh" script for Tomcat needed these lines (preferably in a separate "setenv.sh" file, rather than directly in "catalina.sh"):

# Java 6 settings if needed export -s JAVA_HOME=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre export -s CATALINA_HOME=/wintouch/tomcat export -s JAVA_OPTS="-Dos400.awt.native=true -Djava.awt.headless=true -Djava.version=1.6 -Xms256m -Xmx512m"

But it seems that the very first line of this block is overriding the JAVA_HOME environment variable I'd so laboriously set in the CL program.

Which makes me wonder . . . if I could set CATALINA_HOME and JAVA_OPTS in the CL, instead of the shell script, which would greatly simplify the installation.

I ran some experiments on our box, and found the following results:

1. Tomcat works just fine with the CATALINA_HOME and JAVA_OPTS environment variables set from the command line, instead of in the script so it probably likewise will work just fine with those environmental variables set in the STRTOMCAT CL program.

2. While it seems to like both the "/qopensys/QIBM/ProdData/JavaVM/jdk60/32bit" and "/qopensys/QIBM/ProdData/JavaVM/jdk626/32bit" JVMs (and the "/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre" that was being specified in the script, Tomcat does *not* like the "/qibm/ProdData/Java400/jdk6" JVM at all.

Can anybody explain why Tomcat would object to the "/qibm/ProdData/Java400/jdk6" JVM, yet be perfectly happy with the other Java 6 JVMs?

--
JHHL

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].