Network Deployment (Distributed operating systems), v8.0 > Tune performance > Tune Messaging resources > Tune messaging

Throttling inbound message flow for JCA 1.5 message-driven beans


Message-driven beans (MDB) are deployed as message endpoints for Java EE Connector Architecture (JCA) Version 1.5 inbound resource adapters. The throttling of messages as described in this topic does not apply to the two JCA 1.5-compliant messaging providers that are supplied with WAS:

For the default messaging provider, configure message throttling as described below.

For the WebSphere MQ messaging provider, throttle messages by...

If we have a third-party JCA 1.5-compliant JMS messaging provider, check with your supplier to see whether the method of message throttling described in this topic is appropriate for their messaging provider.

For installations that use resource adapters that implement the Java EE Connector Architecture (JCA) Version 1.5 message delivery support, the WAS provides message throttling support to control the delivery of messages to endpoint message-driven beans (MDB). We can use this support to avoid overloading the server with a flood of inbound messages.

Message delivery is throttled on a message-driven bean basis by limiting the maximum number of endpoint instances that can be created by the adapter that the MDB is bound to. When the adapter attempts to create an endpoint instance, a proxy for the MDB instance is created and returned as allowed by the JCA 1.5 architecture. There is a one-to-one correspondence between proxies and MDB instances, and like the MDB instances, the proxies are pooled based on the minimum and maximum pool size values associated with the message-driven bean. Throttling is performed through the management of the proxy pool.

At the time the adapter attempts to create an endpoint, if the number of endpoint proxies currently created is equal to the maximum size of the pool, adapter createEndPoint processing returns an Unavailable Exception. When this displays, the adapter does not issue any more createEndPoint() requests until it has released at least one endpoint back to the server for reuse. Thus, installations can control the throttling of message delivery to a JCA 1.5 MDB based on the setting of the maximum size of the pool associated with each JCA 1.5 message-driven bean.

We can specify the pool size by using the JVM system property to define the minimum and maximum pool size of stateless, message-driven, and entity beans. For a message-driven bean that supports JCA 1.5, the maximum pool size value specified limits how many message endpoint instances can be created for that message-driven bean. For example, if the installation sets the maximum size of a JCA 1.5 MDB pool to 5, then at most 5 messages can be concurrently delivered to 5 instances of the message-driven bean. This property can be specified using the wsadmin scripting tool or by specifying it under the admin console as an environmental variable.


  1. Open the admin console.

  2. Select Servers > Server Types > WebSphere application server > server_name

  3. Under Server Infrastructure, expand Java and Process Management >Process Definition.

  4. Under Additional Properties, select Java Virtual Machine.

  5. Under Additional Properties, select Custom Properties.

  6. Select New. A panel with three General Properties fields displays. This is where you set the property.

  7. In the Name field, enter

  8. To complete the Value field, see the EJB container system properties for values.

  9. After defining the value of the property, click OK. You are now prompted to save the changes we have made.

  10. Click Save.

Tune messaging
WebSphere MQ messaging provider activation specification advanced properties
Configure MDB throttling for the default messaging provider



Search Tips   |   Advanced Search