Below is the information from my admin who is in charge of the server.
- No resource exhaustion. CPUs were almost completely idle (<1% utilization), approximately 2GB of RAM free, very little I/O (<1% utilization).
- The catalina.out log contained no activity since 8:37. The atlassian log contained multiple java garbage collection failures. It’s not clear what these mean, as they seem to occur often during normal operation. An example:
2018-08-29T08:55:49.092-0400: 1.515: [GC (Allocation Failure) [PSYoungGen: 98304K->12751K(114688K)] 98304K->12759K(376832K), 0.0182664 secs] [Times: user=0.03 sys=0.00, real=0.02 secs]
2018-08-29T08:55:49.587-0400: 2.009: [GC (Allocation Failure) [PSYoungGen: 111055K->15553K(212992K)] 111063K->15569K(475136K), 0.0222298 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
2018-08-29T08:55:50.040-0400: 2.462: [GC (Allocation Failure) [PSYoungGen: 212161K->16363K(212992K)] 212177K->18148K(475136K), 0.0209804 secs] [Times: user=0.03 sys=0.00, real=0.02 secs]
2018-08-29T08:55:50.405-0400: 2.827: [GC (Allocation Failure) [PSYoungGen: 212971K->16375K(245760K)] 214756K->20948K(507904K), 0.0303257 secs] [Times: user=0.06 sys=0.00, real=0.03 secs]
- The problem affected the jira application only. The database (MySQL) was operating normally, and did not require a restart.
It's sort of telling you it is running out of memory. Start at https://confluence.atlassian.com/enterprise/garbage-collection-gc-tuning-guide-461504616.html to troubleshoot
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.