[
https://issues.apache.org/jira/browse/CXF-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharath Ganesh resolved CXF-1639.
---------------------------------
Resolution: Fixed
Verified the new memory leak fixes by profiling JAX-WS server and client
runtime. Also the complete Java EE TCK (JAX-WS 2.0 on CXF 2.0.7 snapshot) runs
in a single run with around 200M heap size. All looks OK.
> Memory leak due to literal keys in WSDLDefinition map
> -----------------------------------------------------
>
> Key: CXF-1639
> URL: https://issues.apache.org/jira/browse/CXF-1639
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1, 2.0.6
> Reporter: Bharath Ganesh
> Assignee: Bharath Ganesh
> Priority: Minor
> Fix For: 2.1.1, 2.0.7
>
>
> The definitionsMap in WSDLManagerImpl holds the WSDLDefinitions against a
> weak key, again relying
> on the WeakHashMap semantics for removal.
> The loadDefinition(String) method loads the WSDLDef and puts this in a map
> against a String key. But this String key, is a literal String and will be
> present in the constant pool, where garbage collection never happens. This
> would mean the key would always be referenced from the constant pool, and
> the entry would never be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
