Bug#316580: tomcat4 with kaffe and security manager does not start

2006-09-15 Thread Arnaud Vandyck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This bug should have been close with new upload of kaffe

- --
Arnaud http://www.ressource-toi.org
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFCn0h4vzFZu62tMIRAlSuAJ9kIxrRPYtEySTJU0lvO++dKtgaKQCeJrtg
IjYAg4XoTc332wAc9BehRyU=
=5X74
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#316580: tomcat4 with kaffe and security manager does not start

2005-07-08 Thread Wolfgang Baer
Michael Koch wrote:
 On Thu, Jul 07, 2005 at 11:20:19PM +0200, Andreas Krüger wrote:
[...]
 
 For Sarge its too late to change this. Your best option is to use a backport
 of kaffe from testing/unstable. I will soon start to create them when kaffe
 get uploaded in a new version.

Hi Michael, I work on a new kaffe package atm and will ask Arnaud if
he has time to upload in a few days.

Wolfgang


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#316580: tomcat4 with kaffe and security manager does not start

2005-07-08 Thread Michael Koch
On Fri, Jul 08, 2005 at 09:24:31AM +0200, Wolfgang Baer wrote:
 Michael Koch wrote:
  On Thu, Jul 07, 2005 at 11:20:19PM +0200, Andreas Krüger wrote:
 [...]
  
  For Sarge its too late to change this. Your best option is to use a backport
  of kaffe from testing/unstable. I will soon start to create them when kaffe
  get uploaded in a new version.
 
 Hi Michael, I work on a new kaffe package atm and will ask Arnaud if
 he has time to upload in a few days.

Thanks. TEll me when its in. Then I can backport it to sarge and upload to 
backports.org
for people running Sarge.


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

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



Bug#316580: tomcat4 with kaffe and security manager does not start

2005-07-07 Thread Michael Koch
On Thu, Jul 07, 2005 at 11:20:19PM +0200, Andreas Krüger wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Michael Koch wrote:
 
  You are really suggesting to deactivate the security manager by default?
 
 What I really suggest is: When I install Sarge Tomcat on a Sarge box,
 together with all packages it depends on, it should operate.
 
 Personally, I much rather deactivate the security manager, than throw
 Tomcat 4 out of Sarge main back into contrib. I am willing to go with
 Tomcat 4 rather than Tomcat 5, and make do without this, that, and the
 other feature, if that buys me free software. The web application that I
 intend to deploy has not yet been written, so I can make it happen.
 
  The bug is in kaffe not tomcat4. Tomcat4 works fine with other runtimes with
  security manager enabled. The bug in kaffe is fixed in CVS and probably in
  unstable too.
 
 Good to know. Thank you for the information.
 
 This particular bug is concerned with Sarge, though. This will be a
 production server (of sorts). The security team's backing is important
 for me, for whatever I end up running.
 
  I can't check currently. This needs to be checked and this bug
  needs then get moved to kaffe and tagged sarge.
 
 Disabling the security manager is not something to be taken lightly, yes.
 Pulling a brand-new release of kaffe into Sarge is not to be taken lightly,
 either.  Which of these two, or maybe what else, is the best way for Debian
 to get Tomcat Sargly running?

For Sarge its too late to change this. Your best option is to use a backport
of kaffe from testing/unstable. I will soon start to create them when kaffe
get uploaded in a new version.

 I tend to lean towards pulling kaffe, if that is an option. Is it? I am
 not sure what the right answer is. In particular, I am an old hat at
 Tomcat, but fairly new as a Kaffe user. So I cannot judge the relative
 stability of the Kaffe version presently in Sarge, vs. the Kaffe version
 that has the bug fix.  Me, I just file them bugs ;-) ...

Thanks for doing this.


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

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



Bug#316580: tomcat4 with kaffe and security manager does not start

2005-07-04 Thread Michael Koch
On Sat, Jul 02, 2005 at 03:48:47AM +0200, Andreas Krüger wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Package: tomcat4
 Version: 4.1.31-3
 Severity: normal
 
 I installed tomcat4 and tomcat4-admin on a Sarge machine.
 
 That machine is a server and has few other software
 packages installed. In particular, the tomcat4 installation
 caused aptitude to install a host of other packages
 (I did not fully analyse what decisions aptitude made).
 
 I did not change anything and try to start tomcat.
 
 That did not work. In catalina_DATE.log, I received:
 
 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)
 
 I checked /usr/share/doc/tomcat4, and a few tomcat4 bug reports
 on the debian bug tracking system.
 
 One bug report suggested to remove the documentation stance from the
 server.xml, so I did that.  I also removed the Apache connector, which
 I'm not needing for my setup. - Same error, tomcat again does not start.
 
 So I uncommented lines in /etc/defaults/tomcat4,
 and disabled the security manager.
 
 Now tomcat came up nicely and displayed the (empty) directory content.
 
 It would be very nice if you came up with a configuration that allows
 tomcat to start out of the box.

You are really suggesting to deactivate the security manager by default?
The bug is in kaffe not tomcat4. Tomcat4 works fine with other runtimes with
security manager enabled. The bug in kaffe is fixed in CVS and probably in
unstable too. I cant check currently. This needs to be checked and this bug
needs then get moved to kaffe and tagged sarge.


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

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