Bug #70600 monitor shutdown does not give enough time to shutdown tomcat
Submitted: 11 Oct 2013 7:48 Modified: 9 Jan 2015 10:15
Reporter: Simon Mudd (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S3 (Non-critical)
Version:3.0.2.2900 OS:Any
Assigned to: CPU Architecture:Any

[11 Oct 2013 7:48] Simon Mudd
Description:
I often see this when shutting down the dashboard:

[root@myhost ~]# /opt/mysql/enterprise/monitor/mysqlmonitorctl.sh stop
Using CATALINA_BASE:   /opt/mysql/enterprise/monitor/apache-tomcat
Using CATALINA_HOME:   /opt/mysql/enterprise/monitor/apache-tomcat
Using CATALINA_TMPDIR: /opt/mysql/enterprise/monitor/apache-tomcat/temp
Using JRE_HOME:        /opt/mysql/enterprise/monitor/java
Using CLASSPATH:       /opt/mysql/enterprise/monitor/apache-tomcat/bin/bootstrap.jar:/opt/mysql/enterprise/monitor/apache-tomcat/bin/tomcat-juli.jar
Using CATALINA_PID:    /opt/mysql/enterprise/monitor/apache-tomcat/temp/catalina.pid
Tomcat did not stop in time. PID file was not removed.    <<========
Stopping tomcat service ....... [ OK ]
Stopping mysql service .................. [ OK ]
[root@myhost ~]# 

It looks as if the shutdown script does not wait very long to shutdown tomcat. Perhaps it should wait up to about 30 seconds for this? Other than that the shutdown process seems to work, but this error seems a bit silly.
Tomcat did not stop in time. PID file was not removed.

How to repeat:
see above.

Suggested fix:
remove the message, or maybe wait longer for tomcat to stop. A busy dashboard may take quite a while to shutdown cleanly.