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

Dhawalpatel commented on CXF-3978:
----------------------------------

Hi Daniel,
Thanks for clarifying!
I am sorry for being irritating but somehow I do not see that comment mentioned 
in this bug comments history. I tried to see the changes that he made in 
ManagedConnectionImpl class but could really make out that infact his changes 
also included caching the Bus and not call createBus every time. Can you please 
help me where in which class did he modify to cache the bus creation?
Thanks
Dhawal
                
> Multiple BusApplicationContext Objects created by CXF
> -----------------------------------------------------
>
>                 Key: CXF-3978
>                 URL: https://issues.apache.org/jira/browse/CXF-3978
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1
>         Environment: Production
>            Reporter: Dhawalpatel
>            Priority: Blocker
>
> Hi all, 
> Can anyone tell me if there was a known bug or issue wherein CXF creates a 
> new BusApplicationCOntext object for each outgoing Web Service call? I see 
> that while using JCA Connector architecture, SpringBusFactory object creates 
> a new BusApplicationContext object. Is it a bug? I am running CXF in 
> WebContainer thread pool of WAS and as the threads never gets killed due to 
> pool, the BusApplicationContext objects accumulates and results in high GC 
> memory. 
> Please help if this is a known bug in this version of CXF? We are in a 
> production down situation due to memory overhead created by 
> BusApplicationContext object size and number of these objects. there is 
> one-one correspondence between BusApplicatioContext to Thread in thread pool 
> which is causing memory to increase.
> The version of cxf-bundle-fuse is 2-1-3-18 
> THanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to