Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 66242 invoked from network); 26 Jan 2009 12:47:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jan 2009 12:47:29 -0000 Received: (qmail 98859 invoked by uid 500); 26 Jan 2009 12:47:29 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 98836 invoked by uid 500); 26 Jan 2009 12:47:28 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 98825 invoked by uid 500); 26 Jan 2009 12:47:28 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 98822 invoked by uid 99); 26 Jan 2009 12:47:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 04:47:28 -0800 X-ASF-Spam-Status: No, hits=-1999.1 required=10.0 tests=ALL_TRUSTED,URIBL_RHS_DOB X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 12:47:21 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3029D234C48D for ; Mon, 26 Jan 2009 04:47:00 -0800 (PST) Message-ID: <1176316550.1232974020178.JavaMail.jira@brutus> Date: Mon, 26 Jan 2009 04:47:00 -0800 (PST) From: "Claus Ibsen (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Commented: (CAMEL-1290) FTPConsumer - Error in Rename Strategy. In-Reply-To: <578629246.1232617559325.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/CAMEL-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48951#action_48951 ] Claus Ibsen commented on CAMEL-1290: ------------------------------------ @Paddy The fix should have been committed just recently. But the fix is part of a big refactor of the, underlying file transport in Camel, that the FTP now sits on top off. So please test it a bit throughly as there might have slipped a bug in the refactor. Its still an ongoing refactor, but the FTP part should be mostly done. > 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 > 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. > > 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 > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.