From: danch <da...@nv...> - 2001-05-12 02:39:14
|
Jim Archer wrote: > Hello.. > > --On Friday, May 11, 2001 8:25 AM +0100 "Kimpton,C (Chris)" > <Kim...@ra...> wrote: > >>> So if each java process I see is a thread within the same VM, >>> does anyone >>> know what causes a new thread to be started? >>> >> >> new Thread(); >> >> ;-) > > > Yeah, OK... > > >> I presume you have a performance problem and your trying to track down >> where things are slow? In which case look at optimisation tools.... > > > Not necesserally a performance problem. We have been load testing for > the purpose of seeing what might fall over and I was just trying to get > an understanding of what the app server is doing, how much RAM is being > used, and so on. Ultimately, we hope to be running our app on a > Debian/Linux box with Jetty, jBoss and PostgreSQL. > > All the threads also raise a shutdown question. We have written an > init.d script to gracefully start and stop jBoss as a server task, in > the same manner as other Debian processes. If the script issues a kill > to each thread, will this produce a gracefull shutdown, or will it > terminate each thread ungracefully? > The kill should be sent to the parent of all the threads. If you look at ps -axf output you'll see that run.sh spawns one process, which is then the parent for all the threads. A change in run.sh to save the pid of the java process into a file in var would be the best way to accomplish this. -danch |