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

[GSS](7.0.z) JBJCA-1355 - set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.9.CR1, 7.0.9.GA
    • 7.0.8.GA
    • JCA
    • None
    • EAP 7.0.9

    Description

      set-tx-query-timeout setting does not work when the remaining transaction timeout is shorter than one second (between 0-999 millis) due to incorrect round-up in IronJacamar WrapperDataSource#getTimeLeftBeforeTransactionTimeout().

      See JBJCA-1355 for details.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13300 [GSS](7.1.z) set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second

          • 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.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12854 [GSS](7.0.z) Upgrade IronJacamar from 1.3.7 to 1.3.8

          • 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.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBJCA-1355 set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second

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

          Web Link KCS 3201332

          Activity

            People

              smaestri@redhat.com Stefano Maestri
              rhn-support-mmiura Masafumi Miura
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: