MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:September 22 2017 7:03pm
Subject:MySQL Enterprise Monitor 3.2.9 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.2.9 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:

     http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/news-3-2-9.html
     (also included at the end of this note for convenience)

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

     https://support.oracle.com

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) 3.4 offers many significant
improvements over MEM 3.2 and MEM 3.3 and we highly recommend that you
consider upgrading. More information on MEM 3.4 is available here:

   What's New in MySQL Enterprise Monitor 3.4
   http://dev.mysql.com/doc/mysql-monitor/3.4/en/mem-comparison-3-4.html

   MySQL Enterprise Monitor
   http://www.mysql.com/products/enterprise/monitor.html

   MySQL Enterprise Monitor Frequently Asked Questions
   http://dev.mysql.com/doc/mysql-monitor/3.4/en/mem-faq.html

   MySQL Enterprise Monitor Change History
   http://dev.mysql.com/doc/relnotes/mysql-monitor/3.4/en/

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
http://www.mysql.com/trials, or contact Sales at
http://www.mysql.com/about/contact.

Useful URLs

* My Oracle Support - http://support.oracle.com/
* What's New in 3.2 - 
https://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-comparison-3-2.html
* Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/
* Installation documentation - 
http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-installing.html
* Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.2/en/
* Product information - 
http://www.mysql.com/products/enterprise/monitor.html
* FAQs - http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-faq.html
* Download - http://support.oracle.com/

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.2.9

Functionality Added or Changed

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

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

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

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

Bugs Fixed

* Validation messages were not displayed on the Settings page after a
   successful change was made.

* It was not possible to edit multiple advisors using the Edit
   Selected button.

* Clicking on the Database Availability graph, on the Overview
   dashboard, opened a blank page instead of the Events page.

* Under certain circumstances, such as filtering on many graphs on the
   All Timeseries page, the resulting graphs were not correctly
   populated with data. This was caused by the default value for the
   maxHttpHeaderSize in the Tomcat configuration file, server.xml,
   which is set too low for large quantities of data. The value is set
   to 32K by default.

   As of this release, the value of maxHttpHeaderSize is doubled, to
   64K, and applied to both the SSL and non-SSL connector
   configurations in server.xml.

   If you are upgrading to this version from a previous version, you
   must edit server.xml and add maxHttpHeaderSize="65536" to each of
   the default connectors.

   If you are performing a clean installation of MySQL Enterprise
   Service Manager, you do not need to edit any files, the new values
   are included by default.

* On Mac OS X platforms, the java_home_dir variable was not set
   properly by the installer. As a result, the configuration report
   contained the following error: ***unknown variable java_home_dir.

* On Linux, Unix, and Mac OS X platforms, the MySQL Enterprise Service
   Manager upgrade installer could not upgrade the installation if the
   installation directory contained files or directories created by a
   different user, or a user with permissions which differed from those
   of the user running the upgrade.

   As of this release, the installers check the installation directory
   to ensure all files and directories have the correct permissions. If
   they do not, it exits with an informative error message.
Thread
MySQL Enterprise Monitor 3.2.9 has been releasedandy bang22 Sep