*Back to [[Book|Administrator's Configuration File Reference#cfr]] [[Topic|Administrator's Configuration File Reference#chap3]]*
h2. {{server.xml}} elements beginning with T
The following elements are discussed below:
|[#{{thread-pool}}] |[#{{time}}] |[#{{token}}] |
h3. {{thread-pool}} {anchor:t1}
The {{thread-pool}} element configures the threads used to process HTTP requests. This element may appear zero or one time within the {{server}} element. For more information, see [{{server}}|S#s3].
h4. Subelements
The {{thread-pool}} element can contain the following subelements:
Table 3-56 List of {{thread-pool}} Subelements
||Element ||Occurrences ||Description ||
|{{min-threads}} |0 or 1 |The minimum number of HTTP request processing threads. The value can be from 1 to 4096. |
|{{max-threads}} |0 or 1 |The maximum number of HTTP request processing threads. The value can be from 1 to 4096. |
|{{stack-size}} |0 or 1 |The stack size (in bytes) for HTTP request processing threads. The value can be from 8192 to 67108864. |
|{{queue-size}} |0 or 1 |The maximum number of concurrent HTTP connections that can be queued waiting for processing. The value can be from 1 to 1048576. |
h4. See Also
* [{{http}}|F & H#h1]
* [{{keep-alive}}|K & L#k1]
h3. {{time}} {anchor:t2}
The {{time}} element configures the time when an event will occur. This element may appear zero or more times within the {{event}} element. For more information, see [{{event}}|E#e2].
h4. Subelements
The {{time}} element can contain the following subelements:
Table 3-57 List of {{time}} Subelements
||Element ||Occurrences ||Description ||
|{{time-of-day}} |1 |The time when the event will occur. The value should be in the {{hh:mm}} format. |
|{{day-of-week}} |0 or 1 |The day of the week. The value can be {{Sun}}, {{Mon}}, {{Tue}}, {{Wed}}, {{Thu}}, {{Fri}}, or {{Sat}}. |
|{{day-of-month}} |0 or 1 |The day of month. The value can be from 1 to 31. |
|{{month}} |0 or 1 |The name of the month. The value can be {{Jan}}, {{Feb}}, {{Mar}}, {{Apr}}, {{May}}, {{Jun}}, {{Jul}}, {{Aug}}, {{Sep}}, {{Oct}}, {{Nov}}, or {{Dec}}. |
h3. {{token}} {anchor:t3}
The {{token}} element configures a PKCS#11 token. This element may appear zero or more times within the {{pks11}} element. For more information, see [{{pkcs11}}|P#p1].
h4. Subelements
The {{token}} element can contain the following subelements:
Table 3-58 List of {{token}} Subelements
||Element ||Occurrences ||Description ||
|{{enabled}} |0 or 1 |Determines whether the server initializes this PKCS#11 token, prompting for a PIN if necessary. The default value is {{true}}. |
|{{name}} |1 |The name of the token. The server's built-in token is named {{internal}}. |
|{{pin}} |0 or 1 |The PIN required to initialize the token. |
h2. {{server.xml}} elements beginning with T
The following elements are discussed below:
|[#{{thread-pool}}] |[#{{time}}] |[#{{token}}] |
h3. {{thread-pool}} {anchor:t1}
The {{thread-pool}} element configures the threads used to process HTTP requests. This element may appear zero or one time within the {{server}} element. For more information, see [{{server}}|S#s3].
h4. Subelements
The {{thread-pool}} element can contain the following subelements:
Table 3-56 List of {{thread-pool}} Subelements
||Element ||Occurrences ||Description ||
|{{min-threads}} |0 or 1 |The minimum number of HTTP request processing threads. The value can be from 1 to 4096. |
|{{max-threads}} |0 or 1 |The maximum number of HTTP request processing threads. The value can be from 1 to 4096. |
|{{stack-size}} |0 or 1 |The stack size (in bytes) for HTTP request processing threads. The value can be from 8192 to 67108864. |
|{{queue-size}} |0 or 1 |The maximum number of concurrent HTTP connections that can be queued waiting for processing. The value can be from 1 to 1048576. |
h4. See Also
* [{{http}}|F & H#h1]
* [{{keep-alive}}|K & L#k1]
h3. {{time}} {anchor:t2}
The {{time}} element configures the time when an event will occur. This element may appear zero or more times within the {{event}} element. For more information, see [{{event}}|E#e2].
h4. Subelements
The {{time}} element can contain the following subelements:
Table 3-57 List of {{time}} Subelements
||Element ||Occurrences ||Description ||
|{{time-of-day}} |1 |The time when the event will occur. The value should be in the {{hh:mm}} format. |
|{{day-of-week}} |0 or 1 |The day of the week. The value can be {{Sun}}, {{Mon}}, {{Tue}}, {{Wed}}, {{Thu}}, {{Fri}}, or {{Sat}}. |
|{{day-of-month}} |0 or 1 |The day of month. The value can be from 1 to 31. |
|{{month}} |0 or 1 |The name of the month. The value can be {{Jan}}, {{Feb}}, {{Mar}}, {{Apr}}, {{May}}, {{Jun}}, {{Jul}}, {{Aug}}, {{Sep}}, {{Oct}}, {{Nov}}, or {{Dec}}. |
h3. {{token}} {anchor:t3}
The {{token}} element configures a PKCS#11 token. This element may appear zero or more times within the {{pks11}} element. For more information, see [{{pkcs11}}|P#p1].
h4. Subelements
The {{token}} element can contain the following subelements:
Table 3-58 List of {{token}} Subelements
||Element ||Occurrences ||Description ||
|{{enabled}} |0 or 1 |Determines whether the server initializes this PKCS#11 token, prompting for a PIN if necessary. The default value is {{true}}. |
|{{name}} |1 |The name of the token. The server's built-in token is named {{internal}}. |
|{{pin}} |0 or 1 |The PIN required to initialize the token. |