Hi Nina,
We had some issues with our automated build (fixed now), so I would recommend trying the latest snapshot again if you still have the issue. If you want to prevent automatic thread creation, you can either: 1. Create a Client(Protocol.HTTP) instance and attach it to each ClientResource via setNext() 2. Use another HTTP connector such as Apache HTTP client by adding org.restlet.ext.httpclient.jar in your classpaht (+ dependencies) The fix in the latest snapshot should however take care of collecting the automatically created client connectors/threads. Best regards, Jerome Louvel -- Restlet ~ Founder and Technical Lead ~ <http://www.restlet.org/> http://www.restlet.org Noelios Technologies ~ <http://www.noelios.com/> http://www.noelios.com De : Nina Jeliazkova [mailto:[email protected]] Envoyé : mardi 29 juin 2010 13:50 À : [email protected] Objet : Re: ClientResource leaves inactive thread Tim Peierls wrote: On Thu, Jun 24, 2010 at 11:52 AM, Nina Jeliazkova <[email protected]> wrote: Tim Peierls wrote: What was the date of that snapshot? It looks like there's a fix as of June 11, revision 6696 in svn. Not sure about the date, it's the snapshot, available in the maven repository, http://maven.restlet.org/org/restlet/jee/org.restlet/2.0-SNAPSHOT/org.restle t-2.0-SNAPSHOT.pom So it depends on when you downloaded it, since the snapshot changes. The snapshot was downloaded (via maven) and tested June 22 (first post in this thread). Today snapshot seems to have the thread leak fixed. I would actually prefer a configurable ClientResource, to be able to switch on/off launching separate threads - does this already exist? Have you tried using something other than the internal connector? The leak was found when running some service under Tomcat , and then reported to me, so it's not specific to the internal connector. Regards, Nina --tim ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2628674
