-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 12.1.2
-
Component/s: JIRA integration
-
None
-
1
-
Severity 3 - Minor
-
1
Issue Summary
Intermittently, because of the startup loading order of plugins, the java.lang.NullPointerException is observed getting for Jirareleases.
When the trigger reason object is reconstructed without going through proper Spring dependency injection (e.g., deserialised from cache), i18nResolver remains null
Steps to Reproduce
N/A
Expected Results
Should return proper I18nResolver field in JIRAReleaseTriggerReason
Actual Results
The below exception is thrown in the atlassian-bamboo.log file:
ERROR Error executing FreeMarker template
freemarker.core._TemplateModelException: Java method
"com.atlassian.bamboo.plugins.jira.release.JIRAReleaseTriggerReason.getTriggerReason()"
threw an exception
Failed at: ${triggerReason.getTriggerReason()}
[in template "com/atlassian/bamboo/plugins/jira/release/jiraReleaseTriggerReasonText-short.ftl" at line 2]
Caused by: java.lang.NullPointerException: Cannot invoke
"com.atlassian.sal.api.message.I18nResolver.getText(String, java.io.Serializable[])"
because "this.i18nResolver" is null
at com.atlassian.bamboo.plugins.jira.release.JIRAReleaseTriggerReason.getTriggerReason(JIRAReleaseTriggerReason.java:77)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available