You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/04/08 09:06:12 UTC
[jira] [Commented] (CAMEL-8603) camel-ftp - Reduce connection info
logging from INFO to DEBUG
[ https://issues.apache.org/jira/browse/CAMEL-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484861#comment-14484861 ]
ASF GitHub Bot commented on CAMEL-8603:
---------------------------------------
GitHub user oscerd opened a pull request:
https://github.com/apache/camel/pull/468
CAMEL-8603 Camel-ftp Reduce connection info logging from INFO to DEBUG
Hi,
This PR is related to:
https://issues.apache.org/jira/browse/CAMEL-8603
Thanks,
Bye.
Andrea
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/oscerd/camel camel-8603-reduce-logging-level
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/468.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #468
----
commit cebc80fd434d2a21ef469fdecea160c97623149a
Author: ancosen <an...@gmail.com>
Date: 2015-04-08T07:03:48Z
Camel-8603 Camel-ftp Reduce connection info logging from INFO to DEBUG
----
> camel-ftp - Reduce connection info logging from INFO to DEBUG
> -------------------------------------------------------------
>
> Key: CAMEL-8603
> URL: https://issues.apache.org/jira/browse/CAMEL-8603
> Project: Camel
> Issue Type: Improvement
> Components: camel-ftp
> Reporter: Claus Ibsen
> Priority: Trivial
> Fix For: 2.15.2, 2.16.0
>
>
> See SO
> http://stackoverflow.com/questions/29496850/reduce-camel-ftp-component-logging
> We should change the 2 places in camel-ftp where we log at INFO level to DEBUG level so we dont noise the production logs.
> Its in both the consumer and producer, such as
> log.info("Connected and logged in to: " + remoteServer());
> Contributions for a patch / PR is much welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)