Chapter 4. Known issues
4.1. AMQ C++
ENTMQCL-693 - Cannot send message properties with null values
The library throws a
conversion_errorif a null value is decoded into aproton::scalar. This occurs when decoding application properties that contain null values.
4.2. AMQ Python
ENTMQCL-483 - Selectors with backslashes are invalid in non-Unicode strings
The
Selectoroption onContainer.create_receiver()accepts a string. If the string is not supplied as Unicode (in Python 2,u"somestring"), any elements escaped with backslashes might not be processed correctly.Workaround: Users of Python 2 should use an explicit Unicode string in filter declarations to avoid the problem.
ENTMQCL-546 - Transactions introduce unexpected link events
Starting a transaction internally opens a sending link for controlling the transaction. This special link can trigger extra application events.
Workaround: Code using transactions should ensure link handler functions are processing the link they expect.
4.3. AMQ .NET
ENTMQCL-794 - Transactions do not work with .NET Core
Rolling back transactions when using AMQ .NET on .NET Core is not working as expected.
Workaround: Use .NET Framework 4.5 instead of .NET Core if you require transactions.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.