Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: SF-341
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Willem Jiang
Reporter: Willem Jiang
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
FUSE Services Framework

Using Timers in JMSContinuation is suboptimal

Created: 28/Mar/11 03:16 AM   Updated: 03/Jun/11 04:19 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.2.12-fuse-00-00, 2.3.4-fuse-00-xx

External Issue URL: https://issues.apache.org/jira/browse/CXF-3567


 Description  « Hide
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.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Dave Stanley added a comment - 01/Apr/11 02:27 PM
BQ:Medium

Willem Jiang added a comment - 03/Jun/11 03:44 AM
Merged the patch into 2.3.x-fuse, 2.2.x-fuse, and trunk.

Willem Jiang added a comment - 03/Jun/11 04:19 AM
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.