Remy Maucherat schrieb:
The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.17/
According to the release process, the 6.0.17 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[ ] Stable
No final vote from my side, but a first test: if the shell scripts are
used (Linux, Unix) and conf/logging.properties gets removed/renamed in
order to use other means of logging, the JVM will not start.
The problem comes from the fact, that the shell variables JAVA_OPTS and
the new LOGGING_CONFIG are set inside catalina.sh only in the case the
file conf/logging.properties is readable. Otherwise they stay empty.
Later, when calling the java binary, we add JAVA_OPTS and
"LOGGING_CONFIG" as the first and second java parameters. An empty
JAVA_OPTS without quutation marks gets eaten by the shell, but an empty
LOGGING_CONFIG with quotation marks leads to an empty argument for the
JVM, which itself produces the error
Exception in thread "main" java.lang.NoClassDefFoundError:
without any class name given. That will be very strange for users.
You'll get the same error when calling e.g.
java "" -version
So we either need to remove the quotation marks (which means we'll run
into problems with spaces in path names, more precisely in
CATALINA_BASE), or we need to set LOGGING_CONFIG to something non void
but transparent to the JVM in case we don't want to use juli (e.g.
LOGGING_CONFIG=-Dcatalina.dummy), which will look strange e.g. in the
process table. Or we use different shell command lines in case
LOGGING_CONFIG is empty / is non-empty, which makes catalina.sh again
less understandable.
I don't know, if there is the same problem with the bat files.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
