Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3439

Use Agroal for standalone narayana JDBC (and connection pooling) support

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • 5.10.6.Final
    • JTA, Transactional Driver
    • None
    • Undefined

    Description

      Narayana supports transactional applications which access databases using the JDBC APIs. When running in a Java SE environment we supply JDBC support via our own Transactional Driver [1,2]. However there are more modern frameworks that are better suited to this need which, additionally, also provide connection pooling.

      This feature enhancement is to ensure that standalone narayana users may easily integrate with at least one of these and the the library of choice should be Agroal [3].

      [1] https://narayana.io//docs/project/index.html#d0e3208
      [2] http://jbossts.blogspot.com/2017/12/narayana-jdbc-transactional-driver.html
      [3] https://agroal.github.io/docs.html

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11214 Periodic recovery does not recover XAResource after jvm crash when agroal subsystem is used

          • 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.
          • Open
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3574 (At least) io.narayana.TransactionalDriverTest::transactionDriverIndirectRecoverableRecovery2 and transactionDriverIndirectRecoverableRecovery no longer work after H2 upgrade

          • 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.
          • Pull Request Sent

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-2976 Make jdbc connection pools separate per db url

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Activity

            People

              jfinelli@redhat.com Manuel Finelli
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: