12:31 a.m.
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: CLI
Reporter: Rich Raposa
Assignee: Alexey Loubyansky
In attempting to define a new JVM for a host, the following command should work:
[domain@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@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
7:25 a.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky updated AS7-2445:
-----------------------------------
Component/s: Domain Management
(was: CLI)
It is bug in the model description of the JVM resource.
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@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@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
3:32 p.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2445:
----------------------------------
Fix Version/s: 7.1.0.CR1
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
Fix For: 7.1.0.CR1
In attempting to define a new JVM for a host, the following command should work:
[domain@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@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
8:56 a.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky resolved AS7-2445.
------------------------------------
Fix Version/s: (was: 7.1.0.CR1)
Resolution: Rejected
I spoke too soon that it's a bug. It's not. Check the operation description. This
is how the relevant parameters are described:
"heap-size" => {
"type" => OBJECT,
"description" => "The Heap size settings allocated by
the JVM.",
"attributes" => {
"size" => STRING,
"max-size" => STRING
},
"required" => false
},
"permgen-size" => {
"type" => OBJECT,
"description" => "The JVM PermGen settings.",
"attributes" => {
"size" => STRING,
"max-size" => STRING
},
"required" => false
}
So, they are complex types. Here is how you should have done it:
[domain@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: [type, agent-lib,
agent-path, env-classpath-ignored, environment-variables, java-agent, java-home,
jvm-options, stack-size, heap-size, permgen-size]
[domain@localhost:9999 /]
/host=master/jvm=small_jvm:add(heap-size=>{"size"=>"64m","max-size"=>"128m"})
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => undefined
}
}
Now, maybe you find it over complicated to provide the arguments this way. If so, then
feel free to re-open and get comments from the author(s) of this stuff.
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@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@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
9:53 a.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
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@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@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@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
9:59 a.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky reopened AS7-2445:
------------------------------------
Re-opening. Will check.
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@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@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
9:10 a.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2445:
----------------------------------------
We talked with Emanuel and decided to fix the model description. I.e. it will be a flat
structure, like you assumed originally.
I've already committed the fix but it hasn't been merged yet.
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@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@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
10:40 a.m.
[
https://issues.jboss.org/browse/AS7-2445?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky resolved AS7-2445.
------------------------------------
Resolution: Done
The description of the resource and the add operation have been corrected, i.e. flattened,
i.e. heap-size and permgen children have become 4 simple attributes.
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@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@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
5075
days inactive
5084
days old
7 comments
7 participants
participants (7)
-
Alexey Loubyansky (Commented) (JIRA) -
Alexey Loubyansky (Reopened) (JIRA)
-
Alexey Loubyansky (Resolved) (JIRA)
-
Alexey Loubyansky (Updated) (JIRA)
-
Brian Stansberry (Updated) (JIRA)
-
Rich Raposa (Commented) (JIRA)
-
Rich Raposa (Created) (JIRA)