[
https://issues.apache.org/jira/browse/DISPATCH-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112148#comment-16112148
]
Dan Langford commented on DISPATCH-195:
---------------------------------------
i wanted to leave a comment here because this page appears in google search
results regarding $coordinator and "dispatch router". (none of the qpid
dispatch docs mention $coordinator)
i was able to linkRoute $coordinator and my client was happy creating a
transacted session. except when the listener had multiTenant set to true. In
this case i found if i wanted to support transactions i could linkRoute
vhost/$coordinator and my client was satisfied
as a reminder for anybody stumbling here from a google search:
if you have multiTenant: true in your listener dispatch router will simulate
multitenancy and take the client provided HOSTNAME and DESTINATION and route
traffic to an address called HOSTNAME/DESTINATION
vhost:foo queue:bar becomes address:foo/bar
so to support multiTenant transactions (i think, at least the client is
satisfied) in a scenario where we are using multiTenant and the vhost is foo i
needed to make a linkRoute handling prefix: foo/$coordinator
> Add support for transactional messages in the Router
> ----------------------------------------------------
>
> Key: DISPATCH-195
> URL: https://issues.apache.org/jira/browse/DISPATCH-195
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Routing Engine
> Affects Versions: 0.5
> Environment: Linux
> Reporter: linuxta
> Assignee: Gordon Sim
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
