Functionality Added or Changed
The included Java runtime environment has been updated to JDK 6.0 Update 29.
On the Manage Servers page of the Dashboard, the
rename button is now
details. You can enter notes about each server, which
are displayed as tooltips for the servers in the Server Tree.
The Agent could die with a vague error message when encountering a SQL error code 2013, requiring a manual restart. The message is now more specific. (Bug #11765869, Bug #58874)
The Connector/J component was upgraded to 5.1.14. (Bug #58751)
use SSL checkbox in both the full
installer and the upgrade installer for the Service Manager.
When you check that box during a full installation, the
config.properties file includes the line
mysql.use_ssl=true. The upgrade installer
defaults to checked or unchecked for that box depending on the
mysql.use_ssl in the
config.properties file. The configuration
file for the repository database includes 3 SSL-related
You cannot select
use SSL if you also use
your own MySQL instance for the repository database, and that
instance does not include SSL support. You can always select
use SSL in combination with the bundled MySQL
server, because that server includes SSL support.
(Bug #58148, Bug #11764423)
Resolved SSL issues when using MySQL Enterprise Monitor on a
server with the
(Bug #53568, Bug #11761108)
The Dashboard installation now includes the
tomcat-native packages for better scalability
of network traffic using SSL.
EXPLAIN plans were not always shown for
queries that ran for greater than 500 milliseconds.
(Bug #42105, Bug #11751302)
The graph for the
pool now reports correct totals when
innodb_buffer_pool_instances is set to a
value greater than 0. The fix only works for MySQL Server 5.5.9
(Bug #58332, Bug #60777, Bug #12346961)
stop incorrectly returned the value 1 if the
MySQL Enterprise Monitor Agent was already stopped. Now this command returns a
value of 0 in this case.
Graph Gallery, underneath the
Graphs tab, displays a large view of the
graphs with less space taken up by navigation controls.
The Start Menu shortcuts that run the
agentctl.bat script to start and stop the
MySQL Enterprise Monitor Agent did not prompt for administrator credentials when
run by a non-administrative user.
Reduced memory usage for the MySQL Enterprise Monitor Agent. Formerly, it retained in memory the canonical queries that it sent to the proxy. (Bug #40462)
For Solaris installations, MySQL Enterprise Monitor now uses the
64-bit HotSpot JVM on platforms that support it. The
-d64 flag is now included in the
JAVA_OPTS setting, in the
catalina.sh configuration file.
Upgraded the bundled Java installation to version 6.0_22. (Bug #58829)
The Manage Servers page now has a menu option
disable] event blackout. You can set up blackout
periods through the Dashboard in addition to scripting them
through the REST API. For details, see
Section 2.8.3, “Manage Servers”.
The non-anonymous bind password fields could be incorrectly
greyed out when switching between
Bind As User settings.
Each time LDAP settings were changed, the binding would fail unless the non-anonymous bind user password was re-entered. (Bug #59103)
The REST API for toggling blackout periods can now be called by
a user with the
agent role. Oracle recommends
using such a lower-privileged account, rather than including
administrator credentials in scripts.