6. # observe the correct max is now reflected in the statistics[domain@localhost:9999 /] /host=master/server=server-one/subsystem=datasources/data-source=ExampleDS/statistics=pool:read-attribute(name=AvailableCount)

{
"outcome" => "success",
"result" => "10"
}

Actual results:
The AvailableCount is reflected as per the changed max-pool-size only after server restarts.

Expected results:
After changing the max-pool-size of the datasource, the AvailableCount should be reflected as per the max-pool-size without a restart of the servers.

Description

In EAP domain mode, when changing the max-pool-size attribute of a datasource via CLI, the response does not indicate that a reload is required. However, reading the statistics of that datasource does not reflect the Available count as per the new max pool value until a restart of the server is performed.