Jira not responding after a period of being idle, usually 1 day or less?

[Lim Han Yong]

Currently, I'm having issues with JIRA 7.12.3 not responding after a period of being idle, typically 1 day or less.

After waiting a couple of minutes, JIRA eventually responds, but my dashboard is missing / empty, menu elements on the top such as Dashboards, Projects, Issues, Boards are there, but the drop down options are missing / empty.

My JIRA instance is installed on an Ubuntu Linux 18.04 64-bit distro VM on vSphere 6.5 with the PostgreSQL Database with an SSL reverse-proxy terminating it. I have 6GB of RAM assigned to the JVM.

I ran JIRA Instance Health and it reports that everything is well, with all green ticks.

I ran the Log Analyzer and have the following output:

It is also a relatively new JIRA installation with just a single Board and less than 40 issues?

I have set a fixed amount of memory for the VM and disabled memory ballooning since vSphere memory ballooning does not behave well with JVMs according to https://www.netiq.com/communities/cool-solutions/how-vmware-esx-and-esxi-memory-ballooning-impacts-access-manager/

JIRA is installed on a single VM with:

• JIRA Core
• Jira Service Desk
• Jira Software

I have tried different things like:

• Increasing the JIRA application memory according to the steps here: https://confluence.atlassian.com/adminjiraserver073/increasing-jira-application-memory-861253796.html
• Increasing the database connection pool according to the steps here: https://confluence.atlassian.com/jirakb/poor-performance-due-to-limited-database-connection-pooling-229179892.html

[Deleted user]

Hi Lim, the best is to open directly a ticket to Atlassian using the Troubleshooting and Support tool:

https://confluence.atlassian.com/support/create-a-support-zip-790796819.html

[Lim Han Yong]

Hi Cristian,

Would be great if I could do that, but there's no support for 10-user licenses according to:

https://www.atlassian.com/blog?p=37521

[Lim Han Yong]

Apparently, it's working again after I left it alone for a day. Didn't restart the JIRA services.

This issue seems to happen intermittently and resolves itself.