...

• Configure the DNS used by the Jira host to resole the proxy name
• Add the proxy name and address to the /etc/hosts file

Time outs in the logs / Incomplete hierarchies / blank JQLs / CPU & Performance issues (ADVANCED)

Sometimes Links Hierarchy might require a lot of time to read all the data, this might require consuming Jira resources (CPU, Threads, RAM, etc) for a long while that might cause performance issues. If the timeout threshold is reached, the user could get an incomplete hierarchy. It is possible to tune it in the database:

...

So, the app divides the job of the threads into pulses of work:

Image Added

Each thread building a hierarchy works for X milliseconds and then sleeps for Y ms. If the job is not completed under a threshold (Z), the job is aborted and the thread frees.

JQLs support an additional timeout: 

A JQL returning N issues will build N hierarchies by using pulses of work foe each root issue. This creates a sequence of pulses that might take a long while. This makes the thread might also take a lot of work (minutes) to be completed. The JQL timeout is checked every time between the start and the end of the sequences of pulses. If the timeout is reached (W), the JQL will by atomátically aborted freeing the thread. In that way, Jira administrators can avoid too long working threads. 

• SLEEP_INTERVAL (X): The number of milliseconds that the process will wait to go work before to sleep. The default is 250 ms.
• SLEEP_DURATION (Y): How many milliseconds the process will sleep. The default is 100 ms.
• TIMEOUT (Z): The threshold in milliseconds to get all the hierarchy data (includes sleeping time). The default is 10000 ms
• TIMEOUT_JQL (W): The threshold in milliseconds to get all the jql data (includes sleeping time). The default is 60000 ms

In other words, the process of reading data works for 250 milliseconds, then goes to sleep for 100 milliseconds in a loop. After 10 seconds the process is aborted causing incomplete hierarchies for every issue hierarchy. In addition for JQL, there is one-minute timeout to complete the work.

In the case of the jql's, if TIMEOUT_JQL is exceeded, the execution of the jql will be aborted and will return an empty set of data.

The SLEEP parameters can be modified to allow the process to read data faster and the TIMEOUT for more time. 

...