[jboss-jira] [JBoss JIRA] (WFLY-8767) Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output
Lin Gao (JIRA)
issues at jboss.org
Mon May 15 07:21:00 EDT 2017
[ https://issues.jboss.org/browse/WFLY-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Gao moved JBEAP-10899 to WFLY-8767:
---------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8767 (was: JBEAP-10899)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
(was: JCA)
Affects Version/s: (was: 7.0.5.GA)
> Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output
> --------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8767
> URL: https://issues.jboss.org/browse/WFLY-8767
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Lin Gao
> Assignee: Lin Gao
> Labels: downstream_dependency
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list