*CXF Component/s:* Bus, JAX-RS
*Affects Version/s:* 3.1.0, 3.1.6
*Environment:* Redhat Enterprise Linux (Santiago), OpenJDK 7, Tomcat 7
We have an application with REST client components for making calls to
Backend web services. During our routine performance test, JProfiler tool
shows lots of Bus property entries (with keys named "bus.providers.set.")
populated while creating instances of ClientProviderFactory.
*public final class ClientProviderFactory extends ProviderFactory {
public static ClientProviderFactory createInstance(Bus bus) {
...
factory.setBusProviders();
...
}*
These Bus property entries seem to stay in heap for the whole duration of
the 6 hour run. In fact, around 100,000 entries occupying 13 MB of heap. In
short, GC doesn't seem to happening frequently enough to keep the heap usage
within limits.
Is this some sort of a bug or, lack of necessary configuration in CXF to
optimize the creation/cleanup of these objects?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Unwanted-bunch-of-Bus-Provider-objects-in-HashMap-occupying-large-volumes-of-heap-memory-tp5769515.html
Sent from the cxf-user mailing list archive at Nabble.com.
