WireTap doesn't process the messages in the order they arrived for each message

[Christian Mueller]

The following test fails randomly fails at message 6 up to 961 (on my
machine). I consider this as an bug:

public class WireTapTest extends CamelSpringTestSupport {
    
    private int counter = 10000;

    @Test
    public void test() throws InterruptedException {
        getMockEndpoint("mock:result").expectedMessageCount(counter * 2);

        template.setDefaultEndpointUri("direct:start");
        for (int i = 0; i < counter; i++) {
            template.requestBody("Camel");
        }

        assertMockEndpointsSatisfied();
        
        List<Exchange> receivedExchanges =
getMockEndpoint("mock:result").getReceivedExchanges();
        for (int i = 0; i < receivedExchanges.size(); i++) {
            System.out.println("check exchange number " + i);

            String body =
receivedExchanges.get(i).getIn().getBody(String.class);
            if (i % 2 == 0) {
                assertEquals("REQUEST", body);
            } else {
                assertEquals("RESPONSE", body);
            }
        }
    }

    @Override
    protected AbstractApplicationContext createApplicationContext() {
        return new ClassPathXmlApplicationContext("bundle-context.xml");
    }
}

which is using the following route:
public class WireTapRouteBuilder extends RouteBuilder {

    @Override
    public void configure() throws Exception {
        from("direct:start")
            .wireTap("seda:wireTap").executorServiceRef("executorService")
            .setHeader("TYPE", constant("RESPONSE"))
            .wireTap("seda:wireTap").executorServiceRef("executorService");

        from("seda:wireTap")
            .choice()
                .when(header("TYPE").isNull())
                    .setBody(constant("REQUEST"))
                    .to("mock:result")
                .otherwise()
                    .setBody(constant("RESPONSE"))
                    .to("mock:result")
            .end();
    }
}

and the following configuration:
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xmlns:camel="http://camel.apache.org/schema/spring";
    xsi:schemaLocation="
        http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
        http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd";>

    <camel:camelContext id="com.xxx.xxxx.wireTapTest">
        <camel:routeBuilder ref="wireTapRouteBuilder" />

        <camel:threadPoolProfile id="executorService" defaultProfile="false"
poolSize="1" maxPoolSize="1" maxQueueSize="10000" rejectedPolicy="Discard"/>
    </camel:camelContext>

    <bean id="wireTapRouteBuilder"
class="com.xxx.xxxx.wiretap.WireTapRouteBuilder" />
</beans>

We use the wiretap to send messages to an endpoint which persist some key
information about the execution in a database. It's important for us to
persist the messages into the database in the same order as they arrive in
the seda endpoint. Because of this, we configured the threadPoolProfile to
only use one thread. But some times the messages receive in the reverse
order in our database/mock endpoint.

Any suggestions what is wrong here?

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/WireTap-doesn-t-process-the-messages-in-the-order-they-arrived-for-each-message-tp5731733.html
Sent from the Camel - Users mailing list archive at Nabble.com.