JIRA failed to establish a connection to database after Update to 8.1

[Tomasz Pordzik]

Hello everybody
after update to version 8.1 no connection to mysql is possible.

During the installation I had to update MySQL connector (mysql-connector-java-8.0.15.jar)

The web interface displays the following:

a connection is possible via CLI:

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the community!

This is an issue that puts too little information in front of you on-screen.  We need to go read the log file for the actual errors.  You can find this in <jira home>/logs/atlassian-jira.log

[Tomasz Pordzik]

Thanks are the logs

root@atl-01:/opt/atlassian/jira/logs# cat atlassian-jira-gc-2019-04-07_15-10-12.log.0.current
Java HotSpot(TM) 64-Bit Server VM (25.181-b13) for linux-amd64 JRE (1.8.0_181-b13), built on Jul 7 2018 00:56:38 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)
Memory: 4k page, physical 10243336k(4609476k free), swap 2094076k(2094076k free)
CommandLine flags: -XX:GCLogFileSize=20971520 -XX:InitialCodeCacheSize=33554432 -XX:InitialHeapSize=402653184 -XX:MaxHeapSize=805306368 -XX:NumberOfGCLogFiles=5 -XX:-OmitStackTraceInFastThrow -XX:+PrintGC -XX:+PrintGCCause -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:ReservedCodeCacheSize=536870912 -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC
2019-04-07T15:10:12.741+0200: 0.655: [GC (Allocation Failure) [PSYoungGen: 98304K->12843K(114688K)] 98304K->12851K(376832K), 0.0295642 secs] [Times: user=0.10 sys=0.00, real=0.03 secs]
2019-04-07T15:10:13.020+0200: 0.933: [GC (Allocation Failure) [PSYoungGen: 111147K->15026K(212992K)] 111155K->15106K(475136K), 0.0106134 secs] [Times: user=0.05 sys=0.00, real=0.01 secs]
2019-04-07T15:10:13.290+0200: 1.203: [GC (Allocation Failure) [PSYoungGen: 211634K->16364K(212992K)] 211714K->17911K(475136K), 0.0126937 secs] [Times: user=0.03 sys=0.01, real=0.01 secs]
2019-04-07T15:10:13.499+0200: 1.413: [GC (Allocation Failure) [PSYoungGen: 212972K->16356K(245760K)] 214519K->20679K(507904K), 0.0137667 secs] [Times: user=0.04 sys=0.01, real=0.01 secs]
2019-04-07T15:10:13.701+0200: 1.615: [GC (Allocation Failure) [PSYoungGen: 245732K->16379K(245760K)] 250055K->23802K(507904K), 0.0092219 secs] [Times: user=0.04 sys=0.01, real=0.01 secs]
2019-04-07T15:10:13.919+0200: 1.833: [GC (Allocation Failure) [PSYoungGen: 245755K->16363K(228352K)] 253178K->30615K(490496K), 0.0093314 secs] [Times: user=0.03 sys=0.00, real=0.01 secs]
2019-04-07T15:10:14.141+0200: 2.055: [GC (Allocation Failure) [PSYoungGen: 228331K->19137K(237056K)] 242583K->45054K(499200K), 0.0105519 secs] [Times: user=0.04 sys=0.00, real=0.01 secs]
2019-04-07T15:10:14.520+0200: 2.434: [GC (Allocation Failure) [PSYoungGen: 231105K->11999K(236032K)] 257022K->39093K(498176K), 0.0062458 secs] [Times: user=0.04 sys=0.00, real=0.01 secs]
2019-04-07T15:10:14.570+0200: 2.483: [GC (Metadata GC Threshold) [PSYoungGen: 24590K->5319K(216576K)] 51684K->33213K(478720K), 0.0035919 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
2019-04-07T15:10:14.573+0200: 2.487: [Full GC (Metadata GC Threshold) [PSYoungGen: 5319K->0K(216576K)] [ParOldGen: 27893K->18938K(262144K)] 33213K->18938K(478720K), [Metaspace: 20871K->20871K(1069056K)], 0.0522652 secs] [Times: user=0.17 sys=0.00, real=0.05 secs]
2019-04-07T15:10:15.052+0200: 2.965: [GC (Allocation Failure) [PSYoungGen: 210944K->11853K(236032K)] 229882K->30800K(498176K), 0.0072799 secs] [Times: user=0.04 sys=0.00, real=0.01 secs] 

[Nic Brough -Adaptavist-]

Ok, that's Garbage Collection failing, not the database.  This can be caused by all sorts of things, but in this case, I notice your maximum heap size is set to the default value (768Mb), which is very small and only usually used to get an empty one running.  I would try increasing to 1Gb and trying again.

[Tomasz Pordzik]

it works thank you