The only log output in /var/log/tomcat5 is: WARNING: System property "java.util.logging.manager" should be the name of a subclass of java.util.logging.LogManager Created MBeanServer with ID: [UID: 291096,1141140478345,-32768]:amilo:1 Moving tomcat-juli.jar away from /usr/share/tomcat5/bin/ avoids the warning and allows at least something to be logged Expected results: Reasonably useful logging by default, comparable with the tomcat 5.0 packages. Additional info: Was it really necessary to update to tomcat 5.5 from 5.0 after all test releases, six days before hard code freeze?
There is an updated rpm in dist-fc5-head with the tomcat-juli.jar removed. This works around the problem for now. Unfortunately the underlying issue is a buggy java.util.logging.LogManager implementation in the classpath version used by gcj, and that will take a bit longer to fix.
Does the underlying problem still exist in FC6/rawhide? If so, we should move the bug there. Otherwise I think this can be closed.
I was too happy to get away from Java programming, I'm afraid I don't have any recent tomcat installation around. The spec file still contains the following snippet, though: # disable the juli log manager until the classpath # java.util.logging.LogManager is fixed # XXX: Still not fixed - http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29869 rm -f $RPM_BUILD_ROOT%{bindir}/tomcat-juli.jar
PR 29869 is being addressed ATM. But yes, the inclusion of tomcat-juli.jar still causes a CNFE. I am changing the version for BZ to devel and monitoring activity on the above PR. Hopefully tomcat-juli.jar can be reinstated soon...
I have re-added the tomcat-juli.jar in $ koji latest-pkg --quiet f7-final tomcat5 tomcat5-5.5.23-9jpp.2.fc7 f7-final vivekl I *believe* this is now fixed. I am closing this bug but re-open if this reappears.