What is the relation between Fixversions and Components in JIRA. "tables which are involved in "issue.getComponents" and ''changing FIX version on transition

Question

Hello Team,

Please find the issues we are facing below:

1)I have upgraded JIRA from 6.3.15 to 7.0.4, After that I'm facing issue with Transition. - (If I change "FixVersion OR "affects version" on transition screen entire jira is getting hung)

The above behavior is happening only if "component Watchers" plugin is enabled and "Component/s" field is not available on the transition screen.

2)We have extensively used "Components Watchers plugin" so cannot go without that plugin.

3) As part of analyzing I have deleted all the existing projects in JIRA(test which is upgraded to 7.0.11) and created a "Test project" and only one issue till the issue is persisting.

4)If you need I can provide the DB dump as well.

5) Same problem is there if install new jira and point to this DB.

6)Tried re-indexing, Integrity checker many times.

7)Analyzed the plugin code - JIRA is getting hung only when it tries to use 
"issue.getComponents()" Api 
only if "component Watchers" plugin is enabled and "Component/s" field is not available on the transition screen.

Nic Brough -Adaptavist- · Answer

>Disclaimer: Don't blame me for this; I didn't do it.

I know

crf · Answer

They have very little in common technically, but there is one particular place where they run into each other, and that is in the way that they are stored in the database:

Disclaimer: Don't blame me for this; I didn't do it.

Not everybody is an expert in database design.  One of the early schema design decisions that still haunts JIRA is the existence of this "nodeassociation" table that connects essentially any entity to essentially any other.  As you can see from this sampling from one of our internal systems, this is used to associate projects with their schemes (mostly... field configuration schemes are handled differently), and also what associates an issue with its affects versions, fix versions, and components.

My guess would be that this plugin is causing a deadlock by doing work inside of a transaction that is not working and playing well with the transaction for the issue edit that changes the components, probably due to interactions in the nodeassociation table.  The deadlock may be entirely in the database, or it may be an interaction between a database lock and a JVM lock within JIRA or the plugin.  These problems can be pretty difficult to diagnose, and which database you are using would be important information for knowing how to look for the transaction involved.

I would:

* Reproduce the problem
* Get a snapshot of what database transactions are open and what statement, if any, they are currently executing.
* Use jstack to dump the JIRA threads
* Try to reconcile the mutual lock information to identify what the lock actually is.  I would focus on database queries that use the nodeassociation table and JVM threads that use calls like "getRelated".  Be warned that this is not easy, and it's probably more appropriate to submit this in a bug report with the plugin developer.

Nic Brough -Adaptavist- · Answer

Ah, you mean the associative link table?  I was thinking more of the business logic, not quite how they're stored.