Bug#453879: Purged tomcat5.5 leaves broken links in /var/lib/tomcat5.5/conf/Catalina/localhost

Jeffrey Baker jwbaker at acm.org
Sat Dec 1 23:00:34 UTC 2007


Package: tomcat5.5-webapps
Version: 5.5.20-2

If I install the webapps and then purge them, I get a bunch of broken links:

/var/lib/tomcat5.5/conf/Catalina/localhost/servlets-examples.xml: No
such file or directory
/var/lib/tomcat5.5/conf/Catalina/localhost/tomcat-docs.xml: No such
file or directory
/var/lib/tomcat5.5/conf/Catalina/localhost/ROOT.xml: No such file or directory
/var/lib/tomcat5.5/conf/Catalina/localhost/balancer.xml: No such file
or directory
/var/lib/tomcat5.5/conf/Catalina/localhost/webdav.xml: No such file or directory
/var/lib/tomcat5.5/conf/Catalina/localhost/jsp-examples.xml: No such
file or directory

This results in 20KB of error messages in my log at startup:

2007-12-01 17:49:35,059
[ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR
org.apache.catalina.startup.HostConfig - Error deploying configuration
descriptor jsp-examples.xml
java.io.FileNotFoundException:
/var/lib/tomcat5.5/conf/Catalina/localhost/jsp-examples.xml (No such
file or directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1543)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:565)
        at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
        at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1190)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:292)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
        at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1305)
        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1569)
        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1578)
        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1558)
        at java.lang.Thread.run(Thread.java:595)

And so forth.  Is there a reasonable way to purge these symlinks when
the package is uninstalled?





More information about the pkg-java-maintainers mailing list