[
https://issues.apache.org/jira/browse/CAMEL-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616703#comment-13616703
]
Riccardo Sirchia commented on CAMEL-5828:
-----------------------------------------
The repo/project is mine. Nice to see somebody else expressing interest in it!
I created it with the intention of doing exactly that, making it mature enough
for donation to ASF, but I ran into some nasty multi-threading issues when used
in high load scenarios causing some messages to be lost.
I was busy analysing if this was caused by Disruptor, Camel core or my attempt
of integrating them (most likely :)) but other activities have kept me from
making significant progress there.
I'll see if I can rekindle my efforts and of course any assistance would be
most welcome!
See my profile/github for contact info.
> 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
> Fix For: Future
>
>
> 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