Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently the ResequencerEngine uses a Queue for asynchronous delivery of the messages. We might want to provide a Processor instead; so we could if we prefer use synchronous dispatch.
e.g. to be able to use a single thread and JMS transaction on a single JMS session (to avoid XA etc) to do
- consume messages
- reorder
- send them on to another destination
- jms session.commit()
As far as I understand it, the current async mechanism will make transactional re-sequencing harder right?
Attachments
Attachments
Issue Links
- is superceded by
-
CAMEL-949 Support for multi-threaded, reliable resequencing.
- Resolved
1.
|
Support for a stream-processing resequencer. | Closed | Unassigned |