.. _section-index24143:

***********************************
Upgrading from 2.4.14.2 to 2.4.14.3
***********************************

See :ref:`section-Install-Upgrade`, if you haven't already.

The following sections describe how to upgrade from |me| 2.4.14.2 to |me| 2.4.14.3.
They describe general, wire, and other compatibility issues between |me| 2.4.14.3
and previous releases.

.. attention::

  For important information on new and removed platforms and features in |me|
  2.4.14.3, see `Supported Platforms and Programming Languages
  <https://community.rti.com/static/documentation/connext-micro/2.4.14.3/doc/html/release/supported_platforms.html>`__
  and `What's New in 2.4.14.3
  <https://community.rti.com/static/documentation/connext-micro/2.4.14.3/doc/html/release/whats_new_24143.html>`__
  in the |me| documentation.

See `RTI Connext Performance Benchmarks
<https://community.rti.com/static/documentation/performance/benchmarks/index.html>`__
for performance details in this release.

API Compatibility
-----------------

|me| 2.4.14.3 supports data fragmentation for best-effort reliability, and uses
the maximum serialized sample size to determine if serialization is required.
Fragmentation is automatically enabled if the maximum serialization size plus
the RTPS overhead is larger than the UDP ``max_message_size``.

If your application uses reliable reliability and the total of maximum sample
size plus RTPS overhead is larger then the UDP ``max_message_size``, entity
creation will fail. When migrating your application to 2.4.14.3, make sure that
you set UDP ``max_message_size`` correctly.