Table 20–3 shows the configurable properties of the ActivationSpec JavaBean. These properties are used by the application server when instructing the Resource Adapter to activate a message endpoint and associate it with a message-driven bean.
Table 20–3 ActivationSpec Properties
Property |
Type |
Default Value |
Description |
||
---|---|---|---|---|---|
addressList [Optional] , [Property specific to Message Queue JMS Resource Adapter] |
String |
Inherited from ResourceAdapter JavaBean |
Message service address for connecting to Message Queue service |
||
destination [Standard Enterprise JavaBean (EJB) and J2EE Connector Architecture (CA) property] |
String |
None |
Name of destination from which to consume messages The value must be that of the destinationName property for a Message Queue destination administered object. |
||
String |
None |
Type of destination specified by destination property: javax.jms.Queue: Queue destination javax.jms.Topic: Topic destination |
|||
String |
None |
Message selector for filtering messages delivered to consumer |
|||
String |
None |
Name for durable subscriptions This property must be set if subscriptionDurability is set to Durable. |
|||
String |
NonDurable |
Durability of consumer for topic destination: Durable: Durable consumer NonDurable: Nondurable consumer This property is valid only if destinationType is set to javax.jms.Topic, and is optional for nondurable subscriptions and required for durable ones. If set to Durable, the clientID and subscriptionName properties must also be set. |
|||
String |
None |
Client ID for connections to Message Queue service This property must be set if subscriptionDurability is set to Durable. |
|||
String |
Auto-acknowledge |
Acknowledgment mode: Auto-acknowledge: Auto-acknowledge mode Dups-ok-acknowledge: Dups-OK-acknowledge mode |
|||
String |
None |
Acknowledgment mode for MDB message consumption Valid values are No_acknowledge or null. You can use no-acknowledge mode only for a nontransacted, nondurable topic subscription; if you use this setting with a transacted subscription or a durable subscription, subscription activation will fail. |
|||
Integer |
6 |
Number of times to redeliver a message when MDB throws an exception during message delivery |
|||
Boolean |
true |
Place message in dead message queue when MDB throws a runtime exception and number of redelivery attempts exceeds the value of endpointExceptionRedeliveryAttempts? If false, the Message Queue broker will attempt redelivery of the message to any valid consumer, including the same MDB. |
|||
String |
None |
A list of additional connection factory properties to be used when creating connections to a Message Queue broker. When specified, the value of options must be a comma-separated list of connection factory properties and their values, in the form:
If value contains a comma or an equals sign, precede the symbol with a backslash (\) or enclose the entire value in quotes; for example:
The options property cannot be used to specify properties that are configured internally or that have their own setter methods, specifically: imqReconnectEnabled, imqReconnectAttempts, imqReconnectInterval, imqDefaultUsername, imqDefaultPassword, imqAddressList, imqAddressListIterations. Any values specified in options for these properties are ignored. |
|||
Boolean |
true |
Controls whether topic subscriptions created using this ActivationSpec will be shared when running in a clustered container, as described in About Shared Topic Subscriptions for Clustered Containers. Set to true (the default) to share subscriptions. The clientID property must also be set, even if the subscription is nondurable. Set to false to not share subscriptions. This setting should only be used for nondurable subscriptions. The clientID property does not need to be set. |