Hi! What about processing in a serial fashion by sending both messages to a seda queue first and from here to your sftp endpoint? Just to avoid any concurrency issues and I am aware this not exactly an answer for your question but maybe a workaround.
Jens Von meinem iPhone gesendet > Am 24.12.2014 um 01:22 schrieb eswar <easwaramoor...@gmail.com>: > > Hi - I do not get this exception all the time. but happens occasionally. > > Two routes are using the same sftp endpoint to send files to same server. > > when both the routes are processing concurrently, the first route is > connected and transmitting the file, this first thread is pushed out and the > second route had started to transmit the files through the second route. > First thread came back in to transmit the file, but i got the below DEBUG > log that there is an exception. Though this is not logged as ERROR and this > resulted in continuing the route rather than stopping at this point. > > DEBUG RemoteFileProducer: Exception occurred during stopping: Cannot change > directory to: / > > is there any way in the camel route to explicitly mention to run the > endpoint to its completion before it gets pushed back for other threads? > > any suggestions on this would be really helpful. thank you. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/sftp-Exception-during-concurent-execution-of-sftp-endpoint-tp5761049.html > Sent from the Camel - Users mailing list archive at Nabble.com.
