[jboss-jira] [JBoss JIRA] (WFLY-1553) Infinispan subsystem ignores cluster name
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Fri Jun 21 12:07:21 EDT 2013
[ https://issues.jboss.org/browse/WFLY-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783667#comment-12783667 ]
RH Bugzilla Integration commented on WFLY-1553:
-----------------------------------------------
Jonathan Mason <jmason at redhat.com> made a comment on [bug 976849|https://bugzilla.redhat.com/show_bug.cgi?id=976849]
+++ This bug was initially created as a clone of Bug #975609 +++
Description of problem:
The Infinispan subsystem uses the name of the cache container as the cluster name, instead of the name configured in <transport cluster="foo"/>.
Version-Release number of selected component (if applicable):
EAP 6.1.
This is a regression in 6.1. Does not affect 6.0.x.
How reproducible:
Always
Steps to Reproduce:
1. Configure the "web" cache with <transport cluster="foo"/>.
2. Deploy a <distributable/> web application.
3. Note the cluster name printed in the log:
GMS: address=master:server-one/foo, cluster=web, physical address=127.0.0.1:7600
Actual results: The cluster is still "web".
Expected results: The cluster is "foo".
Additional info:
This is a critical issue when using a gossip router, as only the cluster name determines what nodes form a cluster.
--- Additional comment from Paul Ferraro on 2013-06-19 11:18:41 EDT ---
https://github.com/jbossas/jboss-eap/pull/188
--- Additional comment from Paul Ferraro on 2013-06-19 11:21:49 EDT ---
https://github.com/jbossas/jboss-eap/pull/189
> Infinispan subsystem ignores cluster name
> -----------------------------------------
>
> Key: WFLY-1553
> URL: https://issues.jboss.org/browse/WFLY-1553
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha1
> Reporter: Dennis Reed
> Assignee: Paul Ferraro
> Priority: Critical
>
> The Infinispan subsystem uses the name of the cache container as the cluster name, instead of the name configured in <transport cluster="foo"/>.
> This is a critical issue when using a gossip router, as only the cluster name determines what nodes form a cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list