Bug 975609 - Infinispan subsystem ignores cluster name
Summary: Infinispan subsystem ignores cluster name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER3
: EAP 6.1.1
Assignee: Paul Ferraro
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 976849
TreeView+ depends on / blocked
 
Reported: 2013-06-18 22:34 UTC by dereed
Modified: 2018-12-02 17:06 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
: 976849 (view as bug list)
Environment:
Last Closed: 2013-09-16 20:23:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1553 0 Critical Resolved Infinispan subsystem ignores cluster name 2016-01-14 16:19:28 UTC

Description dereed 2013-06-18 22:34:31 UTC
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.

Comment 1 Paul Ferraro 2013-06-19 15:18:41 UTC
https://github.com/jbossas/jboss-eap/pull/188

Comment 2 Paul Ferraro 2013-06-19 15:21:49 UTC
https://github.com/jbossas/jboss-eap/pull/189

Comment 3 Richard Janík 2013-07-29 12:07:56 UTC
Verified.

Comment 4 Scott Mumford 2013-08-06 02:30:57 UTC
Added the Release Note skeleton.

More information is required regarding what caused the initial problem and how it was resolved (question marked placeholders above).

Comment 5 Scott Mumford 2013-08-29 00:22:39 UTC
Marking for exclusion from the 6.1.1 Release Notes document as an entry for this bug could not be completed or verified in time.


Note You need to log in before you can comment on or make changes to this bug.