Hi Gena,
This bug should now be fixed in the recent versions of Restlet 2.0 and 2.1. Best regards, Jerome -- <http://www.restlet.org/> http://www.restlet.org http://twitter.com/#!/jlouvel De : gena [mailto:[email protected]] Envoyé : vendredi 1 avril 2011 16:45 À : [email protected] Objet : EncodeRepresentation causes dead threads Hello, it seems, like the EncodeRepresentation#getStream produces each time a new ThreadPool. The newly created threads by those pools still present also after the response proceeded and will not be reused. If i disable the EncodeService (or don't wrap my repsonse within the EncodeRepresentation) the problem doesn't occur. It could also be a cause of last part of my earlier post http://restlet-discuss.1400322.n2.nabble.com/GZip-Deflate-response-truncated -java-io-IOException-Timeout-while-writing-to-the-queue-based-output-m-td623 0386.html The question is, how should i serve the Gzip/Deflate responses? Thanks, Gena. _____ View this message in context: EncodeRepresentation causes dead threads <http://restlet-discuss.1400322.n2.nabble.com/EncodeRepresentation-causes-de ad-threads-tp6231274p6231274.html> Sent from the Restlet Discuss mailing list archive <http://restlet-discuss.1400322.n2.nabble.com/> at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2854742
