This problem will also happen under Word and other apps on Windows, I suspect, where a special Read-Lock is obtained (by that app).
I have noted (yet not proven in a test that) - try catch around a from("file://...") does not catch the exception (as the file poller never starts :-/ ) - onException before the file:// poller does not catch it either (as it happens I assume, before any message is created). - this may be replicable if the file were listable in UNIX in a dir (drwx), but not readable (--wx) for eg. I have wanted to create a test case for each of these and then deal with it but time and christmas :-) .. r On Fri, Dec 19, 2008 at 20:30, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Thu, Dec 18, 2008 at 9:41 PM, watcher <patr...@daly.ws> wrote: > > > > Yeah, I tried opening a txt file with wordpad and notepad and had no > > problems. > > > > Associating a txt file with Excel will cause a problem. > For what is worth it, we have a new strategy in Camel 2.0 to use > rename instead of FileLock so that might work for this strange issue > with Excel. > > > > > > > > > > > > > Thanks Claus. Enjoy the xmas break and have a happy new year. > You too. > > > > > -- > > View this message in context: > http://www.nabble.com/FileComponent-FileNotFoundException-tp21054406s22882p21080535.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > > > > > -- > > /Claus Ibsen > Apache Camel Committer > Blog: http://davsclaus.blogspot.com/ >