Chuck, Thank you for your reply. What has lead me down this path is that I am trying to use Bootstrap.start() and .stop() to manage a Tomcat instance within a main that I have written. The behavior that I'm seeing is that it seems that .stop() does not actually cause the server to come all the way down and the second message to .start() does not seem to bring it back up.
So, while in a debug session I noticed one thread still hanging around after messaging .stop(). It seems to me that I should be able to manage the instance using .start() and .stop() assuming my understanding is correct. Given that, the behavior looks like one of two things to me, either some kind of bug, or more likely my lack of understanding of Tomcat internals being sufficient to manage the instance properly. I did see the Runnable being passed and made the assumption that it was being used to supply the run method. My probing through that source was to gain an understanding of the mechanism used to terminate the threads. I stopped there because I felt I was way in the weeds of Tomcat, beyond what should be necessary to accomplish my task. Fran -- View this message in context: http://www.nabble.com/Bootstrap-stop%28%29-tf3296281.html#a9207055 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
