Finally I have been able to reproduce/identify the issue. Given that we are using a relative path to move the processed files into once successfully ftp-ed to the destination servers:
../../../u/4gl_upload/warehouse_integration_2/trs-server/export/in_progress_bpo/201609081030/done However, for some reason instead of traversing the via correct path to move the processed files the camel consumer creates a new subdirectory tree starting from where it is and this could be quite long as follows. Hence the problem. It doesn’t know where it is and it doesn’t reset itself. /u/4gl_upload/warehouse_integration_2/trs-server/u/4gl_upload/warehouse_integration_2/trs-server/export/in_progress_bpo/201609081030 This was reproduced with the option stepwise=false, which means it traverses the subdirectories in a single step instead of step wise. Still don’t know what best solution is. -- View this message in context: http://camel.465427.n5.nabble.com/GenericFileOperationFailedException-Cannot-rename-file-on-Linux-tp5787225p5787338.html Sent from the Camel - Users mailing list archive at Nabble.com.
