此内容没有您所选择的语言版本。

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.
Expand
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)
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat