[DISPATCH-195] Add support for transactional messages in the Router

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5
• Fix Version/s: 0.8.0
• Component/s: Routing Engine

Environment

Linux

• Assignee: Gordon Sim
• Reporter: linuxta
• Created: 25/Nov/15 00:55
• Updated: 20/Nov/17 18:35
• Resolved: 08/Feb/17 20:41

Description

The proton example fails with a router error:

https://github.com/apache/qpid-proton/blob/master/examples/python/tx_send.py#L41

#41 self.container.declare_transaction(self.conn, handler=self)

When the client declares a transaction at start, proton library sends out a control message that gets rejected by the router. This happens before the client sends out any regular message within the transaction.

Error Messages from router:
ERROR (error) Invalid message: Invalid body value
ERROR (error) Invalid message: Invalid body value
MESSAGE (trace) Sending Message{} on link txn-ctrl

The message format in the body of the control message is not accepted by the router. The body has a structure:

body=Described(symbol(u'amqp:declare:list'), [None])

Apparently, transactionall messages are not supported by the router.