Passivation PassivationPassivation allows the state of a Java object — such as an entire Process Commander PRThread context, including the clipboard state — to be saved to a file. A later operation, known as activation, restores the object.
Process Commander can support HTTP session passivation and requestor clipboard page passivation. Configuration is controlled by prconfig.xml file settings.
When all or part of a requestor clipboard is idle for an extended period and available JVM memory is limited, Process Commander automatically saves clipboard pages in a disk file on the server. This frees up JVM memory for use by active requestors. (Typically, such passivation occurs only on systems supporting 50 or more simultaneous requestors.)
Optional HTTP session passivation can help provide high availability in a multinode environment. If a node fails, activation of the session can usually continue on a different node. This allows a cluster to operate in a resilient manner, reducing the risk of loss of data if a node fails.
In a single-node system, the OnTimeOut passivation setting allows a
user to resume work without loss of context after leaving the
browser window idle for a period. The user may be required to reauthenticate.
Passivation in Process Commander is similar in purpose and results to J2EE EJB bean passivation, but Process Commander passivation does not require Enterprise Archive (EAR file) deployments or use a J2EE passivation interface. Process Commander passivation can occur on any platform, including Tomcat.
|
cluster, daemon, failover, load-balancing, node, prconfig.xml file, timeout |
|
Understanding passivation and requestor timeouts |
Definitions — P