Jira Toolkit: Null Pointer Exception creating an issue (after upgrading jira from 4.4.4 to 5.0.4)

Mihai Ibanescu1

Creating an issue fails with the following backtrace in the logs (abridged).

Disabling the Support Tool Bar module will get rid of that error.

Is this a known problem?

May 23, 2012 1:00:05 AM org.apache.catalina.core.StandardWrapperValve invoke

SEVERE: Servlet.service() for servlet action threw exception

java.lang.NullPointerException

        at com.atlassian.jira.workflow.OSWorkflowManager.isEditable(OSWorkflowManager.java:1073)

        at com.atlassian.jira.issue.managers.DefaultIssueManager.isEditable(DefaultIssueManager.java:439)

        at sun.reflect.GeneratedMethodAccessor370.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181)

        at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(MultiTenantComponentFactoryImpl.java:211)

        at $Proxy78.isEditable(Unknown Source)

        at sun.reflect.GeneratedMethodAccessor370.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)

        at $Proxy78.isEditable(Unknown Source)

        at sun.reflect.GeneratedMethodAccessor370.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154)

        at $Proxy78.isEditable(Unknown Source)

        at com.atlassian.jira.toolkit.customfield.NullCFType.getVelocityParameters(NullCFType.java:51)

        at com.atlassian.jira.issue.customfields.CustomFieldUtils.buildParams(CustomFieldUtils.java:429)

        at com.atlassian.jira.plugin.customfield.CustomFieldTypeModuleDescriptorImpl.getEditHtml(CustomFieldTypeModuleDescriptorImpl.java:84)

        at com.atlassian.jira.issue.fields.CustomFieldImpl.getEditHtml(CustomFieldImpl.java:937)

        at com.atlassian.jira.issue.fields.CustomFieldImpl.getCreateHtml(CustomFieldImpl.java:923)

        at com.atlassian.jira.issue.fields.screen.AbstractFieldScreenLayoutItem.getCreateHtml(AbstractFieldScreenLayoutItem.java:90)

        at com.atlassian.jira.issue.fields.screen.FieldScreenRenderLayoutItemImpl.getCreateHtml(FieldScreenRenderLayoutItemImpl.java:50)

        at com.atlassian.jira.issue.fields.rest.FieldHtmlFactoryImpl.getCreateFields(FieldHtmlFactoryImpl.java:96)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181)

        at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(MultiTenantComponentFactoryImpl.java:211)

        at $Proxy254.getCreateFields(Unknown Source)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Faisal

Hi Mihai,

Judging from the exceptions, it looks like the problem arise due to JIRA Toolkit plugin:

• com.atlassian.jira.toolkit.customfield.NullCFType.getVelocityParameters(NullCFType.java:51)

Upon further investigation on the exceptions, I found that there's a bug report created to address the issue:
https://jira.atlassian.com/browse/JRA-19556

From the bug report, it seems that there's a possible workaround for this problem, which is by removing the supporttools field. Hence, can you kindly check the list of custom fields via Administration > Custom Fields, and see if there's any field of type supporttools? And if there's any, you may try to remove it and let's see if it helps.

Cheers,

Ahmad