The following table describes attributes for the sip-container-availability element.
Table 1–190 sip-container-availability Attributes
Attribute |
Default |
Description |
---|---|---|
true |
(optional) If set to true, and if availability is enabled for the server instance (see availability-service), high-availability features apply to all SIP extension modules deployed to the server instance that do not have availability disabled. All instances in a cluster should have the same availability value to ensure consistent behavior. |
|
memory (availability disabled) replicated (availability enabled) |
(optional) Specifies the session persistence mechanism for SIP extension modules that have availability enabled. Allowed values are memory (no persistence) and replicated (other servers). If set to memory, the manager-properties element’s session-file-name attribute specifies the file system location where the session state is stored if the server instance is gracefully shut down. This is useful for internal testing but is not supported for production environments. |
|
sip-transaction |
(optional) Specifies how often the session state is stored. The default, sip-transaction, is the only allowed value. The session state is stored at the end of each request prior to sending a response back to the client. This provides the best guarantee that the session state is fully updated in case of failure. |
|
session |
(optional) Specifies how much of the session state is stored. Allowed values are as follows:
|
|
true |
(optional) Deprecated. If true, specifies that a forward and reverse repair should be performed on an instance that has joined or rejoined the cluster. |
If the persistence-scope attribute is set to modified-attribute , your SIP extension module must follow these guidelines:
Call setAttribute() every time the session state is modified.
Make sure there are no cross-references between attributes. The object graph under each distinct attribute key is serialized and stored separately. If there are any object cross references between the objects under each separate key, they are not serialized and deserialized correctly.
Distribute the session state across multiple attributes, or at least between a read-only attribute and a modifiable attribute.