- Start a node of Liferay Portal 6.2 setup for cluster operation (node1)
- Monitor it's entity cache for class com.liferay.portal.kernel.dao.orm.EntityCache.com.liferay.portal.model.impl.UserImpl
- Log in to the first node
- Notice that the objects stored are 2 for a clean bundle, but YMMV
- Start another node of Liferay Portal 6.2 set up for cluster (node2)
node1 will maintain its cache.
node1 have all its entity cache invalidated as you can see by the number of objects stored going down to 0 again.
Using those properties
Will have no effect. Neither will do partially backporting -
- to ee-6.2.x. LPS-58725
This is because DBUpgrader.upgrade() is called on startup and it invalidates the cache by calling CacheRegistryUtil.setActive(false).