camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Riccardo Sirchia (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5828) Offer LMAX Disruptor pattern as an endpoint in CAMEL
Date Fri, 24 May 2013 07:13:21 GMT


Riccardo Sirchia commented on CAMEL-5828:

I updated to the version of the code from the Git repo you sent me and indeed, I also get
the same problem now.
I've spent some time on it yesterday, but haven't yet figured out why this fails.

Something noteworthy is that it did not seem to fail on the state of the Apache Camel repo
on Github on 1st of May.
So something changed to camel-core in the meantime may have invalidated some assumptions of
the implementation.
> Offer LMAX Disruptor pattern as an endpoint in CAMEL
> ----------------------------------------------------
>                 Key: CAMEL-5828
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Eric
>            Assignee: Willem Jiang
>             Fix For: Future
>         Attachments: came-disruptor.incremental.patch, 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:

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:

View raw message