You require high availability for HTTP sessions in a web application. In addition, you have the
following constraints:
• There is little free memory on the machines hosting the cluster.
• HA must be guaranteed even when multiple machines fall simultaneously.
• You are not allowed to update the production databases schema.
Which is the best session persistence option?
A.
Database persistence
B.
File persistence
C.
In-memory replication
D.
Whole –server migration
B
Answer : B/
Explanation : For high availability, a persistent file-based store (default, or custom) can be migrated along with its parent server as part of the “whole server-level” migration feature, which provides both automatic and manual migration at the server level, rather than on the service level.
Source : Oracle weblogic 12c
A is wrong : need to modify database schema
C is wrong : Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.
That’ll consume more memory so is not possible for this case.
Source : https://books.google.fr/books?id=oLq6AgAAQBAJ&pg=PA638&lpg=PA638&dq=disadvantage+in+memory+replication+http+session+consume&source=bl&ots=rdUNFch4mW&sig=YiX6eLjxLBkHt5Zr_5RixdIITtU&hl=fr&sa=X&ei=HZrlVNOiOoO1UYvvg7gD&ved=0CCgQ6AEwAA#v=onepage&q=disadvantage%20in%20memory%20replication%20http%20session%20consume&f=false
D is wrong : is not a persistent session > Migration in WebLogic Server is the process of moving a clustered WebLogic Server instance or a component running on a clustered instance elsewhere in the event of failure. In the case of whole server migration, the server instance is migrated to a different physical machine upon failure. In the case of service-level migration, the services are moved to a different server instance within the cluster.
B .. good explanation from nebz
B .. good explanation from nebz