Sriram, You should upgrade to 2.0.1 as we have fixed similar issues related to thread local variables.
Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : Sriram C [mailto:[email protected]] Envoyé : mercredi 1 septembre 2010 02:11 À : [email protected] Objet : RE: JAXRS, Transactional Resources managed by Spring Jerome, I am running with 2.0.RC2. I am not sure that there is a memory leak. However I have noticed that the service resource objects are not immediately cleaned up after a request has been fulfilled - they seem to linger around even after the request has been fulfilled. They seem to be getting garbage collected eventually since the peak memory usage doesn't exceed 0.8 GB out of a total of 3 GB. Is there any way I can configure or tune either Spring or Restlet or JVM settings for the resources to be gc'd immediately after the response is sent to the requestor? This will result in more efficient memory usage. This works fine for my current peak usage of ~200 requests a minute but I am afraid that this might be a bottleneck/performance impediment if I were to grow past my current usage. Any thoughts or ideas to address this issue would be highly appreciated. Sriram -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/JAXRS-Transactional-Resources-managed-by-Spring-tp5224091p5484973.html Sent from the Restlet Discuss mailing list archive at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2653844 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2657890
