Hi Raf, > In enterprise applications it is common to have 2 nodes running the same > application for load balancing and failover. And since camel does enterprise > integration I just assumed the file component would have this functionality > built in.
It certainly does. :) If I find some time tomorrow, I'll try to reproduce your problem. Reading lock should not behave in that way. Regarding load balancing - I only suggesting that load balancing reading from the local file system, as long as you only fan-out the messages from the file system to JMS, is often unnecessary. That happens because reading from local file system is extremely fast and because file systems are not usually used to handle so much payloads, that they can hit the bottleneck of dedicated Camel fan-out router. Regarding the failover - you can for example make your ServiceMix instance to be backed by failover instance. So if one ServiceMix is dead, then the second one will handle the file system processing and continue to fan-out messages to the JMS. I'm not telling that load balancing file system is bad or unsupported by Camel. I'm just sharing my point of view regarding clustering of this endpoint. -- Henryk Konsek http://henryk-konsek.blogspot.com
