Other
=====

.. Release Notes from this point.

:major:`[Major]` Possible race condition with Zero Copy shared memory API
-------------------------------------------------------------------------
A race condition could occur if you accessed the Zero Copy shared
memory API before initialization had been completed.


[RTI Issue ID MICRO-10019]

:major:`[Major]` DataWriter with finite timestamp failed to send data if date exceeded January 2038
---------------------------------------------------------------------------------------------------
A *DataWriter* configured with a finite source timestamp tolerance and
``DDS_BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS`` would fail to send data
after 03:14:07 UTC 19 January 2038.


[RTI Issue ID MICRO-5858]

:major:`[Major]` |me_h| would not work if year exceeded 2038
------------------------------------------------------------
If the date was set beyond the year 2038, |me| would not
work. This was because the date was reported as a 32-bit unsigned
integer; however, |me| expected a signed 32-bit value and
would therefore interpret the “wrap around” value as a negative number,
causing an error.


[RTI Issue ID MICRO-2295]

:minor:`[Minor]` Multiple endpoints did not match properly when using Zero Copy transfer
----------------------------------------------------------------------------------------
When using the Zero Copy v2 transport, multiple endpoints would not
match properly if both *DomainParticipants* were enabled before creating
*DataReaders* or *DataWriters.*


[RTI Issue ID MICRO-10162]

:minor:`[Minor]` SYSTEM_RESOURCE_LIMITS.max_components QoS setting documented incorrectly
-----------------------------------------------------------------------------------------
|me| documentation incorrectly stated that the
``SYSTEM_RESOURCE_LIMITS.max_components`` QoS setting could be changed.
This has been corrected to state that it cannot be changed. The default
value has also been increased to 64.


[RTI Issue ID MICRO-3571]

:trivial:`[Trivial]` DDS_Wstring_cmp did not match the implementation name DDS_Wstring_compare
----------------------------------------------------------------------------------------------
The DDS Wstring compare function was incorrectly documented as being
``DDS_Wstring_cmp`` instead of ``DDS_Wstring_compare``.


[RTI Issue ID MICRO-3529]