Bug 1405954
| Summary: | [GSS](6.4.z) Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Harshada <harshada> |
| Component: | JCA | Assignee: | varsha <vkamble> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Slavicek <pslavice> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.9 | CC: | bmaxwell, bparry, brian.stansberry, fgavrilo, jboss-set, jondruse, jpederse, rstancel, vkamble |
| Target Milestone: | CR1 | Keywords: | Reopened |
| Target Release: | EAP 6.4.20 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-19 12:40:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1510090 | ||
This issue has been fixed in previous releases. It is working correctly in EAP 6.4.13 Closed the PR https://github.com/jbossas/jboss-eap/pull/2985. As discussed with Varsha Kamble, she will take care of. core team requested changes on upstream PR Regression tests passed Verified with EAP 6.4.20.CP.CR1 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |
Description of problem: 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. Version-Release number of selected component (if applicable): EAP 6.4.x How reproducible: Each time 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. Additional info: