Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final
    • Fix Version/s: JBossAS-4.0.5.CR1
    • Component/s: JCA service
    • Labels:
      None

      Description

      Add support for prefilling jca pools where this makes sense from the configuration,
      i.e. only one pool will be used.

      The pool can be optionally prefilled under the following circumstances:

      1) If the pooling strategy is OnePool (i.e. no login module).
      2) If the pooling strategy is BySubject and the login module is ConfiguredIdentity or one
      of its subclasses.

      The easiest way to implement this would be:

      1) Add <prefill/> xml configuration to the -ds.xml:

      2) In BaseConnectionManager2.startService() invoke poolingStrategy.prefill(Subject)
      if prefilling.

      3) In the OnePool and BySubject pooling strategys implement prefill to create the InternalManagedConnectionPool(s) if they don't exist. Other strategies cannot
      prefill the pool.

      4) Add the following code to the InternalManagedConnectionPool constructor
      if (poolParams.prefill)
      PoolFiller.fillPool(this);

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                weston.price Weston M. Price
                Reporter:
                adrian.brock Adrian Brock
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: