Details
-
Bug
-
Resolution: Done
-
Minor
-
7.1.2.Final (EAP)
Description
RHQ sends JSON like this to change e.g. the max-pool-size setting of a data source:
{"operation":"composite","steps":[{"operation":"write-attribute","address":[
{"subsystem":"datasources"},
{"data-source":"ExampleDS"}],"name":"max-pool-size","value":75},{"operation":"write-attribute","address":[
{"subsystem":"datasources"},
{"data-source":"ExampleDS"}],"name":"use-fast-fail","value":false}],"address":[]}
Server returns success.
When I directly go to the cli afterwards I see:
[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=max-pool-size)
{
"outcome" => "success",
"result" => big integer 75,
"response-headers" =>
}
Note the "big integer"
[standalone@localhost:9999 /] /:reload
{"outcome" => "success"}[standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=max-pool-size)
{
"outcome" => "success",
"result" => 75
}
[standalone@localhost:9999 /]
Now the server acts as always.
Attachments
Issue Links
- clones
-
DMR-2 CLONE - Server sends "big interger <val>" for config entries when a reload is needed
- Resolved
- is blocked by
-
AS7-6139 ModelTypeValidator is overly lenient about numeric types
- Resolved
-
AS7-6140 Upgrade jboss-dmr to 1.1.4
- Resolved
- relates to
-
WFLY-572 "Cast" model nodes in AttributeDefinition validateOperation()
- Closed