]
Brian Stansberry updated AS7-4436:
----------------------------------
Fix Version/s: 7.1.2.Final-redhat1
Assignee: Brian Stansberry (was: Kabir Khan)
setting debug-enabled and debug-options via dmr does not work
-------------------------------------------------------------
Key: AS7-4436
URL:
https://issues.jboss.org/browse/AS7-4436
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Brian Stansberry
Labels: debug-enabled, debug-options, jvm
Fix For: 7.1.2.Final-redhat1
Setting the following jvm configuration works, including *debug-enabled* and
*debug-options*:
(see also
https://issues.jboss.org/browse/AS7-1606)
{code:xml}
<servers>
<server name="server-1" group="server-group-1"
auto-start="true">
<jvm name="default" java-home="C:/eplatform/java/jdk1.7.0"
debug-enabled="true"
debug-options="runjdwp:transport=dt_socket,address=13013,server=y,suspend=n">
<heap size="128m" max-size="256m" />
<permgen size="64m" max-size="128m" />
<stack size="512k" />
</jvm>
<socket-bindings port-offset="100" />
</server>
</servers>
{code}
however, *setting these two attributes via dmr does not work*. The following operation:
{code:xml}
{
"operation" => "add",
"address" => [
("host" => "master"),
("server-config" => "server-1"),
("jvm" => "default")
],
"java-home" => "C:/eplatform/java/jdk1.7.0",
"debug-enabled" => "true",
"debug-options" =>
"runjdwp:transport=dt_socket,address=13013,server=y,suspend=n",
"heap-size" => "128m",
"max-heap-size" => "256m",
"permgen-size" => "64m",
"max-permgen-size" => "128m",
"stack-size" => "512k"
}
{code}
results in:
{code:xml}
<servers>
<server name="server-1" group="server-group-1"
auto-start="true">
<jvm name="default"
java-home="C:/eplatform/java/jdk1.7.0">
<heap size="128m" max-size="256m"/>
<permgen size="64m" max-size="128m"/>
<stack size="512k"/>
</jvm>
<socket-bindings port-offset="100"/>
</server>
</servers>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: