TCPKEEPALIVE (JANUS DEFINE parameter) - Revision history

JAL: remove displaytitle

2016-06-08T00:09:32Z

remove displaytitle

← Older revision		Revision as of 00:09, 8 June 2016
Line 1:		Line 1:
	~~{{DISPLAYTITLE:TCPKEEPALIVE}}~~
	<span class="pageSubtitle">Use TCP Keepalives</span>		<span class="pageSubtitle">Use TCP Keepalives</span>

JALWiccan: Automatically generated page update

2013-04-16T22:25:26Z

Automatically generated page update

← Older revision		Revision as of 22:25, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:TCPKEEPALIVE}}		{{DISPLAYTITLE:TCPKEEPALIVE}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Use TCP Keepalives~~<section end="desc" />~~</span>		<span class="pageSubtitle">Use TCP Keepalives</span>

	<var>TCPKEEPALIVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>TCPKEEPALIVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 18:06, 2 March 2012

2012-03-02T18:06:54Z

← Older revision		Revision as of 18:06, 2 March 2012
Line 6:		Line 6:
	This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.		This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.

	In some sense, the term "keepalive" is a misnomer &~~amp;~~mdash; keepalive packets that are not responded to cause a connection to be closed, so keepalives actually cause connections to be closed faster than they might be otherwise.		In some sense, the term "keepalive" is a misnomer — keepalive packets that are not responded to cause a connection to be closed, so keepalives actually cause connections to be closed faster than they might be otherwise.

	<var>TCPKEEPALIVE</var> probably only makes sense for ports where connections are held open for long periods of time. <var>[[JANUS DEFINE#type\|TNSERV]]</var> ports are the most likely candidate. For these ports, <var>TCPKEEPALIVE</var> might be useful for two reasons:		<var>TCPKEEPALIVE</var> probably only makes sense for ports where connections are held open for long periods of time. <var>[[JANUS DEFINE#type\|TNSERV]]</var> ports are the most likely candidate. For these ports, <var>TCPKEEPALIVE</var> might be useful for two reasons:

JALWiccan: 1 revision

2012-03-01T21:15:18Z

1 revision

← Older revision	Revision as of 21:15, 1 March 2012
(No difference)

JALWiccan: 1 revision

2012-03-01T21:15:13Z

1 revision

← Older revision		Revision as of 21:15, 1 March 2012
Line 6:		Line 6:
	This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.		This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.

	In some sense, the term "keepalive" is a misnomer — keepalive packets that are not responded to cause a connection to be closed, so keepalives actually cause connections to be closed faster than they might be otherwise.		In some sense, the term "keepalive" is a misnomer &mdash; keepalive packets that are not responded to cause a connection to be closed, so keepalives actually cause connections to be closed faster than they might be otherwise.

	<var>TCPKEEPALIVE</var> probably only makes sense for ports where connections are held open for long periods of time. <var>[[JANUS DEFINE#type\|TNSERV]]</var> ports are the most likely candidate. For these ports, <var>TCPKEEPALIVE</var> might be useful for two reasons:		<var>TCPKEEPALIVE</var> probably only makes sense for ports where connections are held open for long periods of time. <var>[[JANUS DEFINE#type\|TNSERV]]</var> ports are the most likely candidate. For these ports, <var>TCPKEEPALIVE</var> might be useful for two reasons:
Line 15:		Line 15:
	</ol>		</ol>

	Since the TCP/IP stack does the keepalives, the overhead in ''Model 204'' for setting this parameter is virtually zero.		Since the TCP/IP stack does the keepalives, the overhead in <var class="product">Model 204</var> for setting this parameter is virtually zero.

	This parameter is only available in <var class="product">Sirius Mods</var> Version 6.9 and later.		This parameter is only available in <var class="product">Sirius Mods</var> Version 6.9 and later.

JALWiccan: 1 revision

2012-02-29T23:08:41Z

1 revision

← Older revision	Revision as of 23:08, 29 February 2012
(No difference)

JALWiccan: 1 revision

2012-02-29T23:08:37Z

1 revision

← Older revision		Revision as of 23:08, 29 February 2012
Line 6:		Line 6:
	This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.		This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.

	In some sense, the term "keepalive" is a misnomer -- keepalive packets that are not responded to cause a connection to be closed, so keepalives actually cause connections to be closed faster than they might be otherwise.		In some sense, the term "keepalive" is a misnomer — keepalive packets that are not responded to cause a connection to be closed, so keepalives actually cause connections to be closed faster than they might be otherwise.

	<var>TCPKEEPALIVE</var> probably only makes sense for ports where connections are held open for long periods of time. <var>[[JANUS DEFINE#type\|TNSERV]]</var> ports are the most likely candidate. For these ports, <var>TCPKEEPALIVE</var> might be useful for two reasons:		<var>TCPKEEPALIVE</var> probably only makes sense for ports where connections are held open for long periods of time. <var>[[JANUS DEFINE#type\|TNSERV]]</var> ports are the most likely candidate. For these ports, <var>TCPKEEPALIVE</var> might be useful for two reasons:

JALWiccan: 1 revision

2012-02-29T22:33:28Z

1 revision

← Older revision	Revision as of 22:33, 29 February 2012
(No difference)

JALWiccan: 1 revision

2012-02-29T22:33:19Z

1 revision

← Older revision		Revision as of 22:33, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Use TCP Keepalives<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Use TCP Keepalives<section end="desc" /></span>

	<var>TCPKEEPALIVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port~~. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]~~.		<var>TCPKEEPALIVE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.		This parameter specifies that connections on the port should use TCP keepalives. TCP keepalives request that the TCP stack send periodic "keepalive" packets to the communications partner to see if it is still there. The time interval between these packets, which cannot be set by Janus, is set in the TCP/IP stack configuration. For example, with the IBM stacks, the keepalive interval is set in the TCPCONFIG INTERVAL parameter for BPX (IBM Communications Server) and in the KEEPALIVEOPTIONS INTERVAL parameter for VM TCP/IP.

JALWiccan: 1 revision

2012-02-29T20:00:25Z

1 revision

← Older revision	Revision as of 20:00, 29 February 2012
(No difference)