camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Okhotnikov (JIRA)" <j...@apache.org>
Subject [jira] Closed: (CAMEL-2057) File consumer does not work in certain environments when there are existing matching files on its startup
Date Mon, 12 Oct 2009 10:43:53 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Okhotnikov closed CAMEL-2057.
--------------------------------------

       Resolution: Working as Designed
    Fix Version/s: 2.0.0

The behavior was caused by insufficient permissions on the "poison" files. Can be addressed
by specifying a read lock timeout instead of default infinite one. Better yet, change the
default timeout to something other than "wait forever", which is addressed by https://issues.apache.org/activemq/browse/CAMEL-2062

> File consumer does not work in certain environments when there are existing matching
files on its startup
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2057
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2057
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0.0
>         Environment: Windows 2003 x64
> Java windows service started through Java Service Wrapper from Tanuky Software, in 32
bit java VM:
> 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.
>            Reporter: Vladimir Okhotnikov
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> 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. 
> More details at http://www.nabble.com/File-component-blocked-by-existing-files-td25803233.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message