[Bug 404097] Re: Tomcat 6 init script spawns 3 Tomcat instances
László Monda
laci at monda.hu
Fri Jul 24 15:18:46 BST 2009
Here is a chat from #tomcat at freenode that pretty much explains it:
* nDuff tries to reproduce
<nDuff> umm
<nDuff> it's three process table entries, but that's just threads
<nDuff> it's only one copy of tomcat
<nDuff> NOTABUG.
<nDuff> mlaci, if you do a pstree on the lowest PID, you'll see that the other two are its children.
<mlaci> nDuff, yeah, that's true, but that doesn't make me understand why multiple instances are started by default
<nDuff> mlaci, they _aren't_ multiple instances, that's the point
<nDuff> mlaci, if you start Apache httpd with a multithreaded MPM, the threads will show up as separate process table entries...
<nDuff> mlaci, ...but that doesn't mean there's more than one copy of Apache in memory.
<nDuff> mlaci, ...looking more closely, it appears that the first two are part of jsvc; they're normal and harmless.
<nDuff> mlaci, ...see the "how jsvc works" section at http://commons.apache.org/daemon/jsvc.html
<mlaci> nDuff, the last url pretty much explains it. so 1) these processes are all needed to make tomcat work and 2) they don't consume 3 times more memory than a single tomcat process?
<nDuff> mlaci, (1) to make tomcat work in such a way that it can be controlled via jsvc commands, yes; (2) no, absolutely not.
--
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.
More information about the Ubuntu-server-bugs
mailing list