Steps to Reproduce:
1.# enable statistics to be able to observe behavior
/profile=default/subsystem=datasources/data-source=ExampleDS:write-attribute(name=statistics-enabled, value=true)
2. #Print initial statistics
/host=master/server=server-one/subsystem=datasources/data-source=ExampleDS/statistics=pool:read-attribute(name=AvailableCount)
{
"outcome" => "success",
"result" => "9"
}
3. #Change the max-pool-size :
[domain@localhost:9999 /] /profile=default/subsystem=datasources/data-source=ExampleDS:write-attribute(name=max-pool-size,value=10)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"response" => {"outcome" => "success"}},
"server-two" => {"response" => {"outcome" => "success"}}
}}}}
}
4. #check the above change to be reflected in the AvailableCount
[domain@localhost:9999 /] /host=master/server=server-one/subsystem=datasources/data-source=ExampleDS/statistics=pool:read-attribute(name=AvailableCount)
{
"outcome" => "success",
"result" => "9"
}
5.#Restart the servers :
[domain@localhost:9999 /] /server-group=main-server-group:restart-servers()
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.