I think this might be related to this issue: http://restlet.tigris.org/issues/show_bug.cgi?id=621
--tim On Sat, Feb 28, 2009 at 11:12 AM, Jerome Louvel <[email protected]>wrote: > Hi Felix, > > This is interesting, it appears that we miss some clean-up actions for > these > thread-local variables that we use... I've entered a bug report: > > "Memory leaks due to thread local variables" > http://restlet.tigris.org/issues/show_bug.cgi?id=747 > > 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 : Felix Leipold [mailto:[email protected]] > Envoyé : lundi 23 février 2009 19:34 > À : [email protected] > Objet : Restlet + Spring + Tomcat memory problems > > Hi Guys, > > we are using restlet with spring on tomcat. We use the > RestletFrameWorkServlet in which we pass a class extending SpringRouter. > Everything seemed to stop nicely. All our destroy methods got called, but > somehow all the application classes stuck. > > After some memory debugging we came up with a workaround using a filter > that > does this: > > chain.doFilter(request, response); > > Response.setCurrent(null); > Application.setCurrent(null); > Context.setCurrent(null); > > Thereby resetting all the ThreadLocals in these classes. This seems a bit > hackish. Is there anything we overlooked in our setup? > > Thanks, > > Felix > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=12158 > 40 > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1245477 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1245539
