I'm pretty sure this is because the user is bundling their own rest easy jars in EAR/lib. The API caches stuff in statics, which is keeping a reference to the user deployed RESTeasy.
Stuart On 15/02/2012, at 2:17 AM, Scott Marlow wrote: > https://community.jboss.org/message/716191 is an AS7 user forum thread > about application classloader leaks in a few different areas. > > All of them involve a Seam 2.2.2 application using Resteasy 2.3.1. One > of the leaks is described in jira RESTEASY-660. > > Is there something that the users application has to do, to get Seam > 2.2.2 to call ResteasyProviderFactory.clearContextData() at the end of a > request? > > Scott > -------- Original Message -------- > Subject: Re: [jboss-as7-dev] help needed with responding to reported > classloader leaks in (Rest, Rest WS, JPA, EJB3 activation/passivation, > other)... > Date: Tue, 14 Feb 2012 07:33:29 -0500 > From: Bill Burke <[email protected]> > To: [email protected] > > > > On 2/13/12 12:59 PM, Scott Marlow wrote: >> org.jboss.resteasy.util.ThreadLocalStack creates ThreadLocal pseudo-leak >> on AS 7: https://issues.jboss.org/browse/RESTEASY-660 >> " >> > > This may be Seam related. > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > _______________________________________________ > jboss-as7-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
