cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] [Commented] (CXF-6938) Setting the providers on a bus causes a leak if this bus is used by per-request clients
Date Tue, 21 Jun 2016 16:50:58 GMT


RANADEEP SHARMA commented on CXF-6938:

Hi Sergey,

Regarding the 4th correction suggested by you, I tested following configuration (as suggested
in Section "Configuring HTTP clients in Spring" at
), but the client seems unable to connect to the service.

<jaxrs-client:client id="customerServiceClient"
                  serviceClass="org.apache.cxf.jaxrs.client.WebClient" threadSafe="true">
            <ref bean="jsonProvider" />
            <bean name="exceptionHandler" class="com.mycompany.refapp.exception.AppExceptionHandler"/>

In the Tomcat log, I could see the following. Any pointers on what I am missing?

[2016-06-21 12:37:47,104][WARN ][org.apache.cxf.jaxrs.utils.ResourceUtils]: No resource methods
have been found for resource class org.apache.cxf.jaxrs.client.WebClient

> Setting the providers on a bus causes a leak if this bus is used by per-request clients
> ---------------------------------------------------------------------------------------
>                 Key: CXF-6938
>                 URL:
>             Project: CXF
>          Issue Type: Task
>          Components: Bus, JAX-RS
>    Affects Versions: 3.1.0, 3.1.6
>         Environment: Redhat Enterprise Linux (Santiago), OpenJDK 7, Tomcat 7
>            Reporter: RANADEEP SHARMA
>            Assignee: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 3.0.10, 3.1.7, 3.2.0
> 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.<hashCode>") populated while creating instances of ClientProviderFactory.
> 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
> Is this some sort of a bug or, lack of necessary configuration in CXF?
> Either ways, we need your guidance for trouble-shooting this issue.

This message was sent by Atlassian JIRA

View raw message