nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA not allowing issue creation on restart (possible reason pointed caching)

khelender

Our locally hosted JIRA solution is failing giving problem shown in attached image snapshot (Error at top right)

Community answer suggested clearing cache, but the HOME directory doesn't have cache directory (possibly the name may have changed)

Can someone validated:

1) Whether this problem may be due to caching?

2) If yes, how to find cache directory in JIRA version 7.12.1 Screenshot from 2018-11-06 08-24-07.png

Accepted answers

Alexey Matveev

Hello,

It could be connected to indexes.

The cache directory is in the JIRA_HOME directory. You can find the path to the JIRA_HOME directory in cog item -> system -> system info. Find the Location of Jira Local Home parameter.

All comments

Alexey Matveev

Hello,

It could be connected to indexes.

The cache directory is in the JIRA_HOME directory. You can find the path to the JIRA_HOME directory in cog item -> system -> system info. Find the Location of Jira Local Home parameter.

khelender

Thanks,

I was able to find the Cache directory, and cleaned it up. (I created a tar file of before deleting the content)

However,

=> Cleanup seems to have destroyed lot of tracking information related to JIRA Issues, and the Dashboard charts are not displaying graphs (related data seems to have got lost).

=> Kanban board is not showing up any issues that were put up in

Or the index takes around quite a minutes to build up and show up (The number of issues was not very large for the project)

Any related suggestion to recover the data back?

Alexey Matveev

Hello,

It means that the reindex failed. Could you have a look at atlassian-jira.log?

khelender

This is what I found at end of log file at restart

2018-11-08T16:43:53.992+0530: 373.138: [GC (Allocation Failure) [PSYoungGen: 241664K->2912K(247808K)] 750909K->518605K(772096K), 0.0422643 secs] [Times: user=0.07 sys=0.00, real=0.05 secs]
2018-11-08T16:43:54.285+0530: 373.430: [GC (System.gc()) [PSYoungGen: 102714K->1472K(248320K)] 618408K->518325K(772608K), 0.0427580 secs] [Times: user=0.09 sys=0.00, real=0.04 secs]
2018-11-08T16:43:54.327+0530: 373.473: [Full GC (System.gc()) [PSYoungGen: 1472K->0K(248320K)] [ParOldGen: 516853K->228914K(524288K)] 518325K->228914K(772608K), [Metaspace: 238885K->226324K(1273856K)], 0.6984690 secs] [Times: user=1.83 sys=0.00, real=0.70 secs]
Heap
 PSYoungGen total 248320K, used 18105K [0x00000000f0000000, 0x00000000fff00000, 0x0000000100000000)
 eden space 236544K, 7% used [0x00000000f0000000,0x00000000f11ae7a0,0x00000000fe700000)
 from space 11776K, 0% used [0x00000000ff380000,0x00000000ff380000,0x00000000fff00000)
 to space 12288K, 0% used [0x00000000fe700000,0x00000000fe700000,0x00000000ff300000)
 ParOldGen total 524288K, used 228914K [0x00000000d0000000, 0x00000000f0000000, 0x00000000f0000000)
 object space 524288K, 43% used [0x00000000d0000000,0x00000000ddf8cb88,0x00000000f0000000)
 Metaspace used 226441K, capacity 244181K, committed 260800K, reserved 1273856K
 class space used 30619K, capacity 35091K, committed 37056K, reserved 1048576K