[jboss-jira] [JBoss JIRA] Commented: (JGRP-924) Shared transport: RouterStub cannot connect to 'channel_name'

[Vladimir Blagojevic (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458177#action_12458177 ] 

Vladimir Blagojevic commented on JGRP-924:
------------------------------------------

Possible solution, citing Bela:

Non shared transport:
-------------------------------
- we maintain the channel_name and local_addr in TUNNEL (inherited from TP)
- down(CONNECT) sends a CONNECT(local_addr, cluster_name) to the GR
- Every message passes the cluster name and the dest address to the RouterStub.send() method


Shared transport:
-------------------------
- the channel_name and local_addr are maintained in the TP.ProtocolAdapter (just above TUNNEL) for each separate protocol stack
- down(CONNECT): here we have the cluster name (argument of the event), but not the local_addr. We could set a ThreadLocal with the
 local_addr in TP.ProtocolAdapter, and fetch and reset it in CONNECT, so that we can send a CONNECT(local_addr, cluster_name) to the GR
- Each message passes the cluster_name and local_addr to the GR. With a shared transport, we can always get the cluster name by
 fetching the TpHeader (added by TP.ProtocolAdapter) and passing the local_addr as ThreadLocal. As an alternative, TP.ProtocolAdapter.down(Message)
 could set a ThreadLocal with local_addr and cluster_name. 

> Shared transport: RouterStub cannot connect to 'channel_name'
> -------------------------------------------------------------
>
>                 Key: JGRP-924
>                 URL: https://jira.jboss.org/jira/browse/JGRP-924
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Vladimir Blagojevic
>             Fix For: 2.8
>
>
> Channel name doesn't mean much in a shared transport. RouterStub.connect(channel_name) won't work

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira