[
https://issues.apache.org/activemq/browse/CAMEL-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60623#action_60623
]
Karl Palsson commented on CAMEL-2900:
-------------------------------------
I wish I could put a test case together, but I can't trigger this condition.
It's only happened a couple of times so far, and only in production, never in
test. Last time it happened, the config didn't allow me to turn debug on while
it was still running. (I've fixed that now)
I know that 2.4.x included a raft of FTP fixes, but it wasn't ready by the time
we went live. I fully expect to update to 2.4 this week or next week, and will
be keeping any eye on it. If I see it again, I will enable debug for
org.apache.camel.* and see what I see.
> 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.
