Cluster Deployment Descriptor Reference : Processing Units Tab — JMS Server Connection Properties

Processing Units Tab — JMS Server Connection Properties
The following properties relate to JMS channels. Most enable you to define how TIBCO BusinessEvents attempts to reconnect to a JMS server in the event of a disconnection. Two relate to disabling connections. See TIBCO BusinessEvents Developer’s Guide for details about configuring a JMS channel.
You can add these properties at the cluster level if they apply to JMS channels in all processing units in the cluster.
The value must use the format: attempts, retry interval. For example: 10,500 means 10 attempts, with a 500 millisecond interval between each retry attempt.
Note: Use either be.jms.reconnect.timeout or com.tibco.tibjms.connect.attempts. If you set both the properties, then com.tibco.tibjms.connect.attempts takes precedence.
A value of zero (0) means do not retry. Any other value means keep retrying (with no limit to number of retries), and use the specified interval between each attempt.
Note: Unacknowledged messages (Events) are resent to the TIBCO BusinessEvents engine, which may result in duplicate events.
Note: Use either be.jms.reconnect.timeout or com.tibco.tibjms.connect.attempts. If you set both the properties, then com.tibco.tibjms.connect.attempts takes precedence.
Specifies a case-insensitive character pattern that matches all error messages or error codes that will cause a reconnect attempt.
By default, be-engine connects to all defined channels on startup, including those not mentioned in the CDD file. This is because such channels can be used as output channels. However this is not always desired.
To disable queue or topic connections for specific JMS channels, add the following properties as appropriate. Enter the project path to the JMS channel as the individual value. Use commas or spaces as the delimiter. Use forward slashes in the project path. For example: