Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-664

DataSource created via console fails when test connection is done in WildFly 9

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 2.7.4
    • None
    • None
    • Hide

      try creating a MySQL DataSource from console (WildFly 9 CR1) and then test it

      Show
      try creating a MySQL DataSource from console (WildFly 9 CR1) and then test it
    • Hide

      NOTE- If we manually edit the "standalone.xml" file DataSource configuration which is generated via console andset <max-pool-size>20</max-pool-size> greater than 0
      Example:

                          <pool>
                              <min-pool-size>0</min-pool-size>
                              <initial-pool-size>0</initial-pool-size>
                              <max-pool-size>20</max-pool-size>
                              <allow-multiple-users>false</allow-multiple-users>
                          </pool>
      
      Show
      NOTE - If we manually edit the "standalone.xml" file DataSource configuration which is generated via console andset <max-pool-size>20</max-pool-size> greater than 0 Example: <pool> <min-pool-size>0</min-pool-size> <initial-pool-size>0</initial-pool-size> <max-pool-size>20</max-pool-size> <allow-multiple-users> false </allow-multiple-users> </pool>

    Description

      • When a datasource is created via Console (WildFly 9 CR1) then it always fails when test connection is done on MySQL datasource created via consle.

      Following error is thrown :

      Unexpected HTTP response: 500
      
      Request
      {
          "address" => [
              ("subsystem" => "datasources"),
              ("data-source" => "MySqlDS")
          ],
          "operation" => "test-connection-in-pool"
      }
      
      Response
      
      Internal Server Error
      {
          "outcome" => "failed",
          "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match pool. Check JndiName: java:/MySqlDS",
          "rolled-back" => true,
          "response-headers" => {"process-state" => "reload-required"}
      }
      
      • Even after reloading the whole standalone server the test always fails.

      Attachments

        Issue Links

          Activity

            People

              rhn-support-hbraun Heiko Braun
              jaysensharma Jay SenSharma (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: