Server sends "big interger <val>" for config entries when a reload is needed ---------------------------------------------------------------------------- Key: AS7-4913 URL: https://issues.jboss.org/browse/AS7-4913 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Heiko Rupp Assignee: Brian Stansberry Priority: Minor Labels: rhq Fix For: 7.2.0.Alpha1 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" => {"process-state" => "restart-required"} } 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.