Method CachingHome.invalidate() Does not Invalidate Entities on All Nodes When Using Versioned Application
(Doc ID 2089270.1)
Last updated on NOVEMBER 05, 2024
Applies to:
Oracle WebLogic Server - Version 12.1.2.0.0 and laterJava Cloud Service - Version 12.1.2 and later
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
Symptoms
An application is deployed into WebLogic Server (WLS) 12.1.3.0.0 cluster using WebLogic versioning.
This application contains Entity Bean 2.1 that includes login information of a user.
EJB CachingHome.invalidate() is called so that the instances of Entity Bean 2.1 are invalidated on all the nodes of the cluster. This is the expected behaviour; but the problem is that only the entities on the node, where the CachingHome.invalidate() is called, are invalidated and will be reloaded. On the other nodes of the cluster, the entities will not be invalidated and contain old state of these entities.
This problem does not occur against WebLogic Server 10.3.3 as the WebLogic versioning when deploying the application was not used.
The problem does not occur when not using WebLogic versioning.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |