Turned out that the OS question is the most important one. The effect happens at Windows 2003 x64, which is our live environment. So far I was not able to reproduce it on WinXP 32 VM. Sadly, I think I have no available Win2003x64 machines I could use for java development/debugging.
To complicate things more - the live routes app is deployed as a windows service, using the 'wrapper' application as packaged by the appassembler maven plugin. As such, it actually runs the camel context in a 32-bit java VM there: Java Executable: C:\WINDOWS\system32\java.exe Windows version: 5.2.3790 Java Version : 1.6.0_11-b03 Java HotSpot(TM) Client VM Java VM Vendor : Sun Microsystems Inc. I think I'll try putting together a minimum sample which illustrates the error. Judging by the absence of any messages in the log relevant to those routes, the culprit likely happens in the FileComponent itself. As for other question: I tried restarting the camel context with different existing files in the pickup directory, and the rule is just that - if there is a matching file for a consumer on start - it hangs. If there are no matching files on start - the consumer works. I've added https://issues.apache.org/activemq/browse/CAMEL-2057 with "Minor" priority. Claus Ibsen-2 wrote: > > Hi > > It should work, at least that is the goal. > > Is it always the same consumer that does not work? > Can you try with only 2 and 1 to see if the issue is there as well? > > And can you create a ticket in JIRA about this? I will get time next > week to take a peak, but would appreciate if you had time to track > down more details where the problem may lie. > BTW Which OS do you use? > > > On Thu, Oct 8, 2009 at 9:41 PM, Vladimir Okhotnikov > <[email protected]> wrote: >> >> Sorry, >> >> Camel 2.0 release >> 3 routes like: >> file:///home/javadev/workspace/camelroutes/testdir/testdata/testimport?delete=true&include=%5E.%2Bmapping_warnings%5C.txt%24&readLock=rename >> >> the only difference between all 3 is the include pattern. >> >> >> Claus Ibsen-2 wrote: >>> >>> Hi >>> >>> Always state which version of Camel you are using. >>> And post how you route is configured. >>> >>> >>> On Thu, Oct 8, 2009 at 4:57 PM, Vladimir Okhotnikov >>> <[email protected]> wrote: >>>> >>>> Hi >>>> >>>> I'm observing quite a strange behavior at the moment. In my app, I have >>>> several routes which all start by reading files in the same directory, >>>> deleting them after processing. Obviously, each rule uses its own >>>> include >>>> pattern to process separate subset of files. >>>> >>>> Now, the problem is that if the camel context is started when there are >>>> some >>>> existing files in the directory, the matching routes do not seem to >>>> work. >>>> I >>>> cannot see any related activity in the log file (except for the first >>>> "1 >>>> file to consume message"), and the newly added files are being piled up >>>> in >>>> the directory. The other routes, which had no matching files on camel >>>> start >>>> do work. >>>> >>>> Is it a bug or am I just missing something? >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/File-component-blocked-by-existing-files-tp25803233p25803233.html >>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>> >>>> >>> >>> >>> >>> -- >>> Claus Ibsen >>> Apache Camel Committer >>> >>> Open Source Integration: http://fusesource.com >>> Blog: http://davsclaus.blogspot.com/ >>> Twitter: http://twitter.com/davsclaus >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/File-component-blocked-by-existing-files-tp25803233p25806158.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > -- View this message in context: http://www.nabble.com/File-component-blocked-by-existing-files-tp25803233p25825859.html Sent from the Camel - Users mailing list archive at Nabble.com.
