I’m trying to mimic our QA environment as a QA_new. Our admin copied an image and installed it on a secondary machine. The problem with this is that the orig QA is a cluster environment and the QA_new shouldn’t be a clustered environment. I’ve removed the clustering from the IS of the QA_new and changed the tn.cluster parameters to false. However when I start up the TN in the QA_new environment, I see reference to the production IS (10.68.178.231 and .232) in the QA_new IS console:

2010-11-02 17:32:41.487 Tangosol Coherence CE 3.2.2/371 (thread=Cluster,
member=n/a): This Member(Id=4, Timestamp=2010-11-02 17:32:06.271, Address=10.68.
178.79:24547, MachineId=64591, Edition=Caching Edition, Mode=Production, CpuCoun
t=2, SocketCount=2) joined cluster with senior Member(Id=1, Timestamp=2010-10-29
12:57:31.794, Address=10.68.178.234:24547, MachineId=64746, Edition=Caching Edi
tion, Mode=Production, CpuCount=2, SocketCount=1)
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member(Id=2, Timestamp=2010-11-01 13:56:43.027, Address=10.68.178.231
:24547, MachineId=64743) joined Cluster with senior member 1
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member(Id=3, Timestamp=2010-11-01 14:41:12.444, Address=10.68.178.232
:24547, MachineId=64744) joined Cluster with senior member 1
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member 1 joined Service IS Cluster:TPT_QA_svc with senior member 1
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member 1 joined Service IS Cluster:TPT_QA:Session Store_svc with seni
or member 1
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member 1 joined Service IS Cluster:TPT_QA:Session Timeouts_svc with s
enior member 1
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member 1 joined Service IS Cluster:TPT_QA:Contexts+Keys to DataStore
IDs_svc with senior member 1
2010-11-02 17:32:41.502 Tangosol Coherence CE 3.2.2/371 (thread=Cluster, me
mber=n/a): Member 1 joined Service TNQueryResults@IS Cluster:TPT_QA_svc with sen
ior member 1

Can someone please tell me what’s the impact of this and how I stop it.

Thanks.

When you say you removed the clustering on IS of new_QA, have you restarted your IS after that?
Can you see this new_QA host on the clustering panel under cluster hosts on your production host…

Yes, I’ve restarted. No, I can’t see it on the production clustering panel. Reading up on this, I suspect it has to do with Tangosol Coherence. I think Tangosol Coherence was set up with a default distributed cache and since all the environments have the same default names residing on the same network, they’re somehow forming part of the same cluster, if that makes any sense.
Further troubleshooting, I switched off the production IS and the QA_new console reported that the “prod member” has been disconnected. Any thoughts?

tangosol coherence associate all hosts in same multicasting grp (combination of multicasting ip+port) in distributed shared cache… so as far as you removed clustering from QA_new environment … if you should be okay…

Just a thought try to create a new port and change your primary port if this same port is being used to join in cluster…

I tried creating a new port but QA_new still references the prod machine in its IS console when I query partners in TN. I noticed the same thing with the prod environment, so I guess this is how tangosol works.
Nevertheless, I found a tangosol-coherence-override.xml file in the …\config\caching folder, which made reference to multicasting. I removed the multicasting segment out and the problem seems to be gone now, QA_new no longer references prod when querying TN partners.

what happens when you disable your QA_New IS from clustering ?