You'd also need to make sure that you're calling terminate on the lookupDiscoveryManager that was passed in. If you are, then I'd check to see if Tomcat is right about the threads being kept around. It might be that they just take a few seconds to terminate.
Cheers, Greg. On Sat, 2012-04-21 at 05:01, Zsolt Kúti wrote: > Hello, > > When my webapp is undeployed Tomcat reports several threads that failed > to stop and leaks memory: > [multicast discovery response listener] > [multicast discovery request] etc. > During development redeployment is frequent causing problem sooner or > later. > > These threads come from LookupDiscovery passed to > ServiceDiscoveryManager instance. > Care is taken to call SDM.terminate() in servlet's destroy(). > > > Any advice on what is the suggested practice to use River in such > environment is appreciated. > > Thanks > Zsolt
