[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1627) JBM JGroups groupname is null for both channels. The groupname can't be changed from null-CTRL and null-DATA

[Jay Howell (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12467666#action_12467666 ] 

Jay Howell commented on JBMESSAGING-1627:
-----------------------------------------

Any way we could have this done in the next week.  We have some customers that are trying to isolate their cluster and need to be able to change the groupname.



> JBM JGroups groupname is null for both channels.  The groupname can't be changed from null-CTRL and null-DATA
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1627
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1627
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions:  1.4.0.SP3.CP04, 1.4.0.SP3.CP07
>         Environment: 1.4.0.SP3-CP04
>            Reporter: Jay Howell
>            Assignee: Tim Fox
>
> The groupname for both the control and datachannel are set to null.  "null-CTRL" and "null-DATA".  
> Here's the probe information(you can see channels 4 and 6, the groups are null).  This was reproducable in EAP 4.3CP03 and in 4.3CP04.  This probe came from CP04.
> #1 (249 bytes): 127.0.0.1:43725 (DefaultPartition) 
> local_addr=127.0.0.1:43725
> group_name=DefaultPartition
> version=2.4.5.GA, cvs="$Id: Version.java,v 1.42.2.11 2009/01/09 05:37:36 jiwils Exp $"
> view: [127.0.0.1:43725|0] [127.0.0.1:43725]
> group_addr=228.1.2.3:45566
> #2 (269 bytes): 127.0.0.1:57444 (DefaultPartition-SFSBCache) 
> local_addr=127.0.0.1:57444
> group_name=DefaultPartition-SFSBCache
> version=2.4.5.GA, cvs="$Id: Version.java,v 1.42.2.11 2009/01/09 05:37:36 jiwils Exp $"
> view: [127.0.0.1:57444|0] [127.0.0.1:57444]
> group_addr=229.1.2.3:45551
> #3 (245 bytes): 127.0.0.1:50408 (Tomcat-Cluster) 
> local_addr=127.0.0.1:50408
> group_name=Tomcat-Cluster
> version=2.4.5.GA, cvs="$Id: Version.java,v 1.42.2.11 2009/01/09 05:37:36 jiwils Exp $"
> view: [127.0.0.1:50408|0] [127.0.0.1:50408]
> group_addr=230.1.2.7:45577
> #4 (308 bytes): 127.0.0.1:7900 (null-DATA) 
> local_addr=127.0.0.1:7900
> group_name=null-DATA
> version=2.4.5.GA, cvs="$Id: Version.java,v 1.42.2.11 2009/01/09 05:37:36 jiwils Exp $"
> view: [127.0.0.1:7900|0] [127.0.0.1:7900]
> connections: connections (1):
> key: 127.0.0.1:7900: <127.0.0.1:52926 --> 127.0.0.1:7900> (20 secs old)
> #5 (273 bytes): 127.0.0.1:35607 (DefaultPartition-EntityCache) 
> local_addr=127.0.0.1:35607
> group_name=DefaultPartition-EntityCache
> version=2.4.5.GA, cvs="$Id: Version.java,v 1.42.2.11 2009/01/09 05:37:36 jiwils Exp $"
> view: [127.0.0.1:35607|0] [127.0.0.1:35607]
> group_addr=230.1.2.3:43333
> #6 (235 bytes): 127.0.0.1:52970 (null-CTRL) 
> local_addr=127.0.0.1:52970
> group_name=null-CTRL
> version=2.4.5.GA, cvs="$Id: Version.java,v 1.42.2.11 2009/01/09 05:37:36 jiwils Exp $"
> view: [127.0.0.1:52970|0] [127.0.0.1:52970]
> group_addr=228.7.7.7:45568

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