cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jp <jotpal.si...@melbourneit.com.au>
Subject ComponentFactory - decommissioning instance in component pool
Date Thu, 10 May 2012 04:45:08 GMT
Hi Guys,

I have configured a component pool as below

<component
    class="com.mycompany.ConfigImpl"
    pool-grow="4" pool-max="32" pool-min="8" role="com.mycompany.ConfigImpl">
    <parameter name="config-file" value="resources/myConfig.xml"/>
  </component>

Once we reach the max-pool size, I can see new instances are created if none is
available from the pool. 

My understanding is that these new instances will be destroyed once it is done
with the job. But whats happening is these instances are kept in the memory
forever and are not decommissioned. Because of this, the heap size grows with
time and the app's performance is affected.

Can someone suggest what may be root cause of this issue?

Thanks
JP


Mime
View raw message