Hi guys, I have specific requirements. Incoming request should be split into same another requests and sent to different sources paralelly. The sources (legacy and new) are almost compatible with each other but legacy responds much slower than new. To prevent degradation of the whole service incoming request will have timeout attribute set dynamically to the required value. So when legacy system do not respond in time the service should ignore response from it and return information about timeout. I wonder which EIP components can be used for such service? I created following route with using splitter and aggregator because aggregator has completionTimeout with dynamic argument:
Unfortunately results are not as I expected.Please see below excerpt from console logs. Responses from sources are aggregated correctly but result stay inside Exchange in thread #3 and it is not returned to the caller main thread. Could you advice what could be wrong with my route? I'm not so sure about places where I put end() elements? Anyway I saw in documentation that the only way to return result from splitter to the main thread is to use its aggregation strategy but maybe there is some workaround for this? I'm using Camel 2.8.0-fuse-01-13. Thanks. Alek -- View this message in context: http://camel.465427.n5.nabble.com/Splitter-aggregator-dynamic-timeout-tp5717166.html Sent from the Camel - Users mailing list archive at Nabble.com.
