JMS Auto Reconnect for the Plug-in
Using JMS auto reconnect, which is enabled by default, both the BusinessConnect server and the BusinessConnect palette try to establish connections with the JMS server when the connection is down without restarting.
When JMS is used for private process communication in TIBCO BusinessConnect, both TIBCO BusinessConnect and BusinessConnect palette for ActiveMatrix BusinessWorks make connections to the configured JMS server during startup. If the connection to JMS server cannot be established during startup, such as when a network failure occurs or the JMS server is down, TIBCO BusinessConnect terminates with a warning message. Also, if the connection to JMS server is established during startup but terminated during run time, both TIBCO BusinessConnect and the BusinessConnect palette do not re-establish the connection. Therefore, after correcting the JMS problem, the BusinessConnect palette has to be restarted.
- If the JMS server is down or the network connection is down when the palette starts up, the BusinessConnect palette tries to establish a connection with the JMS server. When the connection is established, the BusinessConnect palette sends messages to and receive messages from TIBCO BusinessConnect. The duration of the initial attempts to establish a valid JMS connection can be set in the Reconnect Duration field of the BC Connection shared resource.
- If the connection between the BusinessConnect palette and the JMS server is terminated during run time, the BusinessConnect palette tries to establish connection with the JMS server. If the connection is not established within the specified period of time that is set in the Reconnect Duration field of the BC Connection shared resource, the BusinessConnect palette activity times out. Furthermore, event sources can no longer receive messages even if the JMS provider comes back up after the timeout.