Burton Wynne

Jeremiah Orr wrote:I'm not familiar with the JBoss environment, but I don't think the cluster has anything to do with how the topic works. When using a topic, any subscriber will receive the message, regardless of location. This is the case whether you're working with a cluster or with multiple subscribers in completely different environments.

I wonder if a queue is what you're looking for, though it won't help you if you want multiple MDBs in the same node to get the message. If that's what you need (many subscribers in a node, but only one node in the cluster should get a given message), then you might just want to have a topic for each node.

I guess I should be more specific. I have multiple mdbs deployed that subscribe to the topic (lets just say A,B,C). I want all of the different mdbs to be called but not the same mdb to be called across servers. When a new message is added to the topic I want A,B,C to be called. I just only want one instance of A,B and C to processed such that only A.x, B.y and C.z are called where x,y and z lie within the bounds of {1-n} and where n is the number of servers.

Thanks for the response...

I have deployed a jee application to a JBoss 4.2 cluster. The application basically adds messages to a topic. mdbs(ejb 3.0) then subscribe to the topic and process the messages. I am using ha-jms( port 1100 ) on JBoss AS. Right now when it appears that the mdbs that I wrote are being called on both members of the cluster (currently there are only two members of the cluster). Is this the correct behavior for the mdbs? Should the all of the mdbs on all of the clusters receive the message from the cluster or should only the mdbs on one node of the cluster act on the message.

The desired behavior that we want is to only have one node's mdbs. Is this a misconfiguration problem or an architectural issue?

Thanks in Advance!