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

Details

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

    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

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14758 [GSS](7.1.z) JBJCA-1377 - Cached-connection-manager DEBUG connection closure could be too eager with enlistment-trace==false

          • 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.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBJCA-1377 use enlistmentTrace instead of disableEnlistment parameter to avoid eager IJ000100

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-10415 Upgrade to ironjacamar 1.4.10 Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: