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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 14.0.0.Beta2
    • 12.0.0.Final, 13.0.0.Beta1
    • JCA

      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

              smaestri@redhat.com Stefano Maestri
              smaestri@redhat.com Stefano Maestri
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: