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

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

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

Hi Tiago,

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

thanks,

nick

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 52m ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

32 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you