[Bug 404097] [NEW] Tomcat 6 init script spawns 3 Tomcat instances
Public bug reported: I've recently used Tomcat on Intrepid and Jaunty. On both of them I've experienced the same problem: There are 3 Tomcat instances spawned by the tomcat6 init script. I'm aware that there are efforts to make the Tomcat init scripts more developer friendly outlined by http://ubuntuserver.wordpress.com/2008/09/01/tomcat-6-lands-in-intrepid/ for example, but I didn't install the tomcat6-user package so there should only be one tomcat instance by default. There is 1 instance owned by the tomcat6 user that does some real work and 2 other instances owned by root that do nothing. Doing a little investigation in the tomcat6 init script it seems that the $DAEMON -user $TOMCAT6_USER -cp $JSVC_CLASSPATH -outfile SYSLOG -errfile SYSLOG -pidfile $CATALINA_PID $JAVA_OPTS $BOOTSTRAP_CLASS command spawns all the instances which is strange to me because I'd expect a much more sophisticated solution like checking the user home dirs for tomcat-related configuration information from the init script and starting the instances accordingly. I have two questions: 1) Why does the init script behave the way it does? 2) Is it possible to change the default behaviour (using only one instance) or is it hardcoded? Thanks! ** Affects: tomcat6 (Ubuntu) Importance: Undecided Status: New -- Tomcat 6 init script spawns 3 Tomcat instances https://bugs.launchpad.net/bugs/404097 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
[Bug 404097] [NEW] Tomcat 6 init script spawns 3 Tomcat instances
Public bug reported: I've recently used Tomcat on Intrepid and Jaunty. On both of them I've experienced the same problem: There are 3 Tomcat instances spawned by the tomcat6 init script. I'm aware that there are efforts to make the Tomcat init scripts more developer friendly outlined by http://ubuntuserver.wordpress.com/2008/09/01/tomcat-6-lands-in-intrepid/ for example, but I didn't install the tomcat6-user package so there should only be one tomcat instance by default. There is 1 instance owned by the tomcat6 user that does some real work and 2 other instances owned by root that do nothing. Doing a little investigation in the tomcat6 init script it seems that the $DAEMON -user $TOMCAT6_USER -cp $JSVC_CLASSPATH -outfile SYSLOG -errfile SYSLOG -pidfile $CATALINA_PID $JAVA_OPTS $BOOTSTRAP_CLASS command spawns all the instances which is strange to me because I'd expect a much more sophisticated solution like checking the user home dirs for tomcat-related configuration information from the init script and starting the instances accordingly. I have two questions: 1) Why does the init script behave the way it does? 2) Is it possible to change the default behaviour (using only one instance) or is it hardcoded? Thanks! ** Affects: tomcat6 (Ubuntu) Importance: Undecided Status: New -- Tomcat 6 init script spawns 3 Tomcat instances https://bugs.launchpad.net/bugs/404097 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
