MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Airton Lastori Date:October 17 2018 7:46pm
Subject:MySQL Enterprise Monitor 3.4.10 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.4.10 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) 8.0 offers many significant improvements over
MEM 3.4 and 4.0, and we highly recommend that you consider upgrading. More information on
MEM 8.0 is available here: 

What's New in MySQL Enterprise Monitor 8.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

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.10 

Functionality Added or Changed 

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

Bugs Fixed

* Under certain circumstances, Out Of Memory errors caused the MySQL Enterprise Monitor
Agent to restart. In the previous release, the default agent heap size, defined by the
MEM_AGENT_JAVA_OPTS parameter in the file, has been increased to 128MB.
In the previous release, this issue was corrected for new installations. As of this
release, this issue is also corrected for upgrades.
If you changed MEM_AGENT_JAVA_OPTS to a value greater than 128MB, the value is not changed
by the upgrade. If you changed MEM_AGENT_JAVA_OPTS to a value lower than 128MB, the
upgrade process updates the value to 128MB.

MySQL Enterprise Monitor 3.4.10 has been releasedAirton Lastori17 Oct