Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14433

[GSS](7.2.0) JBJCA-1370: Disable PoolConfiguration.isPrefill when initialSize is 0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 7.1.0.GA
    • JCA
    • None
    • Release Notes
    • Hide

      The configuration below (or the XA datasource equivalent) can be used to observe the issue (i.e. 5 connections will be opened, given the below, when the idle remover thread runs even if the pool is/has never been used).

                          <pool>
                        <min-pool-size>5</min-pool-size>
                        <prefill>false</prefill>
                        <use-strict-min>false</use-strict-min>
                        ...
                    </pool>
                    ...
                    <timeout>
                        <idle-timeout-minutes>1</idle-timeout-minutes>
                        ...
                    </timeout>
      Show
      The configuration below (or the XA datasource equivalent) can be used to observe the issue (i.e. 5 connections will be opened, given the below, when the idle remover thread runs even if the pool is/has never been used). <pool> <min-pool-size>5</min-pool-size> <prefill> false </prefill> <use-strict-min> false </use-strict-min> ... </pool> ... <timeout> <idle-timeout-minutes>1</idle-timeout-minutes> ... </timeout>

      When the idle remover thread runs for a datasource pool, prefill is triggered even if prefill is set to false and if the pool has never been used.

              yborgess1@redhat.com Yeray Borges Santana
              rhn-support-sfikes Stephen Fikes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: