[
https://issues.jboss.org/browse/WFCORE-1394?page=com.atlassian.jira.plugi...
]
Martin Simka moved JBEAP-3458 to WFCORE-1394:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1394 (was: JBEAP-3458)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 2.1.0.CR1
(was: 7.0.0.ER5)
default maxPermgen is added when jvm isn't configured
------------------------------------------------------
Key: WFCORE-1394
URL:
https://issues.jboss.org/browse/WFCORE-1394
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.1.0.CR1
Reporter: Martin Simka
Assignee: Brian Stansberry
Default maxPermgen size is added when {{jvm}} element isn't specified in
domain.xml/host.xml and warning is logged.
{code:xml}
<server-group name="main-server-group" profile="default">
<!--
<jvm name="default">
<heap size="64m" max-size="512m"/>
</jvm>
-->
<socket-binding-group ref="standard-sockets"/>
</server-group>
{code}
{noformat}
WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: null
{noformat}
It happens because default is defined in
[
JvmElement.java#L76|https://github.com/wildfly/wildfly-core/blob/master/h...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)