WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring MDB throttling on the default messaging provider

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

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

The default messaging provider (the SIB JMS Resource Adapter) uses a special type of message throttling. You should use the throttling support described in this topic instead of the JCA 1.5 throttling of messages described in Throttling of inbound message flow for JCA 1.5 message-driven beans. You 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 a configuration option on the JMS activation specification used to deploy the bean. This configuration option is labelled Maximum concurrent endpoints and can be found on the JMS activation specification panels in the administrative console.

To configure the message throttling support of the default messaging provider (the SIB JMS Resource Adapter), use the administrative console to complete the following steps.

Related information
JMS activation specification collection
JMS activation specification settings

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0027_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)