Bug 975609
| Summary: | Infinispan subsystem ignores cluster name | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | dereed | |
| Component: | Clustering | Assignee: | Paul Ferraro <paul.ferraro> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.1.0 | CC: | cdewolf, istudens, paul.ferraro, rdickens, rjanik, smumford | |
| Target Milestone: | ER3 | |||
| Target Release: | EAP 6.1.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause:
???
Consequence:
The Infinispan subsystem ignored the configured cluster name and used the name of the cache container instead.
Fix:
???
Result:
Infinispan now honors the configured cluster name.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 976849 (view as bug list) | Environment: | ||
| Last Closed: | 2013-09-16 20:23:00 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 976849 | |||
Verified. Added the Release Note skeleton. More information is required regarding what caused the initial problem and how it was resolved (question marked placeholders above). 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. |
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.