Defines a thread pool.
none
Attribute |
Default |
Description |
---|---|---|
none |
Specifies the thread pool ID. |
|
0 |
(optional) Specifies the minimum number of threads in the pool. These are created when the thread pool is instantiated. |
|
200 |
(optional) Specifies the maximum number of threads the pool can contain. |
|
120 |
(optional) Specifies the amount of time after which idle threads are removed from the pool. |
|
1 |
(optional) Specifies the total number of work queues serviced by this thread pool. |
Contains thread pools.
The following table describes subelements for the thread-pools element.
Table 1–214 thread-pools Subelements
Element |
Required |
Description |
---|---|---|
one or more |
Defines a thread pool. |
Configures the Java Transaction Service (JTS).
The following table describes subelements for the transaction-service element.
Table 1–215 transaction-service Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the transaction-service element.
Table 1–216 transaction-service Attributes
Attribute |
Default |
Description |
---|---|---|
false (developer profile) true (cluster profile) |
(optional) If true, the server instance attempts transaction recovery during startup. |
|
0 |
(optional) Specifies the amount of time after which the transaction is aborted. If set to 0, the transaction never times out. |
|
directory specified by the log-root attribute of the domain element |
(optional) Specifies the parent directory of the transaction log directory instance-name/tx. The directory in which the transaction logs are kept must be writable by the user account under which the server runs. A relative path is relative to the log-root attribute of the domain element. |
|
rollback |
(optional) If the outcome of a distributed transaction cannot be determined because other participants are unreachable, this property determines the outcome. Allowed values are rollback and commit. |
|
600 |
(optional) Determines the retry time in the following scenarios:
|
|
65536 (64 K) |
(optional) Specifies the number of transactions between keypoint operations in the log. Keypoint operations reduce the size of the transaction log file by compressing it. A larger value for this attribute results in a larger transaction log file, but fewer keypoint operations and potentially better performance. A smaller value results in smaller log files, but slightly reduced performance due to the greater frequency of keypoint operations. |
The following table describes properties for the transaction-service element.
Table 1–217 transaction-service Properties
Property |
Default |
Description |
---|---|---|
true |
If true, the Oracle XA Resource workaround is used in transaction recovery. |
|
false |
If true, disables transaction logging, which might improve performance. If the automatic-recovery attribute is set to true , this property is ignored. |
|
specific to the XAResource used |
Changes the XAResource timeout. In some cases, the XAResource default timeout can cause transactions to be aborted, so it is desirable to change it. |
|
none if this property is absent, 60 if this property is present but has no value |
Specifies the interval, in seconds, at which an asynchronous thread checks for pending transactions and completes them. |
|
true |
If true, enables last agent optimization, which improves the throughput of transactions. If one non-XA resource is used with XA resources in the same transaction, the non XA resource is the last agent. |
|
false |
If true, cluster-wide delegated recovery is enabled. You must also facilitate storing of transaction logs in a shared file system in one of these ways:
<server config-ref="server-config" name="server"> <system-property name="TX-LOG-DIR" value="/net/tulsa/nodeagents/na/instance1/logs"/> </server> |
|
60 |
Specifies the wait time, in seconds, after which an instance starts the recovery for a dead instance. |
|
none |
Specifies the JNDI name of the JDBC resource for the database to which transactions are logged. For more information, see Chapter 16, Using the Transaction Service, in Sun GlassFish Communications Server 1.5 Developer’s Guide. |
|
host name on which the Communications Server runs |
Specifies the host name that the transaction service uses to identify transactions being managed by the installed Communications Server. This can sometimes be useful for recovering transactions from the log file that was created on a different host running the Communications Server. This should also be used when the Communications Server is installed as part of Sun Cluster HA. |
Configures an eXtensible Stylesheet Language Transformation (XSLT) rule, which transforms a web service message.
The following table describes subelements for the transformation-rule element.
Table 1–218 transformation-rule Subelements
Element |
Required |
Description |
---|---|---|
zero or one |
Contains a text description of this element. |
The following table describes attributes for the transformation-rule element.
Table 1–219 transformation-rule Attributes
Specifies intermediate hosts and domains according to RFC 3325.
The following table describes subelements for the trusted-entity element.
Table 1–220 trusted-entity Subelements
Element |
Required |
Description |
---|---|---|
only one |
Identifies the trusted host on the network using an IP address. |
|
zero or one |
Identifies the trusted host on the network using domain names. |
|
zero or one |
Identifies the principal of the trusted entity. |
The following table describes attributes for the trusted-entity element.
Table 1–221 trusted-entity Attributes
Attribute |
Default |
Description |
---|---|---|
none |
Specifies a unique identifier for the trusted-entity element. |
|
none |
(optional) When set to intermediate, specifies configuration information for incoming messages. When set to destination, specifies configuration information for outgoing messages. When not set, specifies configuration information for both incoming and outgoing messages. |
Specifies a custom trust handler according to RFC 3325. This provides a custom implementation to determine trust and to convert user identity to a format recognized by the system.
The following table describes subelements for the trust-handler element.
Table 1–222 trust-handler Subelements
Element |
Required |
Description |
---|---|---|
zero or more |
Specifies a property or a variable. |
The following table describes attributes for the trust-handler element.
Table 1–223 trust-handler Attributes
Attribute |
Default |
Description |
---|---|---|
none |
Specifies the name of the class that implements com.sun.enterprise.security.auth.TrustHandler and com.sun.enterprise.security.auth.PrincipalMapper. |