Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
7.2.6.GA
-
None
-
Resolving.
Description
EAP 6 was able to change the Datasource pool-size without restarting EAP 6 server. We expect the same behavior on EAP 7 if possible.
Step
1. Run the EAP server by the following configuration.
<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true" statistics-enabled="true">
<connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
<driver>h2</driver>
<pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>5</max-pool-size>
<prefill>true</prefill>
</pool>
2. Execute the following CLI.
[standalone localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:write-attribute(name="min-pool-size", value=10)
[standalone localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:write-attribute(name="max-pool-size", value=10)
[standalone localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:disable{allow-resource-service-restart=true}
[standalone localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:enable
3. EAP 6.4 is..
[standalone localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/statistics=pool:read-attribute(name="AvailableCount")
{
"outcome" => "success",
"result" => 10
}
4. EAP 7.2 is..
[standalone localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/statistics=pool:read-attribute(name="AvailableCount")
{
"outcome" => "success",
"result" => 5,
"response-headers" => {"process-state" => "reload-required"}
}
Attachments
Issue Links
- relates to
-
WFLY-8767 Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output
-
- Closed
-
