After upgrading Jira to 9.12.x, the Automation For Jira admin page throws 500 error
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 an upgrade to 9.12 version from 9.11 version of Jira, Automation for Jira (A4J) pages such as automation rules or the global admin page do not load and throw a 500 error.
Environment
9.12.2
Diagnosis
Check the Jira application logs. If you find the error below, then this article is relevant:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2024-02-22 05:03:19,820-0600 https-jsse-nio-8443-exec-15 ERROR xxxx 303x42889x1 xxxx 13.12.13.42 /secure/AutomationProjectAdminAction!iframe.jspa [c.c.j.p.a.web.admin.AutomationProjectAdminAction] Unexpected error loading project automation UI:
java.lang.RuntimeException: com.fasterxml.jackson.databind.JsonMappingException: Null key for a Map not allowed in JSON (use a converting NullKeySerializer?) (through reference chain: com.codebarrel.automation.api.context.AutomationManagerContext["configProperties"])
at com.codebarrel.api.JsonSupport.toJsonString(JsonSupport.java:83)
at com.codebarrel.jira.plugin.automation.web.admin.AdminContextProvider.createRenderProps(AdminContextProvider.java:233)
at com.codebarrel.jira.plugin.automation.web.admin.AutomationGlobalAdminAction.getIframeViewData(AutomationGlobalAdminAction.java:58)
......
Caused by: com.fasterxml.jackson.databind.JsonMappingException: Null key for a Map not allowed in JSON (use a converting NullKeySerializer?) (through reference chain: com.codebarrel.automation.api.context.AutomationManagerContext["configProperties"])
at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:283)
at com.fasterxml.jackson.databind.SerializerProvider.mappingException(SerializerProvider.java:1358)
at com.fasterxml.jackson.databind.SerializerProvider.reportMappingProblem(SerializerProvider.java:1254)
at com.fasterxml.jackson.databind.ser.impl.FailingSerializer.serialize(FailingSerializer.java:32)
.......
at com.fasterxml.jackson.databind.ObjectMapper._writeValueAndClose(ObjectMapper.java:4568)
at com.fasterxml.jackson.databind.ObjectMapper.writeValueAsString(ObjectMapper.java:3821)
at com.codebarrel.api.JsonSupport.toJsonString(JsonSupport.java:81)
2024-02-22 05:03:19,824-0600 https-jsse-nio-8443-exec-15 ERROR xxxx 303x42889x1 xxxx 13.12.13.42 /secure/AutomationProjectAdminAction!iframe.jspa [o.a.c.c.C.[Catalina].[localhost].[/]] Unhandled exception occurred whilst decorating page
com.google.template.soy.tofu.SoyTofuException: In 'print' tag, expression "$localeString" evaluates to undefined.
at JIRA.Automation.Project.Admin.Page.iframe(automation-admin-page.soy:53)While loading the automation for Jira page, the following checks and data population are done in the database in the propertyentry and propertystring table.
The properties that have been overridden by the Jira Admin in the global configuration page such as audit log expiry, url allowlist and project permissions.
An extra property "max.issues.per.search" if it's absent
The default values for all of the properties(service limits) that haven't been overridden in the database.
The entry in the propertyentry table joined with propertystring table might look as below
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
select * from propertyentry pe left join propertystring ps on pe.id=ps.id where pe.entity_name = 'jira.properties' and pe.property_key like '%com.codebarrel%';
"ID","ENTITY_NAME","ENTITY_ID","PROPERTY_KEY","PROPERTYTYPE","ID","PROPERTYVALUE"
45623,"jira.properties",1,"com.codebarrel.addons.automation:short.scheduled.interval.issue.limit",5,45623,"1000"
45607,"jira.properties",1,"com.codebarrel.addons.automation:permissions.project.admin.allow",5,45607,"false"
45633,"jira.properties",1,"com.codebarrel.addons.automation:max.issues.per.search",5,45633,"1000"
45636,"jira.properties",1,"com.codebarrel.addons.automation:audit.log.expiry",5,45636,"{""auditExpiryDays"":42,""auditExpiryDaysOfWeek"":[6],""auditExpiryMaxDuration"":1,""auditExpiryHour"":1}"
45622,"jira.properties",1,"com.codebarrel.addons.automation:max.queued.items.per.rule",5,45622,"25000"
45626,"jira.properties",1,"com.codebarrel.addons.automation:max.rules.per.hour",5,45626,"5000"
45624,"jira.properties",1,"com.codebarrel.addons.automation:performance.rule.insights.rollup.day.job.interval",5,45624,"5"
45625,"jira.properties",1,"com.codebarrel.addons.automation:performance.rule.insights.rollup.hour.job.interval",5,45625,"5"
45627,"jira.properties",1,"com.codebarrel.addons.automation:max.processing.time.per.day",5,45627,"0"
45628,"jira.properties",1,"com.codebarrel.addons.automation:performance.rule.insights.rollup.minute.job.interval",5,45628,"1"
45629,"jira.properties",1,"com.codebarrel.addons.automation:rule.rate.per.five.second",5,45629,"2"
45630,"jira.properties",1,"com.codebarrel.addons.automation:url.allowlist.enabled",5,45630,"true"
45631,"jira.properties",1,"com.codebarrel.addons.automation:lookup.issues.result.limit",5,45631,"100"
45632,"jira.properties",1,"com.codebarrel.addons.automation:max.queued.items",5,45632,"100000"
45606,"jira.properties",1,"com.codebarrel.addons.automation:_property_keys_",5,45606,"["max.processing.time.per.day","short.scheduled.interval.issue.limit","performance.rule.insights.rollup.day.job.interval","performance.rule.insights.rollup.hour.job.interval","max.rules.per.hour","performance.rule.insights.rollup.minute.job.interval","permissions.project.admin.allow","rule.rate.per.five.second","url.allowlist.enabled","lookup.issues.result.limit","max.queued.items","max.issues.per.search","audit.log.expiry","max.queued.items.per.rule"]"Cause
In this case, one of the entry in the propertyentry table and propertystring were corrupted possibly during the upgrade. For the current problem, one of the entries in the propertyentry table were observed as below. Notice the PROPERTYTYPE value of 6 which means the entry was made in the propertytext table rather than the propertystring table which has a property type of 5, for all other entries in the above result set.
1
45606,"jira.properties",1,"com.codebarrel.addons.automation:_property_keys_",6,,""Now looking at the propertytext table, the entry for the property key was observed as below. Notice the 'null' entry for the second value.
1
45606, ["max.processing.time.per.day","null","short.scheduled.interval.issue.limit","performance.rule.insights.rollup.day.job.interval","performance.rule.insights.rollup.hour.job.interval","max.rules.per.hour","performance.rule.insights.rollup.minute.job.interval","permissions.project.admin.allow","rule.rate.per.five.second","url.allowlist.enabled","lookup.issues.result.limit","max.queued.items","max.issues.per.search","audit.log.expiry","max.queued.items.per.rule"] This would cause the config map being loaded, to report a null, when the config map, consisting of these properties, should be a not nullable vale.
Solution
Its always recommended to perform any database manipulation after shutting down all the nodes in the cluster.
For this scenario, we need to recreate the entry for the com.codebarrel.addons.automation:_property_keys_ property in the propertyentry table and also remove the null for the corresponding entry in the propertytext or propertystring table. Run the following queries to remove those wrong entries from the tables
1
2
3
4
5
delete from propertyentry where id = 45606;
delete from propertytext where id = 45606;
----In case the wrong entry is found in the propertystring table the statement should be as follows----
delete from propertystring where id = 45606;Then reload the automation for Jira project page or the global administration page for automation for Jira. The new entries would be made to the propertyentry and propertystring tables.
Was this helpful?