qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "linuxta (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DISPATCH-195) Router does not support transactional messages
Date Wed, 25 Nov 2015 00:55:10 GMT
linuxta created DISPATCH-195:

             Summary: Router does not support transactional messages
                 Key: DISPATCH-195
                 URL: https://issues.apache.org/jira/browse/DISPATCH-195
             Project: Qpid Dispatch
          Issue Type: Bug
          Components: Routing Engine
    Affects Versions: 0.5
         Environment: Linux
            Reporter: linuxta

The proton example fails with a router error:


#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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message