[jira] [Updated] (CXF-6938) Setting the providers on a bus causes a leak if this bus is used by per-request clients

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin updated CXF-6938:
----------------------------------
    Priority: Minor  (was: Major)
     Summary: Setting the providers on a bus causes a leak if this bus is used by per-request clients  (was: Unwanted bunch of Bus Provider objects in HashMap occupying large volumes of heap memory)

> Setting the providers on a bus causes a leak if this bus is used by per-request clients
> ---------------------------------------------------------------------------------------
>
>                 Key: CXF-6938
>                 URL: https://issues.apache.org/jira/browse/CXF-6938
>             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
>
> 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 limits.
> 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
(v6.3.4#6332)