Issue Details (XML | Word | Printable)

Key: MULE-710
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Ross Mason
Reporter: Holger Hoffstaette
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Mule

Queues could be implemented via java.util.Queue

Created: 18/Mar/06 04:43 PM   Updated: 30/Nov/08 04:36 AM
Component/s: Core: Queues (SEDA) / Persistence
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Related
 

Labels:


 Description  « Hide
The current event queue impementation uses a LinkedList and home-grown synchronisation/timeout behaviour. Sinnce we now have 'proper' Queues via (backport)util.concurrent we should probably use those. They are likely to be a good deal faster (especially on 1.5 native) and better tested for obscure timeout/sync problems etc.

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Holger Hoffstaette added a comment - 27/Jun/06 01:29 PM
moving to 1.4.

Holger Hoffstaette added a comment - 14/Jul/06 06:48 AM
Gerhard Aschauer requested:

"
Since I have the need to prioritize requests going into Mule, I would
like to use a 'java.util.concurrent.PriorityBlockingQueue' as I don't
see any other way to satisfy the application's requirements.

So, I would like to make the following request for comment:

"Make the concrete implementation of the interface
'java.util.concurrent.BlockingQueue'
used in Mule's various thread pool executors configurable."
"


Andrew Perepelytsya added a comment - 24/Apr/07 12:42 PM
Descoping the 1.4.1, unset Fix Version for some issues.