Tune messaging
To tune asynchronous messaging, we can, for example, configure message-driven bean (MDB) throttling for a JCA 1.5-compliant messaging provider. (ZOS) On z/OS platforms we can tune also MDB processing and tune destinations for the IBM MQ messaging provider.
To tune your asynchronous messaging, complete one or more of the following steps.
Tasks
- Configure MDB throttling for a JCA 1.5-compliant messaging provider in one of the following ways, depending on our choice of messaging provider:
- For the default messaging provider, complete the task Configure MDB throttling for the default messaging provider.
- For the IBM MQ messaging provider, either set the maximum server sessions property on the "IBM MQ messaging provider activation specifications advanced properties" page, or the maxPoolSize property when using the createWMQActivationSpec or modifyWMQActivationSpec wsadmin commands.
- For 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.
- Tune MDB processing on z/OS.
- Tune messaging destinations for the IBM MQ.
Subtopics
- Tune messaging performance for the default messaging provider
To help optimize performance, we can set tuning properties that control the performance of message-driven beans and other messaging applications.- Configure MDB throttling for the default messaging provider
Configure the throttling of messages for message-driven bean that we have deployed as JCA 1.5 resources on the default messaging provider.- Tune messaging destinations for the IBM MQ messaging provider
We can optimize performance of message-driven bean (MDB) or other applications that use the IBM MQ messaging provider by configuring the properties of IBM MQ messaging provider destinations.- Tune message-driven bean processing on z/OS using IBM MQ as the messaging provider in ASF mode
We can tune message-driven beans processing when we are running WAS on the z/OS platform, where IBM MQ is the messaging provider, and the message-driven bean has been deployed in Application Server Facilities (ASF) mode.- Throttling inbound message flow for JCA 1.5 message-driven beans
This topic describes how to throttle message delivery for message-driven beans (MDB) which are deployed as message endpoints for Java EE Connector Architecture (JCA) Version 1.5 inbound resource adapters.- Monitor server session pools for listener ports
We can minimize the number of resources that server sessions use by enabling server session pool monitoring and defining the timeout value to be applied to a server session.
Configure an activation specification for the IBM MQ messaging provider IBM MQ messaging provider activation specification advanced properties createWMQActivationSpec command modifyWMQActivationSpec command