[
https://issues.apache.org/jira/browse/CAMEL-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665029#comment-13665029
]
Riccardo Sirchia commented on CAMEL-5828:
-----------------------------------------
Maybe I missed it, but I can't find what you did to trigger the problem? As
there is no sleep in that unit test, where did you put it to trigger/workaround
the problem?
Anyway, I understand what seems to be the problem. I'll also look into it.
Please let me know if you've found out anything that may help solving this
issue.
> 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: came-disruptor.incremental.patch, camel-disruptor.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