users@glassfish.java.net

Re: Easiest way to distribute JMS messages in a Glassfish ...

From: <forums_at_java.net>
Date: Sun, 17 Mar 2013 14:28:15 -0500 (CDT)

Assuming you are using default configuration and your MDB is deployed to a
GlassFish cluster, 1. The distribution of produced messages among the MQ
broker instances in the cluster depends on how evenly the loadbalancer's
directing HTTP requests to all GlassFish instances. By default, a JMS
connection factory is configured to generate a connection with priority to
the broker instance that is associated the GlassFish instance that the
application component is running in; 2. Regardless #1, a MDB is able to
consume messages from all MQ broker instances in the cluster assuming the
destination is not configured with isLocalOnly or
localDeliveryPreferred(Queues); 3. The distribution of messages consumed in
each GlassFish instance by the MDB is affected by prefetch limit and other
factors like relative processing speed in GlassFish instances. The default
prefetch for Queues is 1000 and Topics in cluster is 5. On client side, you
can change the prefetch by setting connection factory property
imqConsumerFlowLimit.

--
[Message sent by forum member 'amyk']
View Post: http://forums.java.net/node/895533