[jboss-jira] [JBoss JIRA] (WFLY-2062) Composite response returns incorrect heap values
Heiko Braun (JIRA)
jira-events at lists.jboss.org
Fri Sep 13 09:17:03 EDT 2013
[ https://issues.jboss.org/browse/WFLY-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heiko Braun updated WFLY-2062:
------------------------------
Description:
Trying to read the heap memory usage from a host vm, we've disovered that a composite request through the http layer, returns bogus data (the numeric values are wrong).
This is the operation that we execute over HTTP:
{noformat}
{
"operation" => "composite",
"address" => [],
"steps" => [
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "memory")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "threading")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "runtime")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "operating-system")
],
"operation" => "read-resource",
"include-runtime" => true
}
]
}
{noformat}
Here's the response for the relevant heap section (wrong values):
{noformat}
{
"init" => 1366294528L,
"used" => 92433896L,
"committed" => 1309081600L,
"max" => 1309081600L
}
{noformat}
But the actual values (using CLI) are (correct values):
{noformat}
[domain at localhost:9999 /] /host=master/core-service=platform-mbean/type=memory:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"heap-memory-usage" => {
"init" => 67108864L,
"used" => 36680856L,
"committed" => 188547072L,
"max" => 477233152L
},
[...]
}
}
{noformat}
was:
Trying to read the heap memory usage from a host vm, we've disovered that a composite request through the http layer, returns bogus data.
This is the operation that we execute over HTTP:
{noformat}
{
"operation" => "composite",
"address" => [],
"steps" => [
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "memory")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "threading")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "runtime")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "operating-system")
],
"operation" => "read-resource",
"include-runtime" => true
}
]
}
{noformat}
Here's the response for the relevant heap section:
{noformat}
{
"init" => 1366294528L,
"used" => 92433896L,
"committed" => 1309081600L,
"max" => 1309081600L
}
{noformat}
But the actual values (using CLI) are:
{noformat}
[domain at localhost:9999 /] /host=master/core-service=platform-mbean/type=memory:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"heap-memory-usage" => {
"init" => 67108864L,
"used" => 36680856L,
"committed" => 188547072L,
"max" => 477233152L
},
[...]
}
}
{noformat}
> Composite response returns incorrect heap values
> ------------------------------------------------
>
> Key: WFLY-2062
> URL: https://issues.jboss.org/browse/WFLY-2062
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Beta1
>
>
> Trying to read the heap memory usage from a host vm, we've disovered that a composite request through the http layer, returns bogus data (the numeric values are wrong).
> This is the operation that we execute over HTTP:
> {noformat}
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "address" => [
> ("host" => "master"),
> ("server" => "server-one"),
> ("core-service" => "platform-mbean"),
> ("type" => "memory")
> ],
> "operation" => "read-resource",
> "include-runtime" => true
> },
> {
> "address" => [
> ("host" => "master"),
> ("server" => "server-one"),
> ("core-service" => "platform-mbean"),
> ("type" => "threading")
> ],
> "operation" => "read-resource",
> "include-runtime" => true
> },
> {
> "address" => [
> ("host" => "master"),
> ("server" => "server-one"),
> ("core-service" => "platform-mbean"),
> ("type" => "runtime")
> ],
> "operation" => "read-resource",
> "include-runtime" => true
> },
> {
> "address" => [
> ("host" => "master"),
> ("server" => "server-one"),
> ("core-service" => "platform-mbean"),
> ("type" => "operating-system")
> ],
> "operation" => "read-resource",
> "include-runtime" => true
> }
> ]
> }
> {noformat}
> Here's the response for the relevant heap section (wrong values):
> {noformat}
> {
> "init" => 1366294528L,
> "used" => 92433896L,
> "committed" => 1309081600L,
> "max" => 1309081600L
> }
> {noformat}
> But the actual values (using CLI) are (correct values):
> {noformat}
> [domain at localhost:9999 /] /host=master/core-service=platform-mbean/type=memory:read-resource(include-runtime=true)
> {
> "outcome" => "success",
> "result" => {
> "heap-memory-usage" => {
> "init" => 67108864L,
> "used" => 36680856L,
> "committed" => 188547072L,
> "max" => 477233152L
> },
> [...]
> }
> }
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list