Hi, thanks for the prompt response. I'll forward you Sergey's email, I cannot find the message in the mailing list archives.
Thanks On 26 June 2014 09:39, Romain Manni-Bucau <[email protected]> wrote: > Hi > > That's not possible today. Do you have a link to the cxf list? seems highly > wrong to not cleanup everything on undeployment. Remember we undeployed not > that well in 1.6 but not sure it is linked or not > > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-06-26 14:34 GMT+02:00 [email protected] < > [email protected]>: > > > Hi All, > > > > I am facing a classloader leak on application redeployment on tomee > > (1.6.0.2). I tracked down the reason to the reflection metadata stored in > > CXF's ExtensionManagerBus, which is not removed on redeployment and > > prevents the classloader from being garbage collected. > > > > The problem seems to be a custom JAX-RS provider > (JacksonJaxbJsonProvider) > > which is registered using the getSingletons() method of my application > > subclass. I have asked in the CXF mailing list, and the best way to avoid > > that would be to use one Bus per endpoint, and recycle the bus when the > > application is undeployed. > > > > Any way we can configure Tomee so that it uses a bus per endpoint? Any > help > > would be greatly appreciated. > > > > Thanks in advance. > > >
