[jboss-jira] [JBoss JIRA] (AS7-2445) CLI does not allow you to define all of the available JVM attributes

[Rich Raposa (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640772#comment-12640772 ] 

Rich Raposa commented on AS7-2445:
----------------------------------

Thanks - that syntax works. I can now add a JVM and specify the heap size:
/host=master/jvm=production_jvm:add(heap-size={"size"=>"2048m","max-size"=>"2048m"},permgen-size={"max-size"=>"512m"},stack-size="1024k",jvm-options=["-XX:-UseParallelGC"])

But when I look at the resource, the output is confusing:
[domain at localhost:9999 /] /host=master/jvm=production_jvm:read-resource(recursive=true)
{
    "outcome" => "success",
    "result" => {
        "agent-lib" => undefined,
        "agent-path" => undefined,
        "env-classpath-ignored" => undefined,
        "environment-variables" => undefined,
        "heap-size" => {
            "size" => "2048m",
            "max-size" => "2048m"
        },
        "java-agent" => undefined,
        "java-home" => undefined,
        "jvm-options" => ["-XX:-UseParallelGC"],
        "max-heap-size" => undefined,
        "max-permgen-size" => undefined,
        "permgen-size" => {"max-size" => "512m"},
        "stack-size" => "1024k",
        "type" => undefined
    }
}

The undefined attributes "max-heap-size" and "max-permgen-size" seem to be inconsistent and contradictory to my settings. So I think we have found the original cause of my confusion - I don't think max-heap-size and max-permgen-size should be displayed on a :read-resource invocation.
                
> CLI does not allow you to define all of the available JVM attributes
> --------------------------------------------------------------------
>
>                 Key: AS7-2445
>                 URL: https://issues.jboss.org/browse/AS7-2445
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Rich Raposa
>            Assignee: Alexey Loubyansky
>
> In attempting to define a new JVM for a host, the following command should work:
> [domain at localhost:9999 /] /host=master/jvm=small_jvm:add(heap-size=64m,max-heap-size=128m)
> 'max-heap-size' is not found among the supported properties
> max-heap-size is a valid attribute. Notice that max-permgen-size is also a valid attribute but is not allowed in the :add operation. Not being able to define these attributes seems to contradict the output of a :read-resource, which looks like:
> [domain at localhost:9999 /] /host=master/jvm=default:read-resource(recursive=true)
> {
>     "outcome" => "success",
>     "result" => {
>         "agent-lib" => undefined,
>         "agent-path" => undefined,
>         "env-classpath-ignored" => undefined,
>         "environment-variables" => undefined,
>         "heap-size" => "64m",
>         "java-agent" => undefined,
>         "java-home" => undefined,
>         "jvm-options" => undefined,
>         "max-heap-size" => "128m",
>         "max-permgen-size" => undefined,
>         "permgen-size" => undefined,
>         "stack-size" => undefined,
>         "type" => undefined
>     }
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira