[jboss-jira] [JBoss JIRA] (WFLY-8767) Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output

RH Bugzilla Integration (JIRA) issues at jboss.org
Fri Apr 13 12:54:00 EDT 2018


    [ https://issues.jboss.org/browse/WFLY-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561097#comment-13561097 ] 

RH Bugzilla Integration commented on WFLY-8767:
-----------------------------------------------

Aurel Pintea <apintea at redhat.com> changed the Status of [bug 1405954|https://bugzilla.redhat.com/show_bug.cgi?id=1405954] from MODIFIED to ON_QA

> 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: varsha Kamble
>              Labels: downstream_dependency
>             Fix For: 12.0.0.Beta1, 12.0.0.Final
>
>   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.5.0#75005)


More information about the jboss-jira mailing list