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

RANADEEP SHARMA edited comment on CXF-6938 at 6/21/16 9:24 PM:
---------------------------------------------------------------

Yes. I have found the cause of the problem. It was a glitch I made in the 
resource URI specified in my webClient.path() call. After correction, all is 
good.

I will ignore the log, as not related.

Thanks again. Appreciate your prompt responses.


was (Author: ranadeep.sha...@gmail.com):
Yes. I have found the cause of the problem. It was a glitch I made in the 
resource URI specified webClient.path() call. After correction, all is good.

I will ignore the log, as not related.

Thanks again. Appreciate your prompt responses.

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

Reply via email to