It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? Update the Universal Plugin Manager (Add-on Manager) by file replacement. How could I solve this problem?jirajira-cloudcloudCommentCommentAdd your comment...1 answer10-1Tiago ComassetoOct 14, 2013Hi Andrew, In order to no have any problem with non-latin characters, make sure that your application is configured to at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:401) at com.atlassian.cache.memory.DelegatingCachedReference.get(DelegatingCachedReference.java:39) ... 71 more Cause: This error may be caused by the JIRA Agile plugin and is tracked in the bug below: JSW-10844 - GreenHopperLicenseStoreImpl can supply null, have a peek here
It's currently unknown at this stage what causes this. Was this helpful? Change the project workflow back to the JIRA default workflow (This will set the Null steps as TEMP statuses, allowing you to migrated to JIRA default workflow). In the entities.xml, change the value (in this example, 6007) in step 4 to the same number found in step 5.
Add a new status called "TEMP". Import the data into Test instance with JIRA 4.4.3 and GreenHopper 5.7.4 then we run into the error below : 2011-12-05 14:31:05,258 JiraImportTaskExecutionThread-1 INFO superadmin 848x1092x2 b654b 10.62.65.6 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Importing Always back up your data before performing any modification to the database. You may be able to find this known bug for the above error JIRA-26635, JIRA-27939 I don't think you need to import activeobjects.xml further into JIRA.
Why was this unhelpful? Thanks,NarenDec 20, 2012Yeah, hope so. In this example, 853.
Even I too faced the same kind of critical situation while importing the XML backup for the ActiveObjects, but with different errors. Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at com.atlassian.jira.index.FutureResult.await(FutureResult.java:31) ... Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence Log in Sign up QuestionsTopicsLeaderboardRewardsThe https://jira.atlassian.com/browse/JRA-27939 Look a little further down for other errorsCommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Printed by Atlassian Confluence 5.7.3, Team
In this example, the ID is 10047. Go to Administration >> Issue Settings >> Statuses. Report a bug Atlassian News Atlassian Atlassian Documentation Log in JIRA Knowledge Base JIRA throws NullPointerException using Imported Workflow Due to Missing Linked Status Problem After a XML restore or They will automatically get assigned to your Null-linked workflow steps.
Start JIRA. Started Today 08:18 AM. AttachmentsIssue Links is cloned from JRA-26635 "Error importing data: java.lang.NullPointerException" when importing in JIRA Resolved Activity People Assignee: Abdullahi Abduljabar [Atlassian] Reporter: faknine Votes: 0 Vote for this issue Watchers: 1 If you are an administrator, please try submitting this problem via the Support Request Page Else, please create a support issue on our support system at http://support.atlassian.com with the following information:
Users get an IllegalArgumentException when attempting to to publish the draft workflow One of the following appears in the atlassian-jira.log: 2011-02-08 14:50:26,111 http-8080-7 ERROR user 890x362x1 1qdw44h 0:0:0:0:0:0:0:1 /secure/project/SelectProjectWorkflowSchemeStep2!default.jspa [webwork.util.ValueStack] METHOD: navigate here at com.atlassian.cache.memory.DelegatingCachedReference.get(DelegatingCachedReference.java:47) at com.pyxis.greenhopper.jira.license.GreenHopperLicenseStoreImpl.retrieve(GreenHopperLicenseStoreImpl.java:35) at com.pyxis.greenhopper.jira.license.GreenHopperPluginLicenseManager.getCurrentLicense(GreenHopperPluginLicenseManager.java:102) at com.pyxis.greenhopper.jira.license.GreenHopperLicenseManagerImpl.doVerify(GreenHopperLicenseManagerImpl.java:131) at com.pyxis.greenhopper.jira.license.GreenHopperLicenseManagerImpl.verify(GreenHopperLicenseManagerImpl.java:121) at com.atlassian.greenhopper.Launcher$FullSystemInitialiser.
error log from 2012-04-23 02:47:11,851 JiraImportTaskExecutionThread-1 INFO anonymous 163x36x1 kglmiu 10.3.16.242 /secure/SetupImport.jspa [jira.bc.dataimport.DefaultDataImportService] Importing data is 89% complete... 2012-04-23 02:47:14,679 JiraImportTaskExecutionThread-1 INFO anonymous 163x36x1 kglmiu 10.3.16.242 /secure/SetupImport.jspa [jira.bc.dataimport.DefaultDataImportService] Importing data is error log from 2012-04-23 02:47:11,851 JiraImportTaskExecutionThread-1 INFO anonymous 163x36x1 kglmiu 10.3.16.242 /secure/SetupImport.jspa [jira.bc.dataimport.DefaultDataImportService] Importing data is 89% complete... 2012-04-23 02:47:14,679 JiraImportTaskExecutionThread-1 INFO anonymous 163x36x1 kglmiu 10.3.16.242 /secure/SetupImport.jspa [jira.bc.dataimport.DefaultDataImportService] Importing data is Shutdown JIRA. Solution 3 Stop your JIRA instance.
Start your JIRA instance. Why was this unhelpful? The following appears in the indexing screen: java.util.concurrent.ExecutionException: java.lang.NullPointerException Task completed in 17 minutes, 42 seconds with unexpected error. http://ascadys.net/jira-error/jira-500-error-after-upgrade.html Reindex JIRA, which will now complete successfully.If there are any problems, restore the previous database backup immediately.
Solution 2 Stop JIRA. Caused by: java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:472) at com.atlassian.jira.issue.index.DefaultChangeHistoryRetriever.filterChangeItems(DefaultChangeHistoryRetriever.java:120) at com.atlassian.jira.issue.index.DefaultChangeHistoryRetriever.createChangeGroupsFromChangeItems(DefaultChangeHistoryRetrieve The following appears Using the Database Integrity Checker: ERROR: ALF-14729 - The workflow entry with id 146727 has an incorrect state. (JRA-4241) JIRA used its 4.4.3 JIRA Standalone version. I created an empty database and I installed Jira there.