MySQL Bugs: #51842: MEM JRE 6.0_18-b07 causing crashes on Linux 64bit

Bug #51842	MEM JRE 6.0_18-b07 causing crashes on Linux 64bit
Submitted:	8 Mar 2010 19:48	Modified:	24 May 2010 10:21
Reporter:	Mark Leith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S1 (Critical)
Version:	2.1.0.1094	OS:	Linux
Assigned to:	BitRock Merlin	CPU Architecture:	Any

Description:
The upgraded JRE has seen the following crashes:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002b9e2724d63c, pid=22850, tid=1083324736
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0-b13 mixed mode linux-amd64 )
# Problematic frame:
# V [libjvm.so+0x62263c]
#

Rolling back to the previous version of the JRE, and keeping the same application version causes these crashes to stop. 

How to repeat:
Have not managed to reproduce, and seems to happen at random intervals at the customer

Suggested fix:
Rollback to the previous version of the JRE we were using - 1.6.0_13-b03.

Note that we should roll back the JRE on all platforms so we're consistent across them.

Patch sent to Keith.

Keith Russell writes: 
SVN repository updated.

Keith Russell writes: 
Available in build version => 2.2.0.1643.

Carsten Segieth writes: 
Build 2.2.0.1643 has "Java(TM) SE Runtime Environment (build 1.6.0_13-b03)" packaged for all except Mac OSX.

On MacOSX I get different results for the Java version than the above shown version, where on the older 10.4 system 'osx-imac-x86' the version showed for 'java -version' and the version that is mentioned in the 'catalina.out' are identical:

   fom catalina.out:
   -----------------
   Using _RUNJAVA -version java version "1.5.0_13"
   Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
   Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing)

   osx-imac-x86:~ mysqldev$ which java
   /usr/bin/java

   osx-imac-x86:~ mysqldev$ java -version
   java version "1.5.0_13"
   Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
   Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing)

... but on the 10.5 system 'xserve-e' they differ:

   fom catalina.out:
   -----------------
   Using _RUNJAVA -version java version "1.6.0_07"
   Java(TM) SE Runtime Environment (build 1.6.0_07-b06-153)
   Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_07-b06-57, mixed mode)
   
   xserve-e:~ mysqldev$ which java
   /usr/bin/java

   xserve-e:~ mysqldev$ java -version
   java version "1.5.0_16"
   Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284)
   Java HotSpot(TM) Server VM (build 1.5.0_16-133, mixed mode)

This needs to be checked/verified before I can close this bug. This difference is not new and can be seen already when having older builds installed.

Mark Matthews writes: 
Carsten,

We can't change the version of Java that's on the Mac. It ships as part of the platform, and there is really no way to change them, so we test against what's shipped by Apple.

Pre-release change, no changelog entry required.

This bug has been seen in 2.1.1.1141 so it seems we need a fix implemented for 2.1.

WORKAROUND:
Download the following:
ftp://ftp.mysql.com/pub/mysql/download/jre_6_13.tar.gz

To deploy it:
cd /opt/mysql/enterprise/monitor
./mysqlmonitorctl.sh stop tomcat
rm -rf ./java
cp /path/to/jre_6_13.tar.gz .
tar -xvf jre_6_13.tar.gz
./mysqlmonitorctl.sh start tomcat

This would have to be done after any upgrade as well until upgrading to a fixed version.

WORKAROUND:

Downgrade to 2.1.0 version of Monitor

Andy Bang writes: 
We have a fix for this in our 2.2 release, but now we also need the fix in our 2.1 maintenance release.

Patch for 2.1 version sent to Keith.

Keith Russell writes: 
Installer repository updated.

Bill Weber writes: 
verified that we have rolled back to 6.0_13 in build 2.1.2.1162

Pre-release change, no changelog entry required.