[
https://issues.apache.org/activemq/browse/SM-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1714.
---------------------------------
Resolution: Fixed
There were several fixes required for solving this:
- remove the CXF Bus being stored in a ThreadLocal inside the BusFactory for
both CXF components
- avoid using a connection pool for the WSN component's JMS connections
- fire endpoint events from a container thread instead of from a component's
thread to avoid ContextClassLoader/AccessControlContext being inherited by new
threads created from the listeners
http://svn.eu.apache.org/viewvc?view=rev&revision=722461 contains all the fixes
for the 3.2.x branch.
http://svn.eu.apache.org/viewvc?view=rev&revision=722487 fixes
container-related issues for the 3.3 trunk
http://svn.eu.apache.org/viewvc?view=rev&revision=722490 and
http://svn.eu.apache.org/viewvc?view=rev&revision=722489 fix the CXF component
problem
> OutOfMemoryException (PermGen) after redeploying servicemix-cxf* and
> servicemix-wsn2005
> ---------------------------------------------------------------------------------------
>
> Key: SM-1714
> URL: https://issues.apache.org/activemq/browse/SM-1714
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: servicemix-cxf-bc-2008.01, servicemix-cxf-se-2008.01,
> 3.2.3, 3.3
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-cxf-se-2008.02, servicemix-cxf-bc-2008.02,
> 3.3.1, 3.2.4
>
>
> Redeploying these two components leaves the component classloader in memory,
> resulting in PermGen memory not being released
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
