The security manager is causing lots of usability issues because it's difficult to get right, for little additional security (since we run as an unprivileged user). Upstream tomcat disables it by default. For Lucid, we are also considering disabling it by default (it will still be an option for those who know what they are doing).
For working around your bug, both solutions are valid. I'd suggest adding a policy file if you still want to run with the securitymanager on. -- Security manager breaks session listing https://bugs.launchpad.net/bugs/509528 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
