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

JBossWorkManager converts from seconds to milliseconds

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 4.2.3.SP6, 4.2.3.CP01
    • 4.2.3.SP5
    • JTA
    • None

    Description

      Transaction timeouts on the work manager were assumed to be in seconds. JBossWorkManager is converting them to milliseconds before we get the timeout. We then convert them to milliseconds (under the assumption they were defined in seconds).

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-725 JCA WorkManager transaction timeouts incorrectly handled.

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-726 CLONE -JCA WorkManager transaction timeouts incorrectly handled.

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

          Bug - A problem that impairs or prevents the functions of the product. JBAS-4002 JBossWorkManager treats ExecutionContext transaction timeout as milliseconds when it should be seconds are per the API

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

          Bug - A problem that impairs or prevents the functions of the product. JBTM-351 fix JBossWorkManager timeout

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBTM-275 Make sure TransactionReaper doesn't wrap checkPeriod

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              rhn-engineering-jhallida Jonathan Halliday
              nmcl2001 Mark Little
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: