1) Why do you deploy the .jar and .war separately? If the .jar is an ejb-jar file, you should put them both into a single .ear file. This will also allow you to use local interfaces and improve performance.
2a) You can add a destroy() method to your servlet that can stop your custom threads. Of course, that depends on you keeping a handle on them when you start them (I'm assuming from your servlet's init() method). 2b) An alternative to your servlet starting and stopping your threads, if your using the 2.3 servlet api, you can register a context listener, where you can receive events when your webapp starts and stops, and manage your threads there. Hope this helps, David -- Frank Morton wrote: > Using 3.0.0. I have an application that I deploy > as a .jar and a .war file separately. Running under > supervision of jetty is a servlet that starts and allows > to run continually a number of Threads. > > When I redeploy the application (actually undeploy > and then deploy), the old threads continue to run. > > How can I stop them as part of the deploy process? > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
