Network Deployment (Distributed operating systems), v8.0 > Tune performance > Tune Service integration


Configure MDB throttling for the default messaging provider

Use this task to configure the throttling of messages for message-driven beans that we have deployed as JCA 1.5 resources on the default messaging provider.

The throttling support described in this topic only applies to the default messaging provider (the service integration JMS Resource Adapter).

For the WebSphere MQ messaging provider, you configure message throttling by setting the maximum server sessions property on the WebSphere MQ messaging provider activation specifications panel, or the maxPoolSize property when using the createWMQActivationSpec or modifyWMQActivationSpec wsadmin commands.

If we have a third-party JCA 1.5-compliant JMS messaging provider, refer to the generic method of message throttling described in Throttling inbound message flow for JCA 1.5 message-driven beans.

Use this task to throttle messages for a message-driven bean deployed as a J2EE Connector Architecture (JCA) 1.5 resource on the default messaging JMS provider.

The default messaging provider (the service integration JMS Resource Adapter) uses a special type of message throttling. We can leave the message-driven bean pools to the default size of 500.

The default messaging provider enables the throttling of message delivery to a message-driven bean through the Maximum concurrent endpoints configuration option on the JMS activation specification used to deploy the bean.

You might want to tune the throttling of your message-driven beans, which is especially important on z/OS. Workload arriving on the destination the message-driven bean is consuming from might use up more server resource and therefore obstruct other activities. An example of this is when restarting MDB applications you find a backlog of messages. The number of messages can be throttled so that the message-driven bean can process them in the most efficient manner.

To configure the message throttling support of the default messaging provider (the service integration bus JMS Resource Adapter), use the admin console to complete the following steps.


Procedure


Workload sharing with queue destinations
Tune messaging performance with service integration technologies
JMS activation specification [Settings]