Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Clustering configuration for topic

 
ravikanth reddy
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

We are working on jboss-4.2.3GA with clustering.
We have two application serveres each with two different nodes hosted in different machines.

ClusterA server is running with 2instances in partitionA
ClusterB server is running with 2instances in partitionB.

Both the servers are using jboss-messaging.
Post office, all the queues and Topics are clustered.

We have a Topic hosted in ClusterA, and we have 3 consumeres in ClusterB.
We have hosted MessageBridge in clusterB.
In non clustered environment when message comes to the Topic, 3 consumers used to consume the message and used to process without any problems.

But In clustered environment when message comes to the topic in ClusterA both the nodes in ClusterB environment or consuming and processing it is leading to the problems.

Messaging failover, load balancing everything is working fine with queues. We have problem only with the Topics.





Could some one please let me know why ClusterB both the nodes are consuming the message.

Is there any other configuration missed for messaging clustring?


 
ravikanth reddy
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How to configure durable Topic. We read some of the posts, with durable topic this problem not occurs. Could some one shade some light, how to create a durable Topic. Is there any configuration in destination-service.xml?
 
ravikanth reddy
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For my queues I can see an entry in jbm_postoffice table with Clustered = 'Y' but for Topic there is no entry in jbm_postoffice but all my Topics are assigned to Postoffice as like queue.
 
ravikanth reddy
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Problem is resolved .

In ClusterB, 3 consumers had unique client id <mdb-client-id>. we created different client-id for all the consumeres. It is working filne.

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic