Skip to main content

Configuring Generic JMS RA for inbound load balancing

Posted by rampsarathy on January 9, 2007 at 4:03 AM PST

Configuring Generic JMS RA for inbound load balancing.

In the last blog we saw how MantaRay peer to peer advantage can be
leveraged by applications (using JMS) in GlassFish. One issue that was
presented there was duplication of message processing by GlassFish
clustered instances when consuming messages from a topic destination.
Ideal production requirements can  be met, if one and only one
cluster instance in GlassFish was allowed to process the message, and
even better if this is achieved without any code changes to the

This can be achieved by performing few configuration changes to Generic
JMS Resource Adapter and the application deployment descriptor.

The following link href="">
shows how mutual exclusive message delivery to cluster instances
can be achieved using generic jms ra.

Briefly the following activation configuration properties need to be
added to the sun-ejb-jar.xml (sun specific deployment descriptor for
the MDB).


<activation-config-property-name> style="color: rgb(51, 204, 0);">InstanceCount</activation-config-property-name>

<activation-config-property-value> style="color: rgb(51, 204, 0);">3</activation-config-property-value>



<activation-config-property-name> style="color: rgb(51, 204, 0);">LoadBalancingRequired</activation-config-property-name>

<activation-config-property-value> style="color: rgb(51, 204, 0);">true</activation-config-property-value>


InstanceCount indicates the number of instances in the cluster and the
LoadBalancingRequired flag indicates that generic ra needs to guarantee
mutual exclusive message delivery to topic subscribers.

Redeploy the application after making the above change to the
deployment descriptor.

The following changes would also be required to the instances in the

JVM properties need to be set for each instance in the cluster :

To add JVM property to an instance , Login to the admin console,

Properties and add the following property for each instance.

For instance 1

For instance 2:

For instance 3:

Restart the cluster (or node agent) after making the above change

Execute the Client programs (samples) now and you would notice that the
messages will be processed by only one of the 3 instances in the

For mode advanced selector configurations , please refer href="">

Related Topics >>