Review the diagram below. It depicts the following:
A WebLogic domain that consists of two WebLogic clusters that are each included in a Coherence cluster
The Coherence cluster includes a configuration for Coherence*Web HTTP session storage
An application deployed on cluster 1 that is configured to use Coherence*Web
A client is using a web browser to interact with the application on cluster 1 (via a proxy)
The client's HTTP session is stored by Coherence*Web on the server in the upper right-hand corner
The server where the client's HTTP session is stored crashes
Assuming the next request for an HTTP session attribute is a new attribute that is not stored in a near-cache, the client's session attribute is fetched from the remaining storage-enabled server in cluster 2.
Why is the session attribute retrieved from this other server's cache? (Choose the best answer.)
Rolling upgrade applies only to upgrades within a major product version. For example, you can upgrade from 10.0 to 10.3.1, but cannot upgrade from 9.0 to 10.0.
Alona
4 days agoYoko
9 days agoArlette
16 days agoYong
19 days agoCorinne
20 hours agoNakisha
23 days agoArlette
27 days ago