[
https://issues.jboss.org/browse/WFLY-1553?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-1553:
-----------------------------------------------
dereed(a)redhat.com made a comment on [bug
975609|https://bugzilla.redhat.com/show_bug.cgi?id=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.
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