Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14758

[GSS](7.1.z) JBJCA-1377 - Cached-connection-manager DEBUG connection closure could be too eager with enlistment-trace==false

    XMLWordPrintable

Details

    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.1) set for the involved datasource

      Attachments

        Issue Links

          clones

          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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-10414 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 incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-14714 [GSS](7.1.z) Upgrade Ironjacamar from 1.4.9 to 1.4.10

          • 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
          links to

          Web Link KCS

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: