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

Avoid flushing pooled connections when matchManagedConnections returns no match

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 1.4.10
    • Core
    • None

      When no match is returned by the resource adapter implementation of ManagedConnectionFactory.matchManagedConnections, the IronJacamar pool implementation terminates non-matching connections.

      There may be cases where resource adapters return null for cases where no connection matches but where the connections in the match set are not invalid though a different connection needs to be created based on the calling context (ConnectionRequestInfo).

      A mechanism to avoid the termination of non-matching connections is needed to support such cases.

              istudens@redhat.com Ivo Studensky
              rhn-support-sfikes Stephen Fikes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: