On Fri, Aug 6, 2010 at 1:23 PM, Marco Crivellaro <[email protected]> wrote: > > I've tried current snapshot; the timeout is working as expected, although the > task doesn't get cancelled. > I receive messages from running thread (connection timeout to an FTP) after > the timeout is raised (many seconds afterwards). >
What do you mean precisely by receiving message? Could you detail exactly what you see? It's the responsibility of the JDK to cancel the task which it tries doing by interrupting it. But I speculate many 3rd party libraries just ignore the interrupt exception. > you can try this behaviour by seding and FTP exchange to an IP which does > not exist in your network and setting the timeout to a low value. > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-2-5-recipientList-aggregationStrategy-timeout-tp2265144p2266518.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
