JRebel is intended to be used in development, not in production. In production, you want to undeploy and redeploy your application and, hopefully, leave no old ClassLoader reference behind.
I'm not sure if InheritableThreadLocal will create memory leaks, but I know it is something to be very carefully considered. On Wed, May 19, 2010 at 2:35 PM, James Carman <ja...@carmanconsulting.com>wrote: > On Wed, May 19, 2010 at 11:56 AM, Adriano dos Santos Fernandes > <adrian...@gmail.com> wrote: > > > > I suggest to not change something in a minor release that breaks things > that > > is working. I also suggest this shouldn't be done by default in major > > releases as well. > > > > I see no way JRebel or any tool going to remove thread locals knowing > what > > its being done. > > JRebel won't require totally blowing away your application object. > It'll just swap out the underlying logic behind it when you restart > your application. >
