Bug#308745: Tomcat 4 fails to start with Kaffe; Security Manager issue

[Michael Koch]

On Thu, May 12, 2005 at 01:25:10AM -0400, Barry Hawkins wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Package: kaffe
> Version: 1.1.5-3
> Severity: normal
> Tags: upstream
> 
> Tomcat 4 packaged by Debian no longer starts up successfully on kaffe's
> current package version in Sarge.  The output from an attempted startup
> on an i386 Sarge installation yields the following output in
> /var/log/tomcat4/catalina_YYYY-MM-DD.log:
> 
> Stopping service Tomcat-Standalone
> May 11, 2005 1:20:08 PM org.apache.coyote.http11.Http11Protocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-8180
> Using CATALINA_BASE:   /var/lib/tomcat4
> Using CATALINA_HOME:   /usr/share/tomcat4
> Using CATALINA_TMPDIR: /var/lib/tomcat4/temp
> Using JAVA_HOME:       /usr/lib/kaffe
> Using Security Manager
> Internal error: caught an unexpected exception.
> Please check your CLASSPATH and your installation.
> java/lang/ExceptionInInitializerError
>         at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:772)
> 
> Discussions on IRC between Michael Koch, Dalibor Topic, and myself
> currently lead to suspicions about the Security Manager in use by
> Tomcat.  Dalibor is of the opinion that Kaffe's Classpath library does
> not like that another Security Manager other than its own is being used.

A way around this is to disable the security manager in /etc/default/tomcat4
(NOT RECOMMENDED, do this only if you know what you are doing).

Simple tests shows that only kaffe gives such a strange error message.
E.g. Jamvm seems to work with any security manager. This might be an
bootstrapping problem in kaffe. I will investigate this.


Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/