10.02.2013 Views

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Reconnection<br />

Fault Tolerant Connections <strong>and</strong> Reconnection<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> endpoints appear as <strong>Sonic</strong>MQ clients. From the perspective of<br />

<strong>Sonic</strong>MQ, the <strong>ESB</strong> reconnect implementation is a customized client reconnect<br />

implementation.<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> always tries to reconnect when a connection fails, regardless of<br />

whether the faultTolerant connection parameter is set to true or false.<br />

The following sections explain how initial connections are created <strong>and</strong> how interrupted<br />

connections are reconnected.<br />

Initial Connections<br />

The initialConnectTimeout value specifies for how many seconds an <strong>ESB</strong> endpoint will<br />

try to establish an initial connection. This value is the total time during which the initial<br />

connection is attempted, not the time spent attempting to connect to each URL. This<br />

means that some URLs in the URL list might not be attempted. For non-fault tolerant<br />

connections, this parameter is ignored <strong>and</strong> the endpoint tries each URL once.<br />

Note Two special timeout values, 0 <strong>and</strong> -1, are available in <strong>Sonic</strong>MQ but are not available in<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong>, where configurations are limited to a value range of 1-3600.<br />

If the <strong>Sonic</strong>MQ initial connection cannot be established within the timeout period, the<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> reconnect logic will retry. This retry looks like the initial connection<br />

attempt to the <strong>Sonic</strong>MQ implementation. The retry starts trying to establish connections<br />

again, starting with the first URL in the initial connection list. The <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong><br />

retry will continue until the container is shut down.<br />

Interrupted Connections<br />

The faultTolerantReconnectTimeout value specifies how many seconds an <strong>ESB</strong> endpoint<br />

will allow for reconnecting a broken connection to the primary or backup broker using the<br />

fault tolerant mechanism. If the connection is re-established before the timeout expires,<br />

the endpoint will not be connected to a broker outside the original fault tolerant pair.<br />

If the connection is not re-established within the reconnect timeout period, <strong>Sonic</strong>MQ<br />

signals that the connection failed <strong>and</strong> the <strong>Sonic</strong> <strong>ESB</strong> reconnect logic tries to create a new<br />

connection using the initial connection process described previously. In this case, it is<br />

possible that a connection can be established to a broker that is not a member of the<br />

original fault tolerant pair.<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> <strong>Guide</strong> 8.5 110

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!