[
https://issues.apache.org/activemq/browse/CAMEL-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60622#action_60622
]
Hadrian Zbarcea commented on CAMEL-2900:
----------------------------------------
Hi Karl,
At every poll(), the FtpConsumer will do a prePollCheck() which leads
eventually to a connectIfNecessary(). That means that although not connected,
it is still started and will attempt to fetch files and attempt to reconnect if
necessary, which means that it is started. You are also correct that it only
tries to connect endpoint.getMaximumReconnectAttempts() times. This is
controlled by the {{int attempt}} variable which stars from 0 with every poll.
The max reconnect attempts is per poll, not for the lifetime of the consumer.
Do you have a test case for that, or do you think it would be hard to put one
together? There is a fair amount of tracing at debug level in that area, so at
the very least logging at debug level and attaching the log would help. If
there is an issue in that area we need to understand it better and fix it.
> 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/activemq/browse/CAMEL-2900
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ftp
> Affects Versions: 2.3.0
> Reporter: Karl Palsson
> Priority: Minor
> Fix For: Future
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
