You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2017/02/08 20:41:41 UTC

[jira] [Resolved] (DISPATCH-195) Router does not support transactional messages

     [ https://issues.apache.org/jira/browse/DISPATCH-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim resolved DISPATCH-195.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.8.0

> 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
>             Fix For: 0.8.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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