Chapter 4. Known Issues

ENTMQCL-604 - Receiver name is not set when using the container.create_receiver() method

Due to a flaw in the option processing of the container.create_receiver() method, the receiver name is not set when using the name option.

Workaround: Set the receiver name using the name option on the connection.create_receiver() method instead of on the container.create_receiver() method.

ENTMQCL-483 - Selectors with backslashes are invalid in non-Unicode strings

The Selector option on Container.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.

ENTMQCL-690 - Container.schedule() fails if called from an event handler

The Container.schedule() method will have no effect if it is called from inside a MessagingHandler callback function.

Workaround: Call schedule() from outside the MessagingHandler callback functions.