Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Data Center 7.4.0 create issue NullPointerException

yanshuai@meituan.com April 13, 2018

hi, all, when I use jira Data Center 7.4.0 for a long time, I got the exception:

errorId=3f59fe3a-572f-4261-aa85-2c3c0f0b00aa, interpretedMsg=, cause=java.lang.NullPointerException: config, stacktrace=java.lang.NullPointerException: config
at java.util.Objects.requireNonNull(Objects.java:228) [?:1.8.0_45]
at com.atlassian.jira.issue.fields.option.CachedOptionSetManager.getOptionsForConfig(CachedOptionSetManager.java:42) [classes/:?]
at com.atlassian.jira.issue.fields.config.manager.IssueTypeSchemeManagerImpl.getIssueTypesForConfigScheme(IssueTypeSchemeManagerImpl.java:272) [classes/:?]
at com.atlassian.jira.issue.fields.config.manager.IssueTypeSchemeManagerImpl.getSubTaskIssueTypesForProject(IssueTypeSchemeManagerImpl.java:265) [classes/:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) [?:1.8.0_45]
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) [atlassian-plugins-core-4.5.0.jar:?]
at com.sun.proxy.$Proxy471.getSubTaskIssueTypesForProject(Unknown Source) [?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) [?:1.8.0_45]
at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:136) [?:?]
at com.sun.proxy.$Proxy471.getSubTaskIssueTypesForProject(Unknown Source) [?:?]
at com.atlassian.jira.quickedit.action.QuickCreateIssue.setSelectedIssueTypeId(QuickCreateIssue.java:510) [?:?]
at com.atlassian.jira.quickedit.action.QuickCreateIssue.doDefault(QuickCreateIssue.java:195) [?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_45]

 

 

it sames that the db data has something wrong, can anybody help me to resolve the issue?

3 answers

0 votes
Ting
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 8, 2020
0 votes
yanshuai@meituan.com April 15, 2018

I have solved it. I found the problem project has the feature that it's assocaited with one issue types that has no relative issue type any more.

So My recover steps are as follows:

1. create a new issue types, which contains all the issue type of problem project

2. stop jira

3. execute sql: update configurationcontext SET fieldconfigscheme=<step 1 create issue types id> WHERE PROJECT=<problem project id> AND customfield = 'issuetype'

4. start jira

5. delete old issue types 

0 votes
Edwin Kyalangalilwa
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 14, 2018
yanshuai@meituan.com April 15, 2018

Thanks for your apply, but it's not the answer

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events