Re: JMS Configuration for clustering

 From the documentation:


"cache.cluster.jms.node.name - A name that uniquely identifies this node 
in the cluster. This is used to prevent nodes from processing their own 
broadcast messages. Each node in the cluster must have a different 
value, for example "node1", "node2", ... ."


So yes, it needs to be set to a different value for each node in the 
cluster. If you are sharing OSCache's configuration then you'll need to 
override this property somehow for each node.

I agree that it would be nicer if OSCache didn't require this, but the 
problem is that nodes need some way to ignore their own broadcast 
messages. The easiest fix I can think of offhand is to automatically 
generate a UUID for the node name on startup, but perhaps there's a 
better approach. Any JMS experts out there know of a good solution?


Praveen Peddi wrote:

> We are currently using oscache in weblogic cluster. We are using 
> javaGroups and are planning to move to JMS.
> Our application is in the form of ear file. Oscache.properties are 
> stored in the db (due to issues with clustering).
>  
> I have seen a property called *cache.cluster.jms.node.name*
> I think I didn't quite understand what this is. Does it mean that I need 
> to include the list of server names in the cluster. Should this property 
> value be different in eash server in the cluster. If so, how could this 
> be possible. I have only one property file stored in db, shared by all 
> servers in the cluster.
>  
> For example, I have 2 servers in the cluster (server1 and server2). What 
> should this property be?
>  
> Praveen



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/