Uploaded image for project: 'FUSE Services Framework'
  1. FUSE Services Framework
  2. SF-341

Using Timers in JMSContinuation is suboptimal

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      A new Timer instance is created for every new JMSContinuation. Every new Timer spawns a new thread. I feel that it should be changed and a new mechanism shared between all JMSContinuation istances should be used. For example: the JMSContinuationProvider class could hold a configurable executor service instance + a DelayQueue. This way there would be a shared pool of threads and they would no longer be created with every new JMSContinuation instance.

        Gliffy Diagrams

          Activity

          Hide
          davestanley Dave Stanley added a comment -

          BQ:Medium

          Show
          davestanley Dave Stanley added a comment - BQ:Medium
          Hide
          willem.jiang Willem Jiang added a comment -

          Merged the patch into 2.3.x-fuse, 2.2.x-fuse, and trunk.

          Show
          willem.jiang Willem Jiang added a comment - Merged the patch into 2.3.x-fuse, 2.2.x-fuse, and trunk.
          Hide
          willem.jiang Willem Jiang added a comment -

          Here we just using the WorkQueue which is provided by CXF.
          User can configure the WorkQueue through spring configuration and using JMX to monitor the states of the WorkQueue.

          Show
          willem.jiang Willem Jiang added a comment - Here we just using the WorkQueue which is provided by CXF. User can configure the WorkQueue through spring configuration and using JMX to monitor the states of the WorkQueue.

            People

            • Assignee:
              willem.jiang Willem Jiang
              Reporter:
              willem.jiang Willem Jiang
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: