Re: [HEADS UP] - File component changes in Camel 2.0
On a slightly related tangent, I'm partly responsible for the hackish code
in FileConsumer's (old) isUnchanged() method (
https://issues.apache.org/activemq/browse/CAMEL-250).
Camel 1.5's exclusiveReadLock feature is unfortunately still picking up
files too early, so I have to fall back to the deprecated behavior. This
happens regardless of the file processing strategy (delete, rename, etc.)
Is there any chance the hackish double-polling stuff can be put back in to
2.0 as a non-default file locking strategy? I can take a crack at it, I
just wasn't sure if the code was still in flux.
- aaron
On Mon, Feb 2, 2009 at 4:44 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Fri, Jan 30, 2009 at 5:40 PM, Aaron Crickenberger
aaron.crickenber...@intalgent.com wrote:
I would hesitate if only because requiring a particular header seems off,
are there other components that do the same?
I haven't looked much at Camel 2.0's code, but it looks like camel-1.x's
file component's expression property could support both scenarios. Use
a
default ${id} expression, but allow user to configure w/ a ${in.header}
expression that barks if the header's not present, no?
That is correct.
Thanks for the feedback. We will leave it as is.
- aaron
On Fri, Jan 30, 2009 at 9:49 AM, James Strachan
james.strac...@gmail.comwrote:
So long as files are written in some directory and they are unique and
preserve order - does it matter if they are generated (from the
message ID say) or the user explicitly gives some name? Like Jon I'd
be tempted ot leave the default behaviour?
2009/1/30 Claus Ibsen claus.ib...@gmail.com:
Hi
As some of you know the file component have had a major refactor ...
actually you can nearly consider it as a rewrite in Camel 2.0.
This mail is about a few remaining issues I want to give a heads up
upon and feedback:
Force a filename to be provided when wring a file
I want to force file producer always requiring a header value with the
filename to write.
What we have in Camel 1.x is that if no filename header is provided it
will fallback to use the message id as the filename.
For me that has no use, as its kinda like telling a database here is
some data store it somewhere, without providing, schema, table, column
names.
So I want it to reject writing a file and report an exception that the
filename is missing.
The file language supports you if you want to use the message id as
the filename. Just set the header value as: ${id}
And also remove option: ignoreFileNameHeader
Thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
--
James
---
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Help with camel relaying HTTP msg between .Net web client and .Net service.
Hello, we are using a .NET client to communicate over http: with a .NET web
service. We are attempting to send a message directly to Camel
(http://activemq.apache.org/camel/) from the .NET client, and then have
camel relay that message to the service. Then the service will then reply
back to Camel and Camel should send that reply message back to the client.
We wish to do all this over HTTP without adding any of these messages to a
JMS queue.
So the process would look something like this
Message sent out
{Client Machine} --Http Message out -- {Camel Machine} -- Http Message out
-- {Service Machine}
Message returned
{Client Machine} -- Http Message retuned -- {Camel Machine} -- Http
Message retuned -- {Service Machine}
Our main problem right now is how to configure the endpoints and which files
need hold the information. In other words, what HTTP endpoint address does
the client side send a message to in order to reach Camel? (How do we expose
Camel as an HTTP endpoint that is reachable by the client?) Also, how do we
then forward that message from Camel to our .NET service over HTTP? Are
there any settings in .wsdl we and web.config files which we need to pay
particular attention to? Any help on how resolve this issue would be greatly
appreciated. Please provide an example of any xml settings etc.
Thanks
Rob
--
View this message in context:
http://www.nabble.com/Help-with-camel-relaying-HTTP-msg--between-.Net-web-client-and-.Net-service.-tp21792780s22882p21792780.html
Sent from the Camel - Development mailing list archive at Nabble.com.
Re: [DISCUSS] Implement protocol related components in Camel [WAS] Re: [Proposal] New components
2009/2/2 Guillaume Nodet gno...@gmail.com: It might be doable. I guess the way to do that would be to define the JBI endpoint as a wrapper to a camel endpoint. When the JBI endpoint would be initialized / started, a camel route would be created for it. Not sure how well camel endpoints can handle the JBI lifecycle where new requests are not accepted, but existing exchanges are still processed until completion (for a consumer endpoint). Could you give an example of a well behaving JBI endpoint that does this? I wonder how hard this would be to add; either at the Camel-Endpoint-As-JBI-Endpoint wrapper or inside Camel etc -- James --- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
Re: [DISCUSS] Implement protocol related components in Camel [WAS] Re: [Proposal] New components
This should not be too complicated to implement if needed. The idea in JBI is that service assemblies (aka routes un camel) have three real states: started, stopped and shutdown. Started means that all endpoints are fully operational. Shutdown means that no exchanges will be processed. The stopped state is the interesting one: consumer endpoints will not accept any new requests from the outside world but will still process existing requests. Other provider endpoints fully process requets. The goal is to ensure an orderly shut down of assemblies and not loose any messages. For example a jms consumer will stop consuming jms messages from the queue, but will still enqueue responses when they come back from the route. If we are to support that in camel, we should do it in a way that we can easily control the lifecycle of mixed applications (if you mix servicemix endpoints and camel routes). On 02/02/2009, James Strachan james.strac...@gmail.com wrote: 2009/2/2 Guillaume Nodet gno...@gmail.com: It might be doable. I guess the way to do that would be to define the JBI endpoint as a wrapper to a camel endpoint. When the JBI endpoint would be initialized / started, a camel route would be created for it. Not sure how well camel endpoints can handle the JBI lifecycle where new requests are not accepted, but existing exchanges are still processed until completion (for a consumer endpoint). Could you give an example of a well behaving JBI endpoint that does this? I wonder how hard this would be to add; either at the Camel-Endpoint-As-JBI-Endpoint wrapper or inside Camel etc -- James --- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/ -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
[jira] Resolved: (CAMEL-1173) Need example of scatter-gather pattern
[ https://issues.apache.org/activemq/browse/CAMEL-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-1173. Resolution: Fixed Fix Version/s: 1.5.0 This can be done in Camel 1.5/2.0 Need example of scatter-gather pattern -- Key: CAMEL-1173 URL: https://issues.apache.org/activemq/browse/CAMEL-1173 Project: Apache Camel Issue Type: Task Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 2.0.0, 1.5.0 See http://www.eaipatterns.com/BroadcastAggregate.html We should be able to do this in Camel already... just need to cook up an example/doco for it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1173) Need example of scatter-gather pattern
[ https://issues.apache.org/activemq/browse/CAMEL-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49088#action_49088 ] Jonathan Anstey commented on CAMEL-1173: Put in an improved scatter-gather example in revision 740056. The problem with the first example was that it was not dynamic enough. Also added wiki docs here http://cwiki.apache.org/confluence/display/CAMEL/Scatter-Gather Need example of scatter-gather pattern -- Key: CAMEL-1173 URL: https://issues.apache.org/activemq/browse/CAMEL-1173 Project: Apache Camel Issue Type: Task Reporter: Jonathan Anstey Assignee: Jonathan Anstey Fix For: 1.5.0, 2.0.0 See http://www.eaipatterns.com/BroadcastAggregate.html We should be able to do this in Camel already... just need to cook up an example/doco for it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1307) Upgrade to FTPServer 1.0 GA
Upgrade to FTPServer 1.0 GA
---
Key: CAMEL-1307
URL: https://issues.apache.org/activemq/browse/CAMEL-1307
Project: Apache Camel
Issue Type: Task
Components: camel-ftp
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.0.0, 1.5.2
We use FTP Server from Apache Mina to unit test camel-ftp itself.
Upgrading to RC2 is complex as the API changed too much and the setPort method
is inaccessible
Created a ticket about it
https://issues.apache.org/jira/browse/FTPSERVER-271
The code below is the partiual upgrade, until hitting the setPort issue.
{code}
protected void initFtpServer() throws Exception {
ftpServerContext = new DefaultFtpServerContext();
// setup user management to read our users.properties and use clear
text passwords
File file = new
File(./src/test/resources/users.properties).getAbsoluteFile();
PropertiesUserManager uman = new PropertiesUserManager(new
ClearTextPasswordEncryptor(), file, admin);
ftpServerContext.setUserManager(uman);
ftpServer = new DefaultFtpServer(ftpServerContext);
if (port 21000) {
throw new IllegalArgumentException(Port number is not initialized
in an expected range: + getPort());
}
ftpServer.getListener(default).setPort(port);
}
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1306) Fixed the file unit test error which are introduced by CAMEL-1241 on Windows
[ https://issues.apache.org/activemq/browse/CAMEL-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-1306. - Resolution: Fixed Fixed the file unit test error which are introduced by CAMEL-1241 on Windows Key: CAMEL-1306 URL: https://issues.apache.org/activemq/browse/CAMEL-1306 Project: Apache Camel Issue Type: Task Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.0.0 There are about 10 unit tests of file are failed in Windows box with the patch of CAMEL-1241 , we need to fix them ASAP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [HEADS UP] - File component changes in Camel 2.0
Hi
Yeah please take a look at the GenericFileExclusiveReadLockStrategy
and see if you can implement it as a implementation of this interface?
Then it can be added into camel 2.0 as an other option to choose.
But beware that the code in trunk is currently have 2 file components.
FileComponent is the old one that is currently active
NewFileComponent is the new one temporary there side by side until its
rock solid and can replace the FileComponent.
The trick is that you can modify the file component file
Index: src/main/resources/META-INF/services/org/apache/camel/component/file
===
--- src/main/resources/META-INF/services/org/apache/camel/component/file
(revision 739943)
+++ src/main/resources/META-INF/services/org/apache/camel/component/file
(working copy)
@@ -15,5 +15,5 @@
# limitations under the License.
#
-class=org.apache.camel.component.file.FileComponent
-strategy.factory.class=org.apache.camel.component.file.strategy.FileProcessStrategyFactory
\ No newline at end of file
+class=org.apache.camel.component.file.NewFileComponent
+strategy.factory.class=org.apache.camel.component.file.strategy.NewFileProcessStrategyFactory
\ No newline at end of file
Where you just use the NewFileComponent and the New factory.
On Mon, Feb 2, 2009 at 3:54 PM, Aaron Crickenberger
aaron.crickenber...@intalgent.com wrote:
On a slightly related tangent, I'm partly responsible for the hackish code
in FileConsumer's (old) isUnchanged() method (
https://issues.apache.org/activemq/browse/CAMEL-250).
Camel 1.5's exclusiveReadLock feature is unfortunately still picking up
files too early, so I have to fall back to the deprecated behavior. This
happens regardless of the file processing strategy (delete, rename, etc.)
Is there any chance the hackish double-polling stuff can be put back in to
2.0 as a non-default file locking strategy? I can take a crack at it, I
just wasn't sure if the code was still in flux.
- aaron
On Mon, Feb 2, 2009 at 4:44 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Fri, Jan 30, 2009 at 5:40 PM, Aaron Crickenberger
aaron.crickenber...@intalgent.com wrote:
I would hesitate if only because requiring a particular header seems off,
are there other components that do the same?
I haven't looked much at Camel 2.0's code, but it looks like camel-1.x's
file component's expression property could support both scenarios. Use
a
default ${id} expression, but allow user to configure w/ a ${in.header}
expression that barks if the header's not present, no?
That is correct.
Thanks for the feedback. We will leave it as is.
- aaron
On Fri, Jan 30, 2009 at 9:49 AM, James Strachan
james.strac...@gmail.comwrote:
So long as files are written in some directory and they are unique and
preserve order - does it matter if they are generated (from the
message ID say) or the user explicitly gives some name? Like Jon I'd
be tempted ot leave the default behaviour?
2009/1/30 Claus Ibsen claus.ib...@gmail.com:
Hi
As some of you know the file component have had a major refactor ...
actually you can nearly consider it as a rewrite in Camel 2.0.
This mail is about a few remaining issues I want to give a heads up
upon and feedback:
Force a filename to be provided when wring a file
I want to force file producer always requiring a header value with the
filename to write.
What we have in Camel 1.x is that if no filename header is provided it
will fallback to use the message id as the filename.
For me that has no use, as its kinda like telling a database here is
some data store it somewhere, without providing, schema, table, column
names.
So I want it to reject writing a file and report an exception that the
filename is missing.
The file language supports you if you want to use the message id as
the filename. Just set the header value as: ${id}
And also remove option: ignoreFileNameHeader
Thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
--
James
---
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Re: [HEADS UP] - File component changes in Camel 2.0
On Fri, Jan 30, 2009 at 5:40 PM, Aaron Crickenberger
aaron.crickenber...@intalgent.com wrote:
I would hesitate if only because requiring a particular header seems off,
are there other components that do the same?
I haven't looked much at Camel 2.0's code, but it looks like camel-1.x's
file component's expression property could support both scenarios. Use a
default ${id} expression, but allow user to configure w/ a ${in.header}
expression that barks if the header's not present, no?
That is correct.
Thanks for the feedback. We will leave it as is.
- aaron
On Fri, Jan 30, 2009 at 9:49 AM, James Strachan
james.strac...@gmail.comwrote:
So long as files are written in some directory and they are unique and
preserve order - does it matter if they are generated (from the
message ID say) or the user explicitly gives some name? Like Jon I'd
be tempted ot leave the default behaviour?
2009/1/30 Claus Ibsen claus.ib...@gmail.com:
Hi
As some of you know the file component have had a major refactor ...
actually you can nearly consider it as a rewrite in Camel 2.0.
This mail is about a few remaining issues I want to give a heads up
upon and feedback:
Force a filename to be provided when wring a file
I want to force file producer always requiring a header value with the
filename to write.
What we have in Camel 1.x is that if no filename header is provided it
will fallback to use the message id as the filename.
For me that has no use, as its kinda like telling a database here is
some data store it somewhere, without providing, schema, table, column
names.
So I want it to reject writing a file and report an exception that the
filename is missing.
The file language supports you if you want to use the message id as
the filename. Just set the header value as: ${id}
And also remove option: ignoreFileNameHeader
Thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
--
James
---
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Re: [jira] Commented: (CAMEL-1302) Documentation - Add camel-bindy documentation
Hi Bindy is a component donated by Charles Moulliard that choosed that name. I guess its named like this sine it does annotation based POJO binding from other data formats, currently only CSV. On Fri, Jan 30, 2009 at 4:36 PM, William Tam email.w...@gmail.com wrote: BTW, I am curious about the name bindy. What does it mean? On Fri, Jan 30, 2009 at 1:28 AM, Claus Ibsen (JIRA) j...@apache.org wrote: [ https://issues.apache.org/activemq/browse/CAMEL-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49034#action_49034 ] Claus Ibsen commented on CAMEL-1302: Charles the wiki page is here you should update: http://camel.apache.org/bindy.html Documentation - Add camel-bindy documentation - Key: CAMEL-1302 URL: https://issues.apache.org/activemq/browse/CAMEL-1302 Project: Apache Camel Issue Type: Sub-task Components: camel-bindy Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
Re: [DISCUSS] Implement protocol related components in Camel [WAS] Re: [Proposal] New components
Let's include the camel folks in this discussion. On Feb 2, 2009, at 11:51 AM, Hadrian Zbarcea wrote: Hi, Another option is to implement such components in Apache Camel and provide a way to easily wrap a camel component in a jbi component. Such components are useful to users who only use Camel too, and it would be a pity to duplicate the work. Thoughts? Hadrian On Feb 1, 2009, at 2:28 AM, Jean-Baptiste Onofré wrote: Hi Chris, Thanks. I propose the following priority for BCs : - servicemix-ldap - servicemix-exec - servicemix-jdbc - servicemix-asterisk - servicemix-talend - servicemix-sap - servicemix-cics What about the servicemix-ejb, does it make sense or do we consider that CXF-SE is enough ? Regards JB On Saturday 31 January 2009 - 17:00, Chris Custine wrote: Hi JB, A while back I did some playing with asterisk-java ( http://asterisk-java.org/) in SMX4 and OSGi so I would be happy to help create a more general purpose JBI component. My code never evolved beyond sandbox quality, but I will dust it off and maybe soon we can chat about some features. Chris -- Chris Custine My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org On Fri, Jan 30, 2009 at 1:27 PM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Dear all, I'm completing the unit tests on the SMPP BC but it's now quite the end (Lars has already included on the svn repo) (it's the SM-1623). I have begun to work on the SM-1771 (extend the SU classpath/ location support). But, I would like to implement new components : - JDBC BC : read and write messages from JDBC - Talend BC : read and write messages from the Talend ETL - Asterisk BC : read and write from Asterisk VoIP software - Exec BC : read and write from command execution (using commons- exec) - LDAP BC : read and write from LDAP (using JNDI) - CICS BC : read and write messages from CICS mainframe - SAP BC : read and write messages from SAP - EJB BC : currently, I use CXF-SE to call an EJB. Maybe a component exposing directly (either if it use CXF-SE in background). What do you think about these components ? Does it make sense (for me, it's the case as I have request from customers to support in FSB/SMX legacy platform such as CICS, SAP, JDBC, etc) ? I'm ready to begin this work if you are OK. Regards JB -- Jean-Baptiste Onofré (Nanthrax) BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net j...@nanthrax.net PGP : 17D4F086 -- Jean-Baptiste Onofré (Nanthrax) BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net j...@nanthrax.net PGP : 17D4F086
[jira] Work stopped: (CAMEL-1289) HeaderFilterStrategy - move from Component to Endpoint
[ https://issues.apache.org/activemq/browse/CAMEL-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-1289 stopped by William Tam. HeaderFilterStrategy - move from Component to Endpoint -- Key: CAMEL-1289 URL: https://issues.apache.org/activemq/browse/CAMEL-1289 Project: Apache Camel Issue Type: Task Reporter: Claus Ibsen Assignee: William Tam Priority: Minor I am working on CAMEL-505 to allow 100% spring bean configuration of endpoints. When we do this we bypass the xxxComponent that can only be used with the URI configuration. Some components have the headerfilterstrategy that they pass down to the xxxEndpoint. We might wanna consider having getter/setter for headerfilterstrategy on the endpoint itself for spring bean configuration and to default set it to some value to ease the spring bean configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (CAMEL-1308) camel-cxf to support jaxrs consumer
[ https://issues.apache.org/activemq/browse/CAMEL-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-1308 started by William Tam. camel-cxf to support jaxrs consumer --- Key: CAMEL-1308 URL: https://issues.apache.org/activemq/browse/CAMEL-1308 Project: Apache Camel Issue Type: New Feature Components: camel-cxf Reporter: William Tam Assignee: William Tam Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1308) camel-cxf to support jaxrs consumer
camel-cxf to support jaxrs consumer --- Key: CAMEL-1308 URL: https://issues.apache.org/activemq/browse/CAMEL-1308 Project: Apache Camel Issue Type: New Feature Components: camel-cxf Reporter: William Tam Assignee: William Tam Fix For: 2.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1290) FTPConsumer - Error in Rename Strategy.
[ https://issues.apache.org/activemq/browse/CAMEL-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1290. Resolution: Fixed Fix Version/s: 2.0.0 FTPConsumer - Error in Rename Strategy. --- Key: CAMEL-1290 URL: https://issues.apache.org/activemq/browse/CAMEL-1290 Project: Apache Camel Issue Type: Bug Components: camel-ftp Affects Versions: 2.0.0 Environment: Windows XP Reporter: Paddy Daly Assignee: Claus Ibsen Fix For: 2.0.0 Attachments: CAMEL-1290_Fix_StringIndexOutOfBounds.diff, CAMEL-1290_TestToShowFix.diff Time Spent: 30 minutes Remaining Estimate: 0 minutes Consuming from a FTP server using the following endpoint cause a StringIndexOutOfBoundsException when using the rename strategy. endpoint id=candidateUrl uri=ftp://usern...@127.0.0.1?password=passwordamp;delete=trueamp;binary=trueamp;delay=1amp;readLock=rename/ 22 Jan 2009 09:36:59,501 ERROR [Thread: 1 org.apache.camel.component.file.remote.RemoteFileComponent @8f7aa2] FtpConsumer.log(207) | String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1938) at org.apache.camel.component.file.remote.RemoteFile.getParent(RemoteFile.java:139) at org.apache.camel.component.file.remote.RemoteFile.changeFileName(RemoteFile.java:65) at org.apache.camel.component.file.remote.strategy.RemoteFileRenameExclusiveReadLockStrategy .acquireExclusiveReadLock(RemoteFileRenameExclusiveReadLockStrategy.java:45) at org.apache.camel.component.file.remote.strategy.RemoteFileProcessStrategySupport.begin(Re moteFileProcessStrategySupport.java:32) at org.apache.camel.component.file.remote.RemoteFileConsumer.processExchange(RemoteFileConsu mer.java:131) at org.apache.camel.component.file.remote.RemoteFileConsumer.poll(RemoteFileConsumer.java:98 ) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Scheduled ThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Schedule dThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadP oolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) A workaround is to add a folder in the url like the following endpoint id=candidateUrl uri=ftp://usern...@127.0.0.1//myFolder/?password=passwordamp;delete=trueamp;binary=trueamp;delay=1amp;readLock=rename/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
