Disabling Clustering in Jboss Application Server

[craig2007]

Hi
I am using jboss-4.0.4.GA for JBoss Messaging.
If any other server is started ,it automatically joins the cluster environment.
I want to disable the joing of new server with my server( Server on which JBoss Messaging is running).
Please tell me a way to disable to cluster participation of JBoss App Servers.

I have pasted the log which i get when another Jboss Server pariciaptes the cluster

14:00:47,626 INFO [DefaultPartition] Suspected member: ABC044690:2301 (additional data: 19 bytes)
14:00:47,626 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 39, delta: -1) : [192.168.251.101:1099]
14:00:47,658 INFO [DefaultPartition] I am (192.168.251.101:1099) received membershipChanged event:
14:00:47,658 INFO [DefaultPartition] Dead members: 1 ([192.168.251.36:1099])
14:00:47,658 INFO [DefaultPartition] New Members : 0 ([])
14:00:47,658 INFO [DefaultPartition] All Members : 1 ([192.168.251.101:1099])
14:03:17,706 INFO [DefaultPartition] New cluster view for partition DefaultPartition: 40 ([192.168.251.36:1099, 192.168.251.101:1099] delta: 1)
14:03:17,706 ERROR [NAKACK] sender at index 1 in digest is null
14:03:17,738 INFO [DefaultPartition] Merging partitions...
14:03:17,738 INFO [DefaultPartition] Dead members: 0


Please do reply me back

[peterj]

Use the 'default' configuration instead of the 'all' configuration.

[craig2007]

Is there any other way i can implement that functionality (Disabling clustering across JBoss Application Server)
Any configuration needs to be done ???

For Jboss Messaging , i am using the following command to start the server

run -c messaging

i am not passing any command line parameter like "default" or "all" to "run" batch command

[visolvejboss]

Hello,

Assume that, you have created "Messaging" server configuration from "all" server configuration which contains clustering option. To prevent from joining other cluster nodes from "Messaging" configuration do any one of the following option.

1. Copy "Default" server configuration as "Messaging" Server configuration and do the needed changes for Messaging and run the server. It won't produce cluster problem.

(or)

2. Keep your "Messaging" Server configuration as such and start the JBoss AS as follows. This might solve your problem.

run.sh -c messaging -g server1 -u 228.1.2.3

For more information refer http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016181#4016181