en.help.ref-webcontaineravailability.html Maven / Gradle / Ivy
Show all versions of console-web-plugin Show documentation
Web Container Availability
Use the Web Container Availability page to configure availability settings for the web container.
The Web Container Availability page contains the following options.
- Load Defaults
-
Button to restore settings that have default values to their default values. Settings that do not have default values are not changed.
- Configuration Name
-
The name of the configuration to which the settings on this page apply. This field is read only.
- Availability Service
-
If the Enabled checkbox is selected, availability is enabled for the web container.
- Persistence Type
-
The persistence mechanism used.
-
If Availability Service Enabled is not checked, select one of the following:
-
memory for no session persistence
-
file for session persistence based on the file system that is not highly available
-
If Availability Service Enabled is checked, select replicated for session persistence based on cluster failover that is highly available.
- Persistence Frequency
-
The frequency at which the HTTP session is stored:
-
web-method — The session state is stored at the end of each web request prior to sending a response back to the client. This mode provides the best guarantee that the session state is fully updated in case of failure. This is the default.
- Persistence Scope
-
The scope of HTTP session changes required for storage to occur:
-
session — The entire session state is stored every time. This mode provides the best guarantee that your session data is correctly stored for any distributable web application.
-
modified-session — The entire session state is stored if it has been modified. A session is considered to have been modified if HttpSession.setAttribute() or HttpSession.removeAttribute() was called. You must guarantee that setAttribute() is called every time an attribute is changed. This is not a Java EE specification requirement, but it is required for this mode to work properly.
-
modified-attribute — Only modified session attributes are stored. For this mode to work properly, you 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.
- Single-Sign-On State
-
If the Enabled checkbox is selected, the single sign-on state available for failover.
- Additional Properties
-
Additional properties for Web Container Availability.
The GlassFish Server does not define any additional Web Container Availability properties.
Related Tasks
-
-
-
-
-
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices