Hi Romilly, Your first solution doesn't work because when you stop the component, it stops the connectors and shuts downs the active socket connections including the one serving your shutdown request.
Your second solution sounds good to me. Make sure you leverage the Application#taskService to get your new thread. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Romilly Cocking [mailto:[email protected]] Envoyé : dimanche 15 mars 2009 12:24 À : [email protected] Objet : RE: InterruptedException when stopping component I've found a workaround; I start another thread and send stop() to the container after a 100 ms delay. It works, but it's not pretty. Is there a better solution? ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=13264 44 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1333512
