JMS Channels : Reconnecting to a JMS Server

Reconnecting to a JMS Server
The following configuration properties enable you to define how BusinessEvents attempts to reconnect to a JMS server in the event of a disconnection.
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 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.