[
https://issues.apache.org/jira/browse/CXF-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-4778.
------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
Fix Version/s: 3.2.0
> Require Command Line Option for wsdl2java to set Maximum Heap Memory Size
> -------------------------------------------------------------------------
>
> Key: CXF-4778
> URL: https://issues.apache.org/jira/browse/CXF-4778
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.4.3
> Reporter: Rouble
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 3.2.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> By default wsdl2Java is coded to use 128M of maximum memory heap space.
> These days, however, WSDLs are starting to become very large and complex
> beasts - and sometimes wsdl2java will run out of heap space while creating
> its internal data structures. This is not an issue with memory management
> within wsdl2java, but rather a consequence of large WSDLs.
> Because of CXF-2081, we have the ability to set the maximum memory heap size,
> however it requires manually modifying wsdl2java. This is not ideal.
> This JIRA is requesting two things:
> a) A command line option -Xmx to wsdltojava, that allows users to set the
> maximum heap memory size.
> b) Upping the default maximum heap memory size to 256M. I leave this up to
> the development team to decide.
> UPDATE:
> Another option is for wsdl2java to inherit all the JAVA_OPTS from the
> environment. So, if someone properly sets -Xmx in the environment variable
> JAVA_OPTS, wsdl2java will pick it up. This is probably a better solution that
> will address more use cases.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
