Advanced Roadmap Plan Creation Error

[ranaweer]

Unable to instantiate QIssueSource schema.java.lang.RuntimeException: Unable to instantiate QIssueSource schema.

  at com.atlassian.rm.jpo.core.issuesource.schema.QIssueSourceFactory.table:27
  at com.atlassian.rm.jpo.core.issuesource.sql.QueryDslIssueSourcePersistence.addIssueSourcesTransactional:121
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$null$1:251
  at com.atlassian.rm.common.persistence.transaction.Registry.run:35
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$createPlan$4:247
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inTransaction:111
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:99
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:89
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.lambda$inDatabaseTransaction$3:69
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.lambda$run$0:24
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.lambda$execute$0:34
  at com.atlassian.rm.common.bridges.jira.persistence.JiraDatabaseProviderBridge710.execute:59
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.execute:34
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.run:24
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inDatabaseTransaction:68
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.createPlan:227
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:21
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:8
  at com.atlassian.rm.jpo.env.threading.AbstractTranslatedLongRunningTaskProvider$1.run:25
  at com.atlassian.rm.jpo.env.threading.JiraLongRunningExecutorRegistry$1$1.run:48
  at com.atlassian.rm.common.bridges.jira.threading.LongRunningExecutorServiceBridge710.lambda$execute$0:104
  at com.atlassian.rm.common.bridges.jira.threading.JiraSafeThreadService.lambda$execute$0:47
  at java.util.concurrent.FutureTask.run:266
  at java.util.concurrent.ThreadPoolExecutor.runWorker:1149
  at java.util.concurrent.ThreadPoolExecutor$Worker.run:624
  at java.lang.Thread.run:748

Caused by java.lang.IllegalArgumentException: Not able to find table AO_D9132D_ISSUE_SOURCE

  at com.atlassian.rm.common.pkqdsl.legacy.DefaultSchemaProvider.getSchema:61
  at com.atlassian.rm.common.bridges.jira.persistence.JiraSchemaProviderBridge710.getSchemaName:25
  at com.atlassian.rm.common.persistence.env.JiraSchemaProvider.getSchema:27
  at com.atlassian.rm.common.persistence.ActiveObjectsMediator.getSchema:34
  at com.atlassian.rm.common.persistence.EmptyActiveObjectsRelationalPathBase.<init>:36
  at com.atlassian.rm.common.persistence.EmptyActiveObjectsRelationalPathBase.<init>:25
  at com.atlassian.rm.common.persistence.ActiveObjectsRelationalPathBase.<init>:21
  at com.atlassian.rm.jpo.core.issuesource.schema.QIssueSource.<init>:27
  at com.atlassian.rm.jpo.core.issuesource.schema.QIssueSourceFactory.table:23
  at com.atlassian.rm.jpo.core.issuesource.sql.QueryDslIssueSourcePersistence.addIssueSourcesTransactional:121
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$null$1:251
  at com.atlassian.rm.common.persistence.transaction.Registry.run:35
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$createPlan$4:247
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inTransaction:111
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:99
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:89
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.lambda$inDatabaseTransaction$3:69
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.lambda$run$0:24
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.lambda$execute$0:34
  at com.atlassian.rm.common.bridges.jira.persistence.JiraDatabaseProviderBridge710.execute:59
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.execute:34
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.run:24
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inDatabaseTransaction:68
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.createPlan:227
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:21
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:8
  at com.atlassian.rm.jpo.env.threading.AbstractTranslatedLongRunningTaskProvider$1.run:25
  at com.atlassian.rm.jpo.env.threading.JiraLongRunningExecutorRegistry$1$1.run:48
  at com.atlassian.rm.common.bridges.jira.threading.LongRunningExecutorServiceBridge710.lambda$execute$0:104
  at com.atlassian.rm.common.bridges.jira.threading.JiraSafeThreadService.lambda$execute$0:47
  at java.util.concurrent.FutureTask.run:266
  at java.util.concurrent.ThreadPoolExecutor.runWorker:1149
  at java.util.concurrent.ThreadPoolExecutor$Worker.run:624
  at java.lang.Thread.run:748

===============
=== Request ===
===============

URL: /jira/rest/jpo/1.0/plans/async/554e7b1a-3456-4ce9-b24e-625857800a1d?_=1595288594228
Type: GET
Status: 500
Data: undefined

===================
=== Client Info ===
===================

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15
Local time: Mon Jul 20 2020 17:44:09 GMT-0600 (MDT)

===================
=== Plugin Info ===
===================

Plugin build: 3.29.0

===================
=== System Info ===
===================

Jira Title: Arts Resource Centre JIRA
Jira Version: 8.7.1
Agile Version: 8.7.1

[Earl McCutcheon]

Hello @ranaweer ,

Thanks for reaching out 

The main portion of the error is noting:

Unable to instantiate QIssueSource schema

And the follow up caused by is noting the table cannot be located:

Caused by java.lang.IllegalArgumentException: Not able to find table AO_D9132D_ISSUE_SOURCE

These errors looks like its going to be something related to a database configuration issue most likely a collation error.  

Some tables have a persistence class and a service and the rest of the code access the table only through the service but there are some exceptions where some classes are access directly via a persistence or the Q-class schema.  These persistence classes become problematic and will trigger a lot of extra log noise when there are other database related connection or configuration issues at hand, and from the "caused by" error it looks like during the app install process tables failed to write to the database.

Can you Tail the Jira log's output to see if you can pick up any additional database errors while triggering this error.  Also check the Database Collation Health checks for failures.

if it does turn out to be a collation issue the following KB article gives some context to this:

• Startup check: Changing your JIRA database collation

And a condensed breakdown on the approach to fix it is as follows:

1. Select a database type/version from our Supported platforms Documentation
2. Create a new blank database per Connecting JIRA to a database, (paying close attention to the correct collation for that database type)
3. Gather an XML backup  of your JIRA instance. Even if you can't start JIRA, you can still find a recent one of these backups in the filesystem of the JIRA server. By default this is saved in <jira-home>/export/ folder 
4. Stop JIRA
5. Run the JIRA Configuration tool  to tell JIRA to use the new blank database, save these changes, (if you can't run this, then you can just directly edit the <jira-home>/dbconfig.xml file to make these changes)
6. Start JIRA up again (when JIRA starts with an empty database, it automatically launches the setup wizard)
7. Copy the export XML zip file from <jira-home>/export/ into <jira-home>/import/ 
8. Then you can import the backup using the 'Import your data' link in the setup wizard

By following these steps you can then import your previous data into a supported database with the correct database setup.

Once the DB collation error is corrected Uninstall and reinstall advanced roadmaps.

Regards,
Earl