Bug 329421

I could reproduce this problem on my box, too. Will push a fix soon.

I have the same problem on Fedora 8, x86_64.

# rpm -qa | egrep "^tomcat5|^jakarta" | sort
jakarta-commons-beanutils-1.7.0-5jpp.1
jakarta-commons-collections-3.1-9jpp.2.fc7.1
jakarta-commons-collections-tomcat5-3.1-9jpp.2.fc7.1
jakarta-commons-daemon-1.0.1-6jpp.4.fc8
jakarta-commons-dbcp-1.2.1-10jpp.2.fc8
jakarta-commons-dbcp-tomcat5-1.2.1-10jpp.2.fc8
jakarta-commons-digester-1.7-6jpp.2
jakarta-commons-discovery-0.3-4jpp.1
jakarta-commons-el-1.0-8jpp.2.fc8
jakarta-commons-fileupload-1.0-6jpp.1
jakarta-commons-httpclient-3.0.1-1jpp.2.fc8
jakarta-commons-launcher-1.1-1jpp.3.fc8
jakarta-commons-logging-1.0.4-6jpp.4.fc8
jakarta-commons-modeler-2.0-3jpp.2.fc8
jakarta-commons-pool-1.3-9jpp.3.fc8
jakarta-commons-pool-tomcat5-1.3-9jpp.3.fc8
jakarta-commons-validator-1.1.4-5jpp.2.fc8
jakarta-oro-2.0.8-3jpp.1
jakarta-taglibs-standard-1.1.1-7jpp.1
tomcat5-5.5.26-1jpp.2.fc8
tomcat5-admin-webapps-5.5.26-1jpp.2.fc8
tomcat5-common-lib-5.5.26-1jpp.2.fc8
tomcat5-jasper-5.5.26-1jpp.2.fc8
tomcat5-jsp-2.0-api-5.5.26-1jpp.2.fc8
tomcat5-server-lib-5.5.26-1jpp.2.fc8
tomcat5-servlet-2.4-api-5.5.26-1jpp.2.fc8
tomcat5-webapps-5.5.26-1jpp.2.fc8

The fix mentioned above solves the problem...

This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

As I mentioned ... it still happened in FC8 !

Not sure if it's fixed in the very-latest fc8 package, but until recently ... 
it wasn't.

So please update version to FC8.

I have just gone to some trouble to verify this bug still exists in the latest
version of Fedora 8, after a full yum update (not tried on Fedora 9).  This
shouldn't be a hard fix!

This bug is still open on F9 and RHEL5.  However, the way I fixed it is
different, so maybe it's not the exact same issue...

For my install of Tomcat5, the problem appears to be with the permissions that
get set on /etc/tomcat5 when the tomcat-admin-app RPM is installed.  Recursively
chowning /etc/tomcat5 to tomcat:tomcat appears to fix the problem.

I figured this out pretty much by accident.  I thought I'd try to grab the
apache tomcat official admin app tarball and deploy it over /var/lib/tomcat5. 
Restart tomcat and the admin console starts working. 

I _think_ that the RPM wants to put the Catalina/localhost config into
/etc/tomcat5, so the chown fix only works for the admin app RPM.  I suspect that
the app config in the apache.org tarball, which puts the Catalina/localhost
config under /var/lib/tomcat5, is looking in a different place.  I'll do some
more testing and confirm...

Verified to still exist on F9.

Fixed by adding symlinks to commons-beanutils.jar and commons-digester.jar.

Not fixed by chown-ing /etc/tomcat5 to tomcat:tomcat.

I find it amazing/embarrassing this hasn't been fixed yet, it's so long that the project I was working on with Tomcat has long since finished.

To the maintainer - get your act sorted out (please)!

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping