FieldConfigScheme Logging increased after upgrade
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After upgrading to Jira 9.11, atlassian-jira.log files are flooded with log from FieldConfigScheme
Environment
Jira Server / Data Center 9.11
Diagnosis
Several entries can be observed on atlassian-jira.log files stating that FieldConfigScheme for projectId=x and fieldId=x is missing. Example below:
1
2023-10-24 09:12:24,976-0400 http-nio-8080-exec-2308 url: /rest/message-field/1.0/config/getForContext; user: xxxx@xxxx.com WARN xxxx@xxxxx.com 552x1646575x3 1902f62 10.1.4.3 /rest/message-field/1.0/config/getForContext [c.a.j.i.f.config.manager.FieldConfigSchemeManagerImpl] FieldConfigScheme for projectId=11200 and fieldId=customfield_22209 is missing.It shouldn't cause problems or prevent the system from functioning normally, as it just means that the field has no configuration, which is expected because it's not in use.
However, these warnings could flood the logs and prevent to troubleshoot other problems in the instance.
Full Re-index might not fix this.
Solution
As a workaround the Jira admin can suppress the WARN level messages:
Go to Administration > System > under System support > click on Logging and profiling;
At the same page under "Default Loggers" section, click on Configure logging level for another package
At the "Package name" field, add the following packages and set the logging level to “ERROR”:
1com.atlassian.jira.issue.fields.config.manager.FieldConfigSchemeManagerImpl
Alternatively, this logging level will be reverted upon Jira restart, so in order to avoid the need to manually set this again after each restart, you may change on this on the log4j properties file, as below:
Make a backup of the file JIRA_INSTALL/atlassian-jira/WEB-INF/classes/log4j.properties
Edit this file and add the line below in the end of the file.
1log4j.logger.com.atlassian.jira.issue.fields.config.manager.FieldConfigSchemeManagerImpl = ERROR, console, filelogRestart Jira to take effect
This issue is tracked in our JRASERVER-76401 - Unused fields cause a lot of warning spam 5.11.1+ bug report. A fix has been released with Jira 9.12.1 and later.
Was this helpful?