[
https://issues.apache.org/activemq/browse/CAMEL-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63508#action_63508
]
Claus Ibsen commented on CAMEL-3365:
------------------------------------
I really dont think this is a Camel problem.
In whatever order Jetty is serving the requests to camel CXF consumer is the
order they are processed by Camel.
Could you take this to the Jetty community please?
> message order issue under load
> ------------------------------
>
> Key: CAMEL-3365
> URL: https://issues.apache.org/activemq/browse/CAMEL-3365
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.4.0
> Environment: Eclipse 3.6 / Windows XP SP3
> Reporter: BARRAULT Hervé
>
> 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.
