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

[GSS](8.0.z) JBJCA-1471 - Prefill pool after returned connection has been destroyed

    XMLWordPrintable

Details

    Description

      Customer is reporting a change in behaviour between EAP 7.4.0 and 7.4.10. With pool settings

       prefill (true)
- use-strict-min (true)
- initial-pool-size (5)
- min-pool-size (5)
- max-pool-size (5)

      they say that in EAP 7.4.10 the pool only gets refilled if the connection count reaches 0. Where as in EAP 7.4.0 it never goes below 5. They have their own RA that is configured via ironjacamar.xml and there is no RA configuration in JBoss EAP standalone*.xml file. So the question is would we expect such setup to behave in the same manner as if the RA was configured in standalone*.xml file.

      please take a look at the attachment in EAPSUP-1212 for the reproducer.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25148 [GSS](7.4.z) JBJCA-1471 - Prefill pool after returned connection has been destroyed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBJCA-1471 Prefill pool after returned connection has been destroyed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-25263 (8.0.z) Upgrade Ironjacamar from 3.0.2.Final-redhat-00002 to 3.0.8.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rhn-engineering-lgao Lin Gao
              pberan@redhat.com Petr Beran
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: