FUSE Services Framework
  1. FUSE Services Framework
  2. SF-341

Using Timers in JMSContinuation is suboptimal

    Details

    • Type: Enhancement Enhancement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 8 results 

      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.

        Activity

        Hide
        Dave Stanley
        added a comment -

        BQ:Medium

        Show
        Dave Stanley
        added a comment - BQ:Medium
        Hide
        Willem Jiang
        added a comment -

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

        Show
        Willem Jiang
        added a comment - Merged the patch into 2.3.x-fuse, 2.2.x-fuse, and trunk.
        Hide
        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
        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
            Reporter:
            Willem Jiang
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: