Details
-
Suggestion
-
Resolution: Won't Do
-
None
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Chatty behavior appears when reading VCS logs:
2013-02-01 14:14:08,862 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Fetching log. 2013-02-01 14:14:09,389 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished fetching log. 2013-02-01 14:14:09,389 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Parsing log. 2013-02-01 14:14:09,392 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished parsing log. 2013-02-01 14:14:09,395 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Fetching log. 2013-02-01 14:14:10,036 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished fetching log. 2013-02-01 14:14:10,037 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Parsing log. 2013-02-01 14:14:10,079 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished parsing log. 2013-02-01 14:14:10,085 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Fetching log. 2013-02-01 14:14:10,434 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished fetching log. 2013-02-01 14:14:10,434 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Parsing log. 2013-02-01 14:14:10,442 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished parsing log. 2013-02-01 14:14:10,445 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Fetching log. 2013-02-01 14:14:10,760 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished fetching log. 2013-02-01 14:14:10,760 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Parsing log. 2013-02-01 14:14:10,762 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished parsing log. 2013-02-01 14:14:10,765 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Fetching log. 2013-02-01 14:14:11,077 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Finished fetching log. 2013-02-01 14:14:11,077 QuartzWorker-1 INFO ServiceRunner VCS Update Service [jira.vcs.cvsimpl.CvsRepositoryUtilImpl] Parsing log.
Apart from that, the logging messages in the VCS Update Service are obviously useless. It would be great to get the option to hide all Info messages in a comfortable way.
Workaround
Add this line to the log4j.properties, to increase the logging threshold for this class to WARN (that means anything at WARN, ERROR or FATAL for jira.vcs.cvsimpl.CvsRepositoryUtilImpl will be logged, but INFO will not):
log4j.logger.com.atlassian.jira.vcs.cvsimpl.CvsRepositoryUtilImpl=WARN
Attachments
Issue Links
- relates to
-
- Closed