[
https://issues.apache.org/jira/browse/CXF-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950401#comment-14950401
]
Giovanni Borelli edited comment on CXF-6632 at 10/9/15 1:52 PM:
----------------------------------------------------------------
I totally agree with you, my "fix" is just a proof of concept that I am using
to prevent the production environment to crash every 10 minutes because of an
OutOfMemory Exception.
Anyway in my case there is no need for a WSDL cache: the application uses a
single WSDL one or two times in it's entire life cycle.
Is there a way to completely disable it?
was (Author: gio):
I totally agree with you, my "fix" is just a proof of concept that I am using
to prevent the production environment to crash every 10 minutes because of an
OutOfMemory Exception.
Anyway in my case there is no need for a WSDL cache: the application uses the
single WSDL one or two times in it's entire life cycle.
Is there a way to completely disable it?
> Memory leak due to literal keys in WSDLDefinition map
> -----------------------------------------------------
>
> Key: CXF-6632
> URL: https://issues.apache.org/jira/browse/CXF-6632
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.7.17
> Reporter: Giovanni Borelli
> Assignee: Bharath Ganesh
>
> Looks like 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 even if it was passed as a URL through
> getDefinition(URL).
> Like the https://issues.apache.org/jira/browse/CXF-1639 this causes a memory
> leak.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
