-
Notifications
You must be signed in to change notification settings - Fork 33
/
connfact_handling.htm
89 lines (70 loc) · 4.23 KB
/
connfact_handling.htm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
<!--
Copyright (c) 2000-2017 Oracle and/or its affiliates. All rights reserved.
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-->
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>connfact handling</TITLE>
<LINK rel="StyleSheet" href="ide.css">
</HEAD>
<BODY>
<H2>Connection Factory Object Properties > <BR>Connection Handling</H2>
<P>Use the Connection Handling tab to reconfigure the connections that will be
created by this factory.</P>
<p><b>Message Server Address List</b> Specifies a list of message server addresses
(one or more), separated by commas, each corresponding to a different broker
instance to which a client runtime can connect. Each address in the list specifies
the host name, host port, and connection service for the connection. <BR>For more
information about Message Server Address Syntax, <A HREF="message_server_syntax.htm">click here</A><br>
</p>
<p><b>Address List Order</b> Specifies whether connection attempts are in the
order of addresses in the message server address list (PRIORITY) or in a random
order (RANDOM). If you have many clients attmpting a connection using the same
connection factory, you would use a random order to prevent them from all being
connected to the same address.<br>
</p>
<p><b>Number of Address List Iterations </b>Specifies the number of times the
client runtime will itereate through the the message server address list in
an effort to establish (or re-establish a connection). A value of -1 indicates
that the number of reconnect attempts is unlimited.</p>
<p><b>Enable Auto-reconnect to Message Server</b> A value of true specifies that
the client runtime will attempt to reconnect to a message server (or the list
of addresses in a message server list) when a connection is lost.<br>
</p>
<p><b>Number of Reconnect Attempts per Address</b> Specifies the number of reconnect
attempts for each address in the message server address list before the client
runtime moves on to try the next address in the list. A value of -1 indicates
that the number of reconnect attempts is unlimited.<br>
</p>
<p><b>Reconnect Interval per Address (milliseconds)</b> Specifies the interval
(in milliseconds) between reconnect attempts for each address in the message
server address list before the client runtime moves on to try the next address
in the list. If too short, this time interval does not give a broker time to
recover. If too long, the reconnect can might represent an unacceptable delay.<br>
</p>
<p><b>Connection Ping Interval (seconds)</b> Specifies the minimum interval (in
seconds) at which the client runtime will periodically check that its connection
to the broker is healthy.<br>
</p>
<p><b>Ping reply timeout (milliseconds)</b> Specifies the maximum time, in milliseconds, that the client runtime will
wait for a ping reply or any data sent from the broker since its last ping reply or data sent.<br></p>
<p><b>Abort connection on ping reply timeout</b> Specifies whether the connection to the broker should be aborted when
no reply to a ping has been received within the ping reply timeout period.
If the connection is aborted, the client runtime operates as though the connection to the broker were broken.
<br></p>
<p><b>TCP socket connection timeout (milliseconds)</b> Specifies the socket timeout, in milliseconds,
used when a TCP connection is made to the broker. A timeout of zero is interpreted as an infinite timeout.
The connection will then block until established or an error occurs.
This property is used when connecting to the port mapper as well as when connecting to the required service.<br></p>
<P> </P>
</BODY>
</HTML>