Error after Upgrade Jira 7.13 =>8.9.1

[anvar.sadikhov]

I have upgraded test environment from 7.13 to 8.9.1 and service desk 4.9.1. I have also upgraded all plugins include Insight.

After upgrades it gives Something went wrong.Contact administrator.

There are WARN in atlassian-jira.log file

2020-06-21 17:06:29,848+0400 SdSerialisedOffThreadProcessor:thread-1 WARN      [c.a.j.cache.request.RequestCacheImpl] Incorrect usage of JIRA API. You can only create/use: RequestCacheImpl inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtil for details.
2020-06-21 17:06:29,848+0400 SdSerialisedOffThreadProcessor:thread-1 WARN      [c.a.j.cache.request.RequestCacheImpl] From Jira 9.0 version creation/usage of RequestCacheImpl will throw the IllegalStateException.

I have tried to use this in log4j.properties and it didn't help me.

log4j.logger.com.atlassian.jira.cache.request.RequestCacheImpl = ERROR, filelog
log4j.additivity.com.atlassian.jira.cache.request.RequestCacheImpl = false

https://jira.atlassian.com/browse/JSDSERVER-6897?_ga=2.111594759.224273647.1593551794-1615353982.1582310973

I have also tried restore to restore Insight to the previous version of plugin that was installed. I have cleaned all plugins caches and this error on the web page disappeared. 

When I update Insight to the newest one it is appear again.

[Andrew Downs]

I have the same issue after upgrading our QA from 8.7.1 to 8.9.1.

Can concur, when removing Insight the error goes away from within Jira, but the errors in the log to do not. The moment Insight is reinstalled the error returns.

But I would suspect it's a bug in the way Insight is trying to handle things

[anvar.sadikhov]

Hi. Do you have any ideas to solve that?

[Andrew Downs]

Not at the moment. Will update if I figure it out.

[anvar.sadikhov]

Thank you

[Viktor Cardfelt]

We have the same issue on our testserver, I have created a ticket to Mindville. 

[Andrew Downs]

So there was a preparation guide that needed to be followed. The steps I received from mindville are as follows:

The Steps to take now, as you have upgraded already are as follows (and here is the MSSQL Database example):

Start by uninstalling Insight (no Data loss is expected)
When uninstalled, query the database:

ALTER TABLE AO_8542F1_IFJ_OBJ_ATTR_VAL DROP CONSTRAINT fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id;

Then, run the following SQL query:

UPDATE propertystring SET propertyvalue = '75' WHERE id = ( SELECT id FROM propertyentry WHERE property_key = 'com.riadalabs.jira.plugins.insight:build');

Install Insight version 8.5.2 (currently recommended) or 8.6.0
After installation, query the database:

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);

Then (for MSSQL ONLY):

UPDATE AO_8542F1_IFJ_ICON SET TYPE_ID = 0 WHERE TYPE_ID IS NULL

It is important to run a clean re-index of Insight when the above steps are done.

[Andrew Downs]

Just followed the steps and all working now.

[anvar.sadikhov]

This line is not passed

UPDATE AO_8542F1_IFJ_ICON SET TYPE_ID = 0 WHERE TYPE_ID IS NULL

Msg 207, Level 16, State 1, Line 1
Invalid column name 'TYPE_ID'.

[anvar.sadikhov]

Thank you a very much Andrew.

I've restored to the old 7.13 version then tried step by step upgraded to JSW 8.55 LTS version with insight 8.5.2. All works great.

Also passed this line  with 'TYPE_ID'

UPDATE AO_8542F1_IFJ_ICON SET TYPE_ID = 0 WHERE TYPE_ID IS NULL

Thank you a lot.

[anvar.sadikhov]

Also installed Insight 8.6.2. Works great!

[anvar.sadikhov]

I've tested this on test environment works great. But on buy prod environment it doesn't work. I've done all queries the same way but it still can't find TYPE_ID attribute for AO_8542F1_IFJ_ICON. It is missed. Why?

[Viktor Cardfelt]

What I understand the issue is actually with Jira and there is an fix for this waiting to be released. 

https://jira.atlassian.com/browse/JSDSERVER-6897?error=login_required&error_description=Login+required&state=2e75ad5d-c153-4342-afba-a1f8c0cf0e8b&state=97cd937e-62b7-4a56-93e2-3ac10f9ecd52

We turned the logging off for this basically on the test server, but will wait until its completely fixed before we upgrade prod. 

[Andrew Downs]

That fixes the log display, the other issue seems to have been related to the upgrade of Insight. looking forward to the fix though, the less errors in the logs the easier it is to track down an actual issue :).

[Arman Feyzi]

I try to fix this bug by this way, but when I want to use SQL queries return this error:

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONSTRAINT fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id' at line 1

My SQL version = Ver 14.14 Distrib 5.7.31.

How I can fix this? @Andrew Downs 

[Andrew Downs]

Hi Arman,

Sorry for the delayed response. The steps I mentioned were for Microsoft SQL. 

MySQL I think is as follows:

1. Before installation, query the database:

   ALTER TABLE AO_8542F1_IFJ_OBJ_ATTR_VAL DROP FOREIGN KEY fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id;

2. Install new Insight version.

3. After installation, query the database:

   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);

More details are here:

https://documentation.mindville.com/insight/latest/preparing-for-insight-version-8-4-36953678.html