camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5828) Offer LMAX Disruptor pattern as an endpoint in CAMEL
Date Thu, 23 May 2013 07:40:20 GMT


Willem Jiang commented on CAMEL-5828:

Hi Riccardo,
Here is the stack trace of DisruptorUnitOfWorkTest if I remove the Thread.sleep code.

testDisruptorUOW(org.apache.camel.component.disruptor.DisruptorUnitOfWorkTest)  Time elapsed:
0.182 sec  <<< FAILURE!
java.lang.AssertionError: expected:<onCompleteA> but was:<null>
	at org.junit.Assert.failNotEquals(
	at org.junit.Assert.assertEquals(
	at org.junit.Assert.assertEquals(
	at org.apache.camel.component.disruptor.DisruptorUnitOfWorkTest.testDisruptorUOW(

Here is my system information
Apache Maven 3.0.4 (r1232337; 2012-01-17 16:44:56+0800)
Maven home: /usr/share/maven
Java version: 1.6.0_41, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_41-b02-445.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac"

> 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