Bug #71581 MEM server 3.0.6 upgrade does not properly stop java/tomcat
Submitted: 4 Feb 2014 9:23 Modified: 9 Jan 2015 10:13
Reporter: Simon Mudd (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S3 (Non-critical)
Version:3.0.6 OS:Linux
Assigned to: CPU Architecture:Any
Tags: windmill

[4 Feb 2014 9:23] Simon Mudd 
Description:
I ran the upgrade installer: mysqlmonitor-3.0.6.2936-linux-x86_64-update-installer.bin to upgrade a working 3.0.5 MEM server.

I noticed after restarting 3 different MEM servers I'd upgraded that I had 2 copies of the tomcat server running, that is the older version will not running when it should have shutdown.

How to repeat:
Install 3.0.5
run the upgrade installer (I didn't shutdown MEM first)
see if more than 1 instance of MEM is running.

Suggested fix:
Ensure that MEM (the java processes) is shutdown prior to completing the install.
I've noticed in the past that on a busy server it can take a long time.
I've also resorted to simply kill -9 <java pids> which isn't nice but is effective.
While this should not be necessary if the script that's doing the shutdown sees that it hasn't been effective perhaps it should consider doing the same, thus ensuring that tomcat is stopped.