The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Unexpected Failure - Data may be in an unstable state when importing from Bugzilla

Henry CC
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 20, 2013

Hello,

We receive the following error when trying to import from Bugzilla to Jira.

2013-02-19 18:25:53,595 INFO - ------------------------------

2013-02-19 18:25:53,595 INFO - Finished Importing : Issues

2013-02-19 18:25:53,595 INFO - ------------------------------

2013-02-19 18:25:53,595 ERROR - Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state

java.lang.NullPointerException

at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.createQueryForExternalSystemUrl(DefaultJiraDataImporter.java:371)

at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:329)

at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:25)

at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:14)

at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:359)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)

at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)

at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:249)

at java.lang.Thread.run(Thread.java:662)

2013-02-19 18:25:53,607 INFO - No issues need to be reindexed.

The bug records do import from Bugzilla but the link data between bugs (Depends on / Blocks) is not replicated in Jira so we loose all our bug relationships.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Tiago Comasseto
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 Champions.
February 20, 2013

Hi Henry,

I think it may be related to data corruption into Bugzilla database. You may check if this is the case using a tool called Sanity Check within Bugzilla Administration section.

Cheers

Henry CC
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 20, 2013

Hi Tiago,

thanks for the reply, i've run a sanity check and it came back clean.

thanks,

nick

TAGS
AUG Leaders

Atlassian Community Events