Hello,
after upgrade to 8.15 we got the following error in the admin panel:
The instance health shows no error but in the logs following entry is shown:
2021-03-06 06:58:43,344+0100 http-nio-8080-exec-13 url: /jira/rest/insight/1.0/global/config; user: pmarx ERROR pmarx 418x5210x1 9kws0h x.x.x.x.x.x,0:0:0:0:0:0:0:1 /rest/insight/1.0/global/config [c.r.j.p.i.services.core.ConfigureServiceImpl] RuntimeException:bundle [com.riadalabs.jira.plugins.insight]com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.riadalabs.jira.plugins.insight] at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:95) at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:86) at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:38) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:Database: - name:Microsoft SQL Server - version:13.00.4259 - minor version:0 - major version:13 - name:Microsoft JDBC Driver 7.2 for SQL Server - version:7.2.1.0com.microsoft.sqlserver.jdbc.SQLServerException: Auf die pk_AO_8542F1_IFJ_OBJ_ATTR_ID-Einschränkung wird von der AO_8542F1_IFJ_OBJ_ATTR_VAL-Tabelle, FOREIGN KEY-Einschränkung "fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id" verwiesen. at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:54)
How can we fix that?
Thanks and regards
Phil
I'm having the same problem after upgrading to Jira 8.20, did you find a reason/solution?
Dear Dimitri,
the Insight Application caused the error. Please find below the answer from the atlassian support team:
Those errors usually occur if you have upgraded Insight from a version below 8.4 (You may have been done it in the past) without first carry out the database changes needed, https://confluence.atlassian.com/insightapps/preparing-for-insight-8-4-1085180929.html and now we are carrying over those errors.
We have a KB, https://confluence.atlassian.com/jirakb/something-went-wrong-contact-administrator-error-pop-up-is-seen-in-many-jira-pages-after-upgrading-to-jsm-version-above-4-15-1085180562.html to help to get rid of those errors.
In your case, can you please follow the steps below:
Steps required direct modification in the database. Before applying it to a Production instance, please test on an instance where the issue can also be reproduced, and/or take a database backup before applying the database changes.
ALTER TABLE AO_8542F1_IFJ_OBJ_ATTR_VAL DROP CONSTRAINT fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id;
UPDATE propertystring SET propertyvalue = '75' WHERE id = ( SELECT id FROM propertyentry WHERE property_key = 'com.riadalabs.jira.plugins.insight:build');
ALTER TABLE AO_8542F1_IFJ_OBJ_ATTR_VAL ADD CONSTRAINT fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id FOREIGN KEY (OBJECT_ATTRIBUTE_ID) REFERENCES AO_8542F1_IFJ_OBJ_ATTR (ID);
Jira > Administration > Manage apps > Indexing Insight > Clean Re-Index
Hope it helps.
Regards,
Philipp
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.