10-4 Programming Message-Driven Beans for Oracle WebLogic Server
subscription-durability to Durable. Alternatively, when using
annotations, specify an ActivationConfigProperty with propertyName = subscriptionDurability
and propertyValue = Durable.
10.2.3 Setting Automatic Deletion of Durable Subscriptions
You can configure an MDB to automatically delete a durable topic subscription when the MDB is undeployed or deleted from a server. To configure an MDB to
automatically delete durable topic subscriptions, set durable-subscription-deletion
to True. By default, durable-subscription-deletion
is set to False
10.2.4 Setting Container Managed Transactions
See Section 6.2, Configuring Transaction Management Strategy for an MDB.
10.2.5 Setting Message Filtering JMS Selectors
JMS provides an SQL-like syntax for filtering messages based on standard JMS message header fields and message properties. In addition, WebLogic JMS supports an
extension to the selector syntax that allows the specification of selectors that include XML xpath expressions for filtering XML messages based on their XML contents.
One way to specify a message selector is to specify it as the propertyValue for an ActivationConfigProperty
with propertyName = messageSelector. The syntax of JMS selectors is fully described in the Javadoc for the
javax.jms.Message class. The WebLogic xpath selector extension syntax is
described in Filtering Messages in Programming JMS for Oracle WebLogic Server.
10.2.6 Controlling MDB Concurrency
As discussed in Appendix A, Topic Deployment Scenarios,
, an MDB deployment may create one or more MDB free pools. The max-beans-in-free-pool and
dispatch-policy descriptor attributes work together to control MDB thread
concurrency in an MDB free pool as follows:
■
For a discussion of how to determine the number of concurrent MDBs, see Determining the Number of Concurrent MDBs in Performance and Tuning for
Oracle WebLogic Server.
■
When an MDB topicMessagesDistributionMode is set to Compatibility and the MDB uses container-managed transactions, concurrent MDB invocations
are prevented. In addition, max-beans-in-free-pool should be explicitly set to 1 for bean-managed transaction MDBs that are driven by a foreign
non-WebLogic topic.
Configuring and Deploying MDBs Using JMS Topics 10-5
See Tuning Message-Driven Beans in Performance and Tuning for Oracle WebLogic Server for more information.
10.2.7 Setting Subscription Identifiers
