I've got an application configured remote object that manages a couple of threads inside lcds. When I go to shutdown lcds I get this
SEVERE: The web application [/wrcastle] appears to have started a thread named [Thread-5] but has failed to stop it. This is very likely to create a memory leak.
the tasks aren't shutting down and I've got catches for handling the thread.interrupt() should proprogate down.
How do I cleanly shutdown my tasks?
Look at registering your own BootstrapService (See docs here). You can do anything you want in such a service (not just register runtime destinations) and the stop() method will get called when the MessageBroker servlet stop() method is called. You could then kill your threads here.
You could just ignore the messages from tomcat. If you are shutting down the VM, there will be no memory leak.
Thanks, this will do the trick. The memory leak messages aren't the correct
messages in closing down the problem is the threads were waiting and lcds
wasn't completely shutting down, now I can send a shutdown message to those