camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-3365) message order issue under load
Date Wed, 24 Nov 2010 17:23:24 GMT


Claus Ibsen commented on CAMEL-3365:

What about the client? Is it single threaded only? eg only one client sending request .. waiting
for response ... sending request ... waiting for response ... and so on.

And whats the problem really? What do mean mean is out of order? Can you give an example.

And next time please use the mailing list first for help. The issue track is not really for
that. It brings a lot of noise in the project. When its only the committers who are reading
the issue tracker. And we are not keen on people opening tickets.

> message order issue under load
> ------------------------------
>                 Key: CAMEL-3365
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.4.0
>         Environment: Eclipse 3.6 / Windows XP SP3
>            Reporter: BARRAULT Hervé
>         Attachments:
> We are using a simple route to process a one way message.
> We have modified the behavior of jetty and camel to have only one thread.
> Jetty configuration :
> <httpj:engine-factory bus="cxf">
>     	<httpj:engine port="0">
>     		<httpj:threadingParameters minThreads="1" maxThreads="2" />
>     	</httpj:engine>
> </httpj:engine-factory>
> Route configuration :
> from("cxf:bean:myEndpoint").threads(1,1).process(myprocessor);
> When processing time is higher than the time between two requests, after a while, the
emitter is blocked and the order is not kept.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message