cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
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 20:11:57 GMT

    [ https://issues.apache.org/jira/browse/CXF-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342573#comment-15342573
] 

Sergey Beryozkin commented on CXF-6938:
---------------------------------------

You can ignore it as the runtime checks if a given class can be proxified or not.
No idea why the connection can not be set up - lets continue on the CXF users list or enable
the logging feature 

> 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
>             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
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)

Mime
View raw message