[
https://issues.apache.org/jira/browse/CAMEL-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664195#comment-13664195
]
Willem Jiang commented on CAMEL-5828:
-------------------------------------
Hi Riccardo
I think Markdown is OK, if you don't have the right the update the wiki page, I
can do that for you.
I found DisruptorUnitOfWorkTest failed sometimes, so I dug the code for a
while. I just found camel-distruptor consumer doesn't copy the handovers of
from the exchange as the seda consumer does. So when the Notify is matched, the
onCompletion method could not be called yet.
Here are the code of DisruptorConsumer
{code}
private Exchange prepareExchange(final Exchange exchange) {
// send a new copied exchange with new camel context
// don't copy handovers as they are handled by the Disruptor Event
Handlers
final Exchange newExchange = ExchangeHelper
.copyExchangeAndSetCamelContext(exchange,
endpoint.getCamelContext(), false);
// set the from endpoint
newExchange.setFromEndpoint(endpoint);
return newExchange;
}
{code}
Can you give me more explanations about the code?
> 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: Future
>
> Attachments: camel-disruptor.patch
>
>
> 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