Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10968

ManagedConnectionFactory bottleneck

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • EAP_EWP 5.3.0.ER2
    • EAP_EWP 5.2.0
    • JCA
    • None
    • Release Notes
    • Hide
      <para>A method-level synchronized block was added as part of the fix for JBPAPP-7464, however this created a concurrency bottleneck which limited connection pools to creating one connection at a time. This issue was fixed by removing the method synchronization and making it thread safe in an alternate way. As a result, more than one connection can now be created concurrently.</para>
      Show
      <para>A method-level synchronized block was added as part of the fix for JBPAPP-7464 , however this created a concurrency bottleneck which limited connection pools to creating one connection at a time. This issue was fixed by removing the method synchronization and making it thread safe in an alternate way. As a result, more than one connection can now be created concurrently.</para>
    • Documented as Resolved Issue
    • NEW

    Description

      JBPAPP-7464 was fixed by using synchronized to control access to the properties, but the synchronization is wider than it needs to be. The entire ManagedConnectionFactory.createManagedConnection() method is synchronized, when in reality only the part touching the properties needs to be. This causes a bottleneck where only one connection can be created at once, which impacts early use when the pool is filling.

      Backporting the relevant changes which are part of https://github.com/ironjacamar/ironjacamar/commit/e2db9c25fff32207c733c0945e825cd126f34ffb would remove the bottleneck.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-7464 JCA dead-lock when multiple threads execute org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.equals()

          • 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

          Activity

            People

              rhn-support-jlivings James Livingston (Inactive)
              rhn-support-jlivings James Livingston (Inactive)
              Lucas Costi Lucas Costi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: