MySQL Forums
Forum List  »  Announcements

MySQL Enterprise Monitor 3.4.5 has been released
Posted by: Andy Bang
Date: December 08, 2017 12:11PM

We are pleased to announce that MySQL Enterprise Monitor 3.4.5 is now
available for download on the My Oracle Support (MOS) web site.

This is a maintenance release that includes a few enhancements and
fixes a number of bugs. You can find more information on the contents
of this release in the change log:
(also included at the end of this note for convenience)

You will find binaries for the new release on My Oracle Support:

Choose the "Patches & Updates" tab, and then choose the "Product or
Family (Advanced Search)" side tab in the "Patch Search" portlet.

IMPORTANT: MySQL Enterprise Monitor (MEM) 4.0 offers many significant
improvements over MEM 3.4 and we highly recommend that you consider
upgrading. More information on MEM 4.0 is available here:

What's New in MySQL Enterprise Monitor 4.0

MySQL Enterprise Monitor

MySQL Enterprise Monitor Frequently Asked Questions

MySQL Enterprise Monitor Change History

Please open a bug or a ticket on My Oracle Support to report problems,
request features, or give us general feedback about how this release
meets your needs.

If you are not a MySQL Enterprise customer and want to try the Monitor
and Query Analyzer using our 30-day free customer trial, go to, or contact Sales at

Useful URLs

* My Oracle Support -
* What's New in 3.4 -
* Change log -
* Installation documentation -
* Complete documentation -
* Product information -
* Download - (available now) or

Thanks and Happy Monitoring!

- The MySQL Enterprise Tools Development Team


Changes in MySQL Enterprise Monitor 3.4.5

Functionality Added or Changed

* The Tomcat server, bundled with the MySQL Enterprise Service
Manager, has been upgraded to 8.5.23.

* The bundled JRE was updated to 1.8.0_151 for both the Agent and
Service Manager.

* As of this release, on Solaris platforms, the installer and upgrade
installer check for the presence of the Oracle Developer Studio 12.5
Runtime libraries. If these libraries are not installed, the
installation stops and displays an error.

Oracle Developer Studio 12.5 Runtime libraries must be installed
before running the MySQL Enterprise Monitor installers on Solaris.

* The MySQL server, bundled with the MySQL Enterprise Service Manager,
has been upgraded to MySQL 5.7.20.

* The OpenSSL libraries used by the MySQL Enterprise Monitor
installers and MySQL Enterprise Monitor Aggregator have been
upgraded to 1.0.2m.

Bugs Fixed

* The service_manager privilege descriptions lacked examples. For more
information, see MySQL Enterprise Monitor Repository. (Bug

* The documentation incorrectly stated that a Service Manager user
required privileges on the mysql.inventory table. The
mysql.inventory table is no longer created. (Bug #27130103)

* Some selections were not properly displayed in the Column drop-down
menus on the Query Analyzer's Advanced filter. (Bug #27110602)

* The advice page for the Prepared Statements Not Being Used
Effectively advisor incorrectly referred to the variables
Com_stmt_prepare and Com_stmt_execute. The correct variables are
Com_prepare_sql and Com_execute_sql. (Bug #26949933)

* Timeseries graphs displayed old data, such as filesystems and
network interfaces which were removed or no longer exist.

As of this release, only recently reported, active assets are
displayed in the timeseries graphs. (Bug #26942873)

* It was not possible to refresh a replication topology using the
Rediscover Replication Topologies button. An error was displayed.
(Bug #26900106)

* The link between two inactive nodes on the Replication topology view
remained green, indicating an active connection. As of this release,
links between inactive nodes are gray, indicating an unknown state.
The same is now true for lines between active and inactive nodes.
(Bug #26878020)

* Topology did not correctly display nodes which were not running.
They were displayed in Green, instead of Yellow, indicating that the
replication thread was not running. (Bug #26871473)

* Under certain circumstances, if you were upgrading to the previous
version, it was necessary to edit server.xml and add
maxHttpHeaderSize="65536" to each of the default connectors.

As of this release, it is no longer necessary to manually edit
server.xml, the upgrade installer checks and corrects the values
automatically if they are set to a value less than 64K. If
maxHttpHeaderSize is set to 64K or higher, the upgrader installer
makes no changes. (Bug #26828438)

References: See also: Bug #26391094.

* It was not possible to select the last graph in the drop-down menu
on the Overview dashboard. (Bug #26679583)

* It was not possible to delete or edit a notification group if the
subject contained braces, { or }. An error was displayed.

As of this release, it is possible to edit, and correct,
notification group subjects which contain unsupported characters.
Also, an error is displayed on saving if the notification group's
subject contains an unsupported character. (Bug #25535520)

* Under certain circumstances, bulk schedule changes were not
correctly applied to the replication advisors, Group Replication
Configuration and Group Replication Status.

* On the Advisors view, Filter and Expand filtered the advisor
selection, but did not expand it as expected.

Also, some Advisor controls were not correctly rendered after

* Expanding the Filter, on any page which includes the Asset Selector,
disabled the Asset Selector's Show All Assets checkbox, unless it
was already enabled.

* If Show All Assets was not enabled, expanding the Filter forced the
Asset Selector to reload and display only MySQL instances.

* Under certain circumstances, the graphs in the Support Diagnostics
archive could not be loaded in some browsers.

* The graphs tab of the Query Analyzer's Query dialog was larger than
the dialog which contained it.

* The Group Name icon was not displayed correctly on the Email
Notification Group page.

* A rate limit exception caused a null pointer exception which stopped
the MySQL Enterprise Service Manager from retrieving the sys schema

* OS X 10.13 was not reported as Mac OS X (High Sierra), but as

* Data purge was not completed if the MySQL Enterprise Service Manager
was restarted while the purge was running.

Options: ReplyQuote

Written By
MySQL Enterprise Monitor 3.4.5 has been released
December 08, 2017 12:11PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.