Hi
On 26/06/14 04:32, [email protected] wrote:
Hi All,
hope you are doing well. We've been using Tomee as our application server
lately (we have some basic JAX-RS APIs), and after several redeployments we
get a PermGen space error. I've been digging into the heap dump, and from
what I see our custom JAX-RS provider (JacksonJaxbJsonProvider) is being
referenced inside ExtensionManagerBus's properties and never unregistered.
I'm pretty sure it's Tomee's fault, because it should be doing due cleanup
on undeployment, but I was wondering whether the ExtensionManagerBus has
any way of removing the registered providers.
CXF JAX-RS checks provider context properties when it registers
providers and stores reflection-specific information and proxies on the
bus, it does not store the actual providers.
Do you have some more info how Bus ends up linking to the provider ?
We have a feature allowing providers registered directly on the bus via
bus properties, is it what is being done in your case ?
If not then I'm not sure. ProviderFactory holding providers is
registered on the endpoint but I'm not seeing the code where the
endpoint is registered on the bus.
Either way, the problem appears to be originating from the fact that a
single shared bus is used between multiple endpoints in Tomee. Is it
possible in Tomee endpoint descriptors set up an endpoint specific bus ?
For example, in Spring/Blueprint descriptors which can declare a new CXF
Bus and have jaxrs/jaxws endpoints linking to it and this bus would be
recycled on the redeployment.
So, please let me know:
- if you have more info about the link from Bus to providers
- check if providers are registered directly on the bus (check its
properties like "javax.ws.rs.ext.MessageBodyReader")
- check if Tomee allows creating endpoint specific buses
Lets us know please how it goes
Thanks, Sergey
Any help would be appreaciated
Thanks in advance.
