Show Table of Contents
30.4.3. JCA Inbound Configuration
The inbound configuration should again remain unchanged. This controls what forwards messages onto MDBs. It is possible to override properties on the MDB by adding an activation configuration to the MDB itself. This could be used to configure the MDB to consume from a different server.
The inbound configuration also defines additional properties in addition to the global configuration properties.
Table 30.3. Inbound Configuration Properties
| Property Name | Property Type | Property Description |
|---|---|---|
| Destination | String | JNDI name of the destination |
| DestinationType | String | type of the destination, either javax.jms.Queue or javax.jms.Topic (default is javax.jms.Queue) |
| AcknowledgeMode | String | The Acknowledgment mode, either Auto-acknowledge or Dups-ok-acknowledge (default is Auto-acknowledge). AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE are acceptable values. |
| MaxSession | Integer | Maximum number of session created by this inbound configuration (default is 15) |
| MessageSelector | String | the message selector of the consumer |
| SubscriptionDurability | String | Type of the subscription, either Durable or NonDurable |
| SubscriptionName | String | Name of the subscription |
| TransactionTimeout | Long | The transaction timeout in milliseconds (default is 0, the transaction does not timeout) |
| UseJNDI | Boolean | Whether or not use JNDI to look up the destination (default is true) |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.