Michael Koch <[EMAIL PROTECTED]> (24/04/2008): > Before applying any patch I would like to be able to reproduce the > issue. What did you actually did in which order and which java packages > are installed? Did you installed tomcat5.5 from scratch or did you > updated it?
It was an update, but I just tried on another computer with a clean install, I have the same problem. Can you check the content of MANIFEST.MF in /usr/share/tomcat5.5/bin/bootstrap.jar, especially: Class-Path: jmx.jar commons-daemon.jar commons-logging-api-1.1.1.jar t omcat-juli.jar I don't have any commons-logging-api-1.1.1.jar in /usr/share/tomcat5.5/bin/, but a commons-logging-api.jar which is a symlink to /usr/share/java/commons-logging-api.jar. I guess one of the reason you can't reproduce the bug might be because you have a /usr/share/tomcat5.5/bin/commons-logging-api-1.1.1.jar which does not belong to any package. Note that MANIFEST.MF of tomcat 5.5.25 does contain the right Class-Path. Hope that helps. Cheers, -- Thomas Huriaux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]