Yes, by default we run Tomcat with a security manager, which means you need to configure rights for your application in the policy files.
See instructions at: http://tomcat.apache.org/tomcat-6.0-doc/security-manager-howto.html Given the complexity of getting security policy files right, depending on your environment it may make sense to run without the security manager (i.e. disabling TOMCAT_SECURITY). The security manager is just another layer for security in depth, restricting what the code run can ultimately do with your system. By the way, this is not a specificity in our Tomcat packaging... It would also fail with a stock Tomcat 6 if you enabled the security manager without configuring policy files to give proper rights to your application. Closing as invalid as this is not a bug. ** Changed in: tomcat6 (Ubuntu) Status: New => Invalid -- tomcat6 with spring throws org/springframework/core/NestedExceptionUtils https://bugs.launchpad.net/bugs/374567 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs