JANUS LIMITS: Difference between revisions
Jump to navigation
Jump to search
m (→Syntax) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:JANUS LIMITS}} | {{DISPLAYTITLE:JANUS LIMITS}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Display Janus thread activity</span> | ||
This provides information about overall Janus thread usage activity in an Online, which can be useful in isolating problems with thread availability and in doing capacity planning. The <var>[[JANUS TSTATUS]]</var> (or <var>JANUS TSTAT</var>) command provides information about port-specific thread usage and availability. The <var>JANUS LIMITS</var> command is available in <var class="product">[[Sirius Mods]]</var> 6.0 and later. | This provides information about overall Janus thread usage activity in an Online, which can be useful in isolating problems with thread availability and in doing capacity planning. The <var>[[JANUS TSTATUS]]</var> (or <var>JANUS TSTAT</var>) command provides information about port-specific thread usage and availability. The <var>JANUS LIMITS</var> command is available in <var class="product">[[Sirius Mods]]</var> 6.0 and later. | ||
==Syntax== | ==Syntax== | ||
<p class="syntax" | <p class="syntax"> JANUS LIMITS | ||
</p> | |||
JANUS LIMITS provides the following information: | JANUS LIMITS provides the following information: | ||
| Line 19: | Line 19: | ||
<li>The high water mark of number of Janus "connections" in the Online. These are connections that count against the site's maximum connection limit and include active network connections and persistent <var>WEBSERV</var> sessions (<var class="product">Janus Web Legacy</var> or <var>$Web_Form_Done</var>).</li> | <li>The high water mark of number of Janus "connections" in the Online. These are connections that count against the site's maximum connection limit and include active network connections and persistent <var>WEBSERV</var> sessions (<var class="product">Janus Web Legacy</var> or <var>$Web_Form_Done</var>).</li> | ||
<li>The number of refused connections. Connections can be refused either because the licensed connection limit has been exceeded, all the threads for a port are in use, no sdaemons are available, or Janus could not get the virtual storage for the required buffers on an <var>[[ALLOCC (JANUS DEFINE parameter)|ALLOCC]]</var> port. Ideally, this number should be zero. If it is non-zero, the root cause can only determined by scanning the journal for messages, MSIR.0019, MSIR.0020, MSIR.0023 or MSIR.0026.</li> | <li>The number of refused connections. Connections can be refused either because the licensed connection limit has been exceeded, all the threads for a port are in use, no sdaemons are available, or Janus could not get the virtual storage for the required buffers on an <var>[[ALLOCC (JANUS DEFINE parameter)|ALLOCC]]</var> port. Ideally, this number should be zero. If it is non-zero, the root cause can only be determined by scanning the journal for messages, MSIR.0019, MSIR.0020, MSIR.0023 or MSIR.0026.</li> | ||
0 | |||
To make this process simpler, it might make sense to <var>MSGCTL</var> these messages to <var>OPR</var>. Of course, in many cases it might be possible to infer the cause of refused connections or at least to eliminate some possibilities. For example, if the connection highwater mark is less than the maximum licensed connections, it's clear that no connections could be rejected for exceeding the site's connection limit. | To make this process simpler, it might make sense to <var>MSGCTL</var> these messages to <var>OPR</var>. Of course, in many cases it might be possible to infer the cause of refused connections or at least to eliminate some possibilities. For example, if the connection highwater mark is less than the maximum licensed connections, it's clear that no connections could be rejected for exceeding the site's connection limit. | ||
| Line 28: | Line 28: | ||
==Example== | ==Example== | ||
<p class="code"> | <p class="code"> Limit MaxCon Active Perst InUse InUseH Refused | ||
Sdaemons/threads 15 0 0 0 15 17 | |||
Janus Base 150 0 0 0 15 0 | |||
Janus Open Server 150 0 0 0 0 0 | |||
Janus Open Client 150 0 0 0 0 0 | |||
Janus Specialty Data Store 150 0 0 0 0 0 | |||
Janus Web 100 0 0 0 15 0 | |||
Janus Network Security 150 0 0 0 15 0 | |||
Janus Sockets 50 0 0 0 1 0 | |||
</p> | </p> | ||
<p class="caption">JANUS LIMITS output</p> | <p class="caption">JANUS LIMITS output</p> | ||
See | ==See also== | ||
<ul> | |||
<li>[[List_of_Janus_commands|Janus command list]] | |||
</ul> | |||
[[Category:Janus commands|JANUS LIMITS]] | [[Category:Janus commands|JANUS LIMITS]] | ||
Latest revision as of 14:14, 27 September 2024
Display Janus thread activity
This provides information about overall Janus thread usage activity in an Online, which can be useful in isolating problems with thread availability and in doing capacity planning. The JANUS TSTATUS (or JANUS TSTAT) command provides information about port-specific thread usage and availability. The JANUS LIMITS command is available in Sirius Mods 6.0 and later.
Syntax
JANUS LIMITS
JANUS LIMITS provides the following information:
- The maximum number of licensed simultaneous connections.
- The number of sdaemon threads in the Online. The minimum of this value and the maximum licensed connection value is the absolute limit on simultaneous Janus connections in the Online. Since sdaemon threads can be used for things other than Janus (such as Daemon objects), the actual number of sdaemons available for Janus processing in an Online will often be less than the value displayed here.
- The current number of Janus "connections" in the Online. These are connections that count against the site's maximum connection limit and include active network connections and persistent WEBSERV sessions (Janus Web Legacy or $Web_Form_Done).
- The high water mark of number of Janus "connections" in the Online. These are connections that count against the site's maximum connection limit and include active network connections and persistent WEBSERV sessions (Janus Web Legacy or $Web_Form_Done).
- The number of refused connections. Connections can be refused either because the licensed connection limit has been exceeded, all the threads for a port are in use, no sdaemons are available, or Janus could not get the virtual storage for the required buffers on an ALLOCC port. Ideally, this number should be zero. If it is non-zero, the root cause can only be determined by scanning the journal for messages, MSIR.0019, MSIR.0020, MSIR.0023 or MSIR.0026. 0 To make this process simpler, it might make sense to MSGCTL these messages to OPR. Of course, in many cases it might be possible to infer the cause of refused connections or at least to eliminate some possibilities. For example, if the connection highwater mark is less than the maximum licensed connections, it's clear that no connections could be rejected for exceeding the site's connection limit. SirMon also provides some TCP and sdaemon usage statistics that might be helpful in isolating the cause of refused connections.
Example
Limit MaxCon Active Perst InUse InUseH Refused Sdaemons/threads 15 0 0 0 15 17 Janus Base 150 0 0 0 15 0 Janus Open Server 150 0 0 0 0 0 Janus Open Client 150 0 0 0 0 0 Janus Specialty Data Store 150 0 0 0 0 0 Janus Web 100 0 0 0 15 0 Janus Network Security 150 0 0 0 15 0 Janus Sockets 50 0 0 0 1 0
JANUS LIMITS output