[jira] Commented: (CAMEL-444) FTPConsumer - WARN connection closed without indication

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42024#action_42024 ] 

Claus Ibsen commented on CAMEL-444:
-----------------------------------

Hmmm the FTP Component doesn't have nice house keeping when its stopping. The WARN above is logged when the consumer is stopped such as stopping Camel or a unit test.

> FTPConsumer - WARN connection closed without indication
> -------------------------------------------------------
>
>                 Key: CAMEL-444
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-444
>             Project: Apache Camel
>          Issue Type: Sub-task
>          Components: camel-ftp
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> The FTPConsumer seems in the unit tests not to properly close.
> We get these WARN in the logs
> {code}
> [ Thread: 1 RemoteFileComponent] ScheduledPollConsumer          WARN  Caught: org.apache.commons.net.ftp.FTPConnectionClosedException: Connection closed without indication.
> org.apache.commons.net.ftp.FTPConnectionClosedException: Connection closed without indication.
>         at org.apache.commons.net.ftp.FTP.__getReply(FTP.java:267)
>         at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:460)
>         at org.apache.commons.net.ftp.FTP.sendCommand(FTP.java:520)
>         at org.apache.commons.net.ftp.FTP.cwd(FTP.java:745)
>         at org.apache.commons.net.ftp.FTPClient.changeWorkingDirectory(FTPClient.java:725)
>         at org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:101)
>         at org.apache.camel.component.file.remote.FtpConsumer.poll(FtpConsumer.java:77)
>         at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:63)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
>         at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)
> {code}

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