[
https://issues.apache.org/jira/browse/CAMEL-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riccardo Sirchia updated CAMEL-5828:
------------------------------------
Attachment: fixDisruptorUnitOfWorkTest.patch
This patch fixes the problem that was detected in the DisruptorUnitOfWorkTest.
The problem was that final processing and synchronisation (which should be
considered part of the processing of that exchange) in the DisruptorConsumer
was done after the unit of work was considered done.
The final processing was previously done on the AsyncCallback, which is called
after the CamelInternalProcessorTasks in
CamelInternalProcessor.InternalCallback#done.
To solve the issue, the final processing is instead registered as a
Synchronization on the exchange, so
org.apache.camel.impl.DefaultUnitOfWork#done processes it before the UOW is
processed as done.
Let me know if there's anything else that should be improved and Claus: good
too see that this component can be included in 2.12.0!
> Offer LMAX Disruptor pattern as an endpoint in CAMEL
> ----------------------------------------------------
>
> Key: CAMEL-5828
> URL: https://issues.apache.org/jira/browse/CAMEL-5828
> Project: Camel
> Issue Type: New Feature
> Reporter: Eric
> Assignee: Willem Jiang
> Fix For: 2.12.0
>
> Attachments: came-disruptor.incremental.patch, camel-disruptor.patch,
> fixDisruptorUnitOfWorkTest.patch, README.md
>
>
> My system is an hybrid of CAMEL and LMAX Disruptor, where threads consuming
> from LMAX ringbuffer are feeding a "pool" of SEDA queues in a round-robin
> fashion. This system operates at very high-speed such as consumers from the
> SEDA queues and their producers are constantly blocking on the queues.
> Having a non-blocking, high-performance endpoint like LMAX Disruptor would be
> a great addition to CAMEL.
> LMAX Disruptor website: http://lmax-exchange.github.com/disruptor/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
