Public bug reported:

Binary package hint: tomcat5.5

Steps:
1. Using Ubuntu 8.04 Hardy Heron, i386, fully apt-get updated as of 2008/04/23.
2. Installed tomcat5.5 (5.5.25-5ubuntu1), tomcat5.5-admin (5.5.25-5ubuntu1), 
and sun-java6-jdk (6-06-0ubuntu1).
3. Tomcat works ok on localhost:8180/admin, I get the purple tomcat admin login 
page.
4. Edited /etc/tomcat5.5/tomcat-users.xml to create an administrator user and 
role for the localhost:8180/admin application.
5. Log into tomcat admin and create an instance:
6. In left frame, select Tomcat Server -> Service (Catalina) -> Host (localhost)
7. In right frame, select Create New Context
8. Enter a Document Base and Path (to a valid app, in this case the gong server 
from http://gong.ust.hk/ installed at the /gong path)
9. Click Save.
10. Click Commit Changes in the top frame, and OK in the alert box.
11. Logout, and restart tomcat (sudo /etc/init.d/tomcat5.5 restart).

This should allow me to go localhost:8180/gong but it does not. Upon
restarting tomcat5.5 the context has disappeared from the admin tool.

Some sleuthing reveals the following in the log:

23/04/2008 12:52:14 org.apache.catalina.storeconfig.StandardContextSF 
storeWithBackup
SEVERE: Cannot move orignal context output file at 
/etc/tomcat5.5/Catalina/localhost/gong.xml

and upon shutdown:

23/04/2008 12:52:22 org.apache.commons.modeler.Registry unregisterComponent
SEVERE: Error unregistering mbean 
java.security.AccessControlException: access denied (java.io.FilePermission 
/home/johnno/projects/gong-server/WEB-INF/lib/cos.jar read)
        at 
java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
        at 
java.security.AccessController.checkPermission(AccessController.java:546)
        at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
        at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
        at java.util.zip.ZipFile.<init>(ZipFile.java:109)
        at java.util.jar.JarFile.<init>(JarFile.java:133)
        at java.util.jar.JarFile.<init>(JarFile.java:97)
        at 
org.apache.catalina.loader.WebappClassLoader.openJARs(WebappClassLoader.java:1765)
        at 
org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1995)
        at 
org.apache.catalina.loader.WebappClassLoader.findResource(WebappClassLoader.java:936)
        at 
org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:299)
        at 
org.apache.juli.ClassLoaderLogManager$2.run(ClassLoaderLogManager.java:273)
        at java.security.AccessController.doPrivileged(Native Method)
        at 
org.apache.juli.ClassLoaderLogManager.getClassLoaderInfo(ClassLoaderLogManager.java:270)
        at 
org.apache.juli.ClassLoaderLogManager.getLogger(ClassLoaderLogManager.java:175)
        at java.util.logging.Logger.getLogger(Logger.java:275)
        at com.sun.jmx.trace.TraceManager.getLogger(TraceManager.java:166)
        at com.sun.jmx.trace.TraceManager.isSelected(TraceManager.java:197)
        at com.sun.jmx.trace.Trace.isSelected(Trace.java:84)
        at com.sun.jmx.mbeanserver.Repository.isTraceOn(Repository.java:68)
        at com.sun.jmx.mbeanserver.Repository.contains(Repository.java:471)
        at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.isRegistered(DefaultMBeanServerInterceptor.java:593)
        at 
com.sun.jmx.mbeanserver.JmxMBeanServer.isRegistered(JmxMBeanServer.java:598)
        at 
org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:612)
        at 
org.apache.catalina.core.StandardWrapper.stop(StandardWrapper.java:1706)
        at 
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4350)
        at 
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:893)
        at 
org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1180)
        at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1151)
        at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:313)
        at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
        at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1055)
        at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067)
        at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448)
        at 
org.apache.catalina.core.StandardService.stop(StandardService.java:510)
        at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734)
        at org.apache.catalina.startup.Catalina.stop(Catalina.java:602)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.catalina.startup.Bootstrap.stop(Bootstrap.java:307)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.commons.daemon.support.DaemonLoader.stop(DaemonLoader.java:200)
23/04/2008 12:52:22 org.apache.catalina.loader.WebappClassLoader 
findResourceInternal
INFO: Illegal access: this web application instance has been stopped already.  
Could not load logging.properties.  The eventual following stack trace is 
caused by an error thrown for debugging purposes as well as to attempt to 
terminate the thread which caused the illegal access, and has no functional 
impact.

When I create the /etc/tomcat5.5/Catalina/localhost/gong.xml file
manually, it all works and the /gong app works as normal.

Testing with other apps seems to suggest that tomcat5.5 (for some
reason) can't create the initial xml file in
/etc/tomcat5.5/Catalina/localhost - and also fails when it tries to copy
the non-existent file to a timestamped backup.

** Affects: tomcat5.5 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Creating a new context using the /admin interface does not commit changes.
https://bugs.launchpad.net/bugs/220871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to