[ 
https://issues.apache.org/jira/browse/DISPATCH-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278792#comment-16278792
 ] 

Ted Ross commented on DISPATCH-890:
-----------------------------------

On first attempt, I am unable to reproduce this symptom.  It appears to work 
correctly for me.


> Multi tenancy doesn't work over a websockets listener
> -----------------------------------------------------
>
>                 Key: DISPATCH-890
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-890
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Container
>    Affects Versions: 1.0.0
>            Reporter: Ernest Allen
>            Assignee: Ted Ross
>             Fix For: 1.1.0
>
>
> When a listener has http: true and multiTenant: true, the connection isn't 
> multi-tenant
> - add bob.com to /etc/hosts and map to 127.0.0.1
> - setup listeners like:
> listener {
>     host: bob.com
>     port: 5674
>     multiTenant: true
>     http: true
>     saslMechanisms: ANONYMOUS
> }
> listener {
>     host: 0.0.0.0
>     port: 5672
>     role: normal
>     saslMechanisms: ANONYMOUS
> }
> - serve the stand-alone console from http://bob.com:5674/
> - The console will connect to the router via bob.com:5674 
> - qdstat -c     or just use the console's Entities tab and look at the 
> connections
> In theory, there should be a connection that has a tenant of bob.com, but 
> there isn't.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to