Remy Maucherat wrote:
> Jason Brittain wrote:
>
>>> "This release of Apache Tomcat was packaged to run on J2SE 5.0
>>> or later. It can be run on earlier JVMs by downloading and
>>> installing a compatibility package from the Apache Tomcat
>>> binary download page."
>>> means JMX wasn't found, that's all.
>>
>> Yes.
>>
>> I did:
>>
>> [root@localhost jakarta-tomcat-5.5.9]# export
>> CLASSPATH=/home/jbrittain/jakarta-tomcat-5.5.9/bin/jmx.jar
>>
>> and then started it again, and it still didn't find JMX (same message
>> in catalina.out). If that's what you meant, it didn't work.
>
> CLASSPATH is obviously ignored. This has been like that for years.
At first I thought that was the case, so I had a brief look in 5.5.9's
catalina.sh script and found this:
# Add on extra jar files to CLASSPATH
if [ -n "$JSSE_HOME" ]; then
CLASSPATH="$CLASSPATH":"$JSSE_HOME"/lib/jcert.jar:"$JSSE_HOME"/lib/jnet.jar:"$JSSE_HOME"/lib/jsse.jar
fi
CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/bootstrap.jar:"$CATALINA_HOME"/bin/commons-logging-api.jar
... which is used farther down like:
"$_RUNJAVA" $JAVA_OPTS $CATALINA_OPTS \
-Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" -classpath "$CLASSPATH" \
...
It must not have the effect on the JVM that I thought it may.
So then to what classpath should I add jmx.jar?
--
Jason Brittain
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
|