Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10414

Cached-connection-manager DEBUG connection closure could be too eager with enlistment-trace==false

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 12.0.0.Final, 13.0.0.Beta1
    • Fix Version/s: 14.0.0.Beta2
    • Component/s: JCA
    • Labels:

      Description

      There is some corner cases in which IJ isn't able to avoid IJ000100 (closing connection for you) on connection already marked as invalid and firing IJ000100 closing it, even if the connection would be closed as invalid immediately after. It doesn't create problems to the connection pool, but the redundant WARN isn't useful and could be read as connection leak.

      It happens only with enlistment-trace=false (which is default since 7.2) set for the involved datasource

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  maeste Stefano Maestri
                  Reporter:
                  maeste Stefano Maestri
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: