Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.0.X, 7.1.X, 7.2.X, 7.3.X, Master
-
7.3.x, 7.2.x, 7.1.x, 7.0.x
-
Committed
-
3
Description
When working with a database like Oracle where the maximum number of expressions in an IN clause is limited we can still obtain the following error, even after LPS-68101:
at com.liferay.portal.kernel.service.persistence.impl.BasePersistenceImpl.processException(BasePersistenceImpl.java:269) at com.liferay.portal.service.persistence.impl.PortletPreferencesPersistenceImpl.fetchByPrimaryKeys(PortletPreferencesPersistenceImpl.java:5894) at com.liferay.portal.cache.internal.dao.orm.FinderCacheImpl._primaryKeyToResult(FinderCacheImpl.java:364) at com.liferay.portal.cache.internal.dao.orm.FinderCacheImpl.getResult(FinderCacheImpl.java:144) at com.liferay.portal.kernel.dao.orm.FinderCacheUtil.getResult(FinderCacheUtil.java:49) at com.liferay.portal.service.persistence.impl.PortletPreferencesPersistenceImpl.findByO_O_P(PortletPreferencesPersistenceImpl.java:2427) at com.liferay.portal.service.persistence.impl.PortletPreferencesPersistenceImpl.findByO_O_P(PortletPreferencesPersistenceImpl.java:2380) at com.liferay.portal.service.persistence.impl.PortletPreferencesPersistenceImpl.findByO_O_P(PortletPreferencesPersistenceImpl.java:2334)
This can happen when the result of a finder returns more than N elements and we try to retrieve them all to save them in the EntityCache.
Attachments
Issue Links
- depends on
-
LPS-134094 BasePersistenceImpl.fetchByPrimaryKeys does not honor database.in.max.parameters
- Closed