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

Henrik Filtenborg Sørensen commented on CAMEL-2900:
---------------------------------------------------

I have also stumbled into this problem recently. We were using camel 2.9.0 and 
having a FTP-consumer with disconnect=false which suddenly (and silently) 
stopped consuming. This has only happened to us once.

Our log files did *not* contain messages about the FTP-consumer reconnecting to 
the server and JMX reported no errors.

We decided to try to fix the problem by using disconnect=true and upgrade to 
latest version of camel. Time will tell if the solution solves the problem ;-)
                
> if an ftp consumer gives up reconnecting, the consumer is still listed as 
> "started" it should say "stopped retrying" or similar
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2900
>                 URL: https://issues.apache.org/jira/browse/CAMEL-2900
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-ftp
>    Affects Versions: 2.3.0
>            Reporter: Karl Palsson
>            Assignee: Hadrian Zbarcea
>            Priority: Minor
>             Fix For: 2.5.0
>
>
> when an ftp consumer gives up retrying connections, (because the default is 
> 3) the consumer status (read via JMX) is still listed as "Started"  It would 
> be nice, and certainly have helped debugging why things weren't working, if 
> this said something like "Stopped-Retries Exceeded" or something.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to