[jboss-jira] [JBoss JIRA] (WFLY-6013) Admin Console: cannot update min and max pool sizes for XA data source

Chen Maoqian (JIRA) issues at jboss.org
Fri Apr 8 03:39:00 EDT 2016


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

Chen Maoqian edited comment on WFLY-6013 at 4/8/16 3:38 AM:
------------------------------------------------------------

Hello,i just want to reproduce the error from what your description,but it can not be reproduced  in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.


was (Author: bayern39):
Hello,i just want to reproduce the erro from what your description,but it can not be reproduced  in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.

> Admin Console: cannot update min and max pool sizes for XA data source
> ----------------------------------------------------------------------
>
>                 Key: WFLY-6013
>                 URL: https://issues.jboss.org/browse/WFLY-6013
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 9.0.2.Final
>            Reporter: The Alchemist
>            Assignee: Chen Maoqian
>            Priority: Minor
>
> h2. How to Reproduce
> # Start Wildfly
> # Create a XA data source  and set min pool size to 1, max pool size to 5
> # Refresh your web browser
> # Go to the data source you created, and update the min to 10, and max to 50.  You'll get this error:
> {code}
> Unexpected HTTP response: 500
> Request
> {
>     "operation" => "composite",
>     "address" => [],
>     "steps" => [
>         {
>             "address" => [
>                 ("subsystem" => "datasources"),
>                 ("xa-data-source" => "java:jboss/datasources/myAuth")
>             ],
>             "operation" => "write-attribute",
>             "name" => "min-pool-size",
>             "value" => 10
>         },
>         {
>             "address" => [
>                 ("subsystem" => "datasources"),
>                 ("xa-data-source" => "java:jboss/datasources/myAuth")
>             ],
>             "operation" => "write-attribute",
>             "name" => "initial-pool-size",
>             "value" => undefined
>         },
>         {
>             "address" => [
>                 ("subsystem" => "datasources"),
>                 ("xa-data-source" => "java:jboss/datasources/myAuth")
>             ],
>             "operation" => "write-attribute",
>             "name" => "max-pool-size",
>             "value" => 50
>         }
>     ]
> }
> Response
> Internal Server Error
> {
>     "outcome" => "failed",
>     "result" => {
>         "step-1" => {
>             "outcome" => "failed",
>             "rolled-back" => true
>         },
>         "step-2" => {
>             "outcome" => "failed",
>             "failure-description" => "WFLYJCA0045: failed to set attribute: null",
>             "rolled-back" => true
>         },
>         "step-3" => {
>             "outcome" => "failed",
>             "rolled-back" => true
>         }
>     },
>     "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYJCA0045: failed to set attribute: null"}},
>     "rolled-back" => true
> }
> {code}
> Looks like the web console is trying to write the {{initialPoolSize}} attribute too, even though I haven't touched it.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list