Hi Claus,
Thanks for pointing me in the proper direction.
In most cases I want the http server to remain multithreaded, but in this
specific case I really need the messages in order so out of your ideas I
figured the most appropriate would be to limit the individual route using
the threads dsl.
I changed my route to:
<route>
<from uri="httpserver:myserver?someoptions"/>
<threads poolSize="1" maxPoolSize="1">
<log message="message ${body}"/>
</threads>
</route>
But I will still occasionally log messages out of order (generally happens
if one is much larger than a following one, eg 358kb message followed by a
0.5kb message, the 0.5kb message is logged first sometimes). They're all
still logged in the proper order inside the http component, just like
before, but once I call processor.process on my newly created exchange I
lose the order.
Did I miss the spirit of your post or am I using the threads dsl improperly?
--
View this message in context:
http://camel.465427.n5.nabble.com/custom-component-synchronous-processing-tp5652471p5660809.html
Sent from the Camel - Users mailing list archive at Nabble.com.
