Uploaded image for project: 'IronJacamar'
  1. IronJacamar
  2. JBJCA-1423

Pool prefill setting silently ignored for multi-user pool configurations

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • None
    • 1.4.10
    • Core
    • None
      • When prefill is used in combination with allow-multiple-users in the pool configuration then this configuration silently ignored Pool prefill setting and do not initialize the min-pool size.
    • User Experience
    • Undefined

    Description

      When using the pool or XA-pool configuration below, the prefill thread does not run.

                              <initial-pool-size>3</initial-pool-size>
                        <min-pool-size>4</min-pool-size>
                        <max-pool-size>5</max-pool-size>
                        <prefill>true</prefill>
                        <allow-multiple-users>true</allow-multiple-users>

      This may be because it doesn't make sense to try to pre-fill a multi-user pool when the user(s) will be unknown until DataSource.getConnection(user, password) is executed.

      There is no warning or error logged (prefill is simply ignored).

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21832 [GSS](7.4.z) JBJCA-1423 - Pool prefill setting silently ignored for multi-user pool configurations

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21563 [GSS](7.3.z) JBJCA-1423 - Pool prefill setting silently ignored for multi-user pool configurations

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              chikumar@redhat.com Chintu Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: