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

          Attachments

            Activity

              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: