Product: Confluence
Environment
| Operating System | |
|---|---|
| Affect Version/s | 2.5.2 |
| JVM | |
| Database | Oracle 9.x |
| Application Server | Weblogic 8.x |
Error Message
2007-09-18 14:20:50,750 ERROR [Logger@17450849 3.2/365 (RC3)] [Coherence] log 2007-09-18 14:20:50.749 Tangosol Coherence AE 3.2/365 (RC3) <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "beki0_cluster" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use overlapping network configurations.
Symptom
Cannot get a Confluence cluster run on a machine. The above error appears when trying to give a cluster name.
Diagnostics/Test
Running 2 confluence clusters on the same machine, so the unicast IP address/port goes in conflict.
Root Cause
Cannot run two Confluence clusters on one machine. This feature is not currently supported.
Solution
Created a new bug report in Jira:
http://jira.atlassian.com/browse/CONF-9525
addressing this problem.