Tips: How to configure a Cluster of JMS Messaging on Jboss 5.1.0
Last week I lost a lot of time to obtain a perfect Jboss AS Cluster with JMS Messaging, now I am writing here some tips in order to avoid other wast time in the future 
To configure a cluster of Jboss it’s very easy, but for having a right JMS Messaging configuration could be too difficult.
For example, in my case I configured a jboss cluster, with two node (A & B) but just one node at time read the messages from the queue. It was an active-passive cluster. I would a real active-active cluster with load balacing policy.
First of all you need to configure at least 2 nodes starting from “all” configuration (e.g. nodeA & nodeB).
In this example I am going to explain how to configure the JMS messaging with a Oracle persistence.
A possible Concurrency Producer and Consumer pattern
Often I discuss about concurrency problems and how to design applications that involved Producer and Consumer actors.
Thanks to my RSS feed I found an interesting article to discuss three different approach to read – process- update massive data.
The problem is:
- Load data based on Database based on groups
- Process the data
- Update the records loaded in step 1 with modifications
