Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4002

JBossWorkManager treats ExecutionContext transaction timeout as milliseconds when it should be seconds are per the API

    XMLWordPrintable

Details

    • Hide

      A temporary work around is to pass the appropriate value in milliseconds (ie 60 seconds == 60000). However, this should really be fixed to reflect the correct intent of the API.

      Show
      A temporary work around is to pass the appropriate value in milliseconds (ie 60 seconds == 60000). However, this should really be fixed to reflect the correct intent of the API.

    Description

      As per the document for ExecutionContext found here

      http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/work/ExecutionContext.html

      the transaction timeout is in seconds. The JBossWorkManager incorrectly treats this as milliseconds.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-274 JBossWorkManager converts from seconds to milliseconds

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

          Activity

            People

              weston.price Weston M. Price (Inactive)
              weston.price Weston M. Price (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: