"schrouf" wrote : I decided to deploy the MDB's on one node. The plan was then
to remove most of the logic out of the MDB into SLSB which are load balanced
across the cluster.
|
|
| Ok, what about the following two-step approch:
|
| The MDB with a durable subscription to your JMS to
anonymous wrote :
| Why do you restrict the MDB's to one node ?
|
| Deploying them on ALL the same nodes as your SLSB and delegation to a local
SLBS from within onMessage() would also loadbalance your message processing !
|
The MDB's are restricted to one node because they listen to a
Thanks for the help.
I was already specifying the providerUrl="localhost:1100" to connect to HAJNDI
but didn't know about changing the 'CallByValue' to 'true' to stop JNDI always
connecting to the local JVM object.
I followed the instructions in the javadoc and changed the naming service
attri
Hi,
I'm having difficulty with load balancing SLSB on a cluster of 2 nodes running
JBoss 4.01sp1 (I had the same issue with 3.2.7, upgraded to latest version to
see if it was a fixed issue).
The SLSB is configured to do round robin load balancing and is deployed on 2
nodes.
I've also got HAJM
