How to Stop Clustering on same Network in jBoss 6.1?

[shailendra.soni]

Hi,

I have created my own node/instance from “all” node in Jboss 6.1 server. Now I have copied this server on different machine which are on same network. Now when I am trying to start  node on all these systems , log shows clustering warning/error.

So my question is that how to stop clustering in such type of scenario?

Thanks and Regards,

Shailendra Soni

[wdfink]

Does http://community.jboss.org/wiki/TwoClustersontheSameNetwork helps?

The easiest way is to start each instance with different values for

run.sh -p <a partition name> -u <a multicast address> -m <a multicast port> ....

BTW why you start the 'all' configuration if you don't wan't to have a cluster, in this case use the 'default' configuration.

[shailendra.soni]

Good Question. Problem is different of mine. We have two production solaris servers where we were planned to do clustering but at last moment there was issue installing Apache on both the productions solaris servers. Now , that was plan to do clusting on production and same configuration was successfully on our development and QA enviorments. So at deploy as it is on production servers.

[wdfink]

For me it is still unclear what you want to achieve.

Do you start with '-p -u -m' options and separate your instances?

[rhusar]

If I understand correctly, the problem is that for the quality assurance team they use the same production profile for testing. However multicast messages get from the production environment to the QA one. This is exactly what Wolf's recommendations solve (eg. use different multicast group with -u).

[shailendra.soni]

You are right Radoslav, Problem is solved suggected by Wolf. Thanks to all.

[wdfink]

Great to hear

But you should mark your thread as answerd as well to give a hint in the summary list for other people which looks for an answer or event to help