Icat+ does not start when filling the cache with more than max limit of entities
Reported by @a2282 and @rolf.krahl
ICAT+ will not start because the limit of the max entities is reached. ICAT error trace is:
2021-05-27 21:27:18,668 INFO [http-thread-pool::http-listener-2(4)] EntityBeanManager - Final search JPQL: SELECT DISTINCT investigation FROM Investigation investigation ORDER BY investigation.startDate DESC
2021-05-27 21:27:19,765 INFO [http-thread-pool::http-listener-2(4)] IcatExceptionMapper - Processing VALIDATION: attempt to return more than 10000 entities
ICAT+ error trace is:
2021-05-27T19:27:19.778Z [error]: [cache] Cache could not be initialized
error : Request failed with status code 412
It does not happen here because ICAT has been configured with:
# Restrict total number of entities to return in a search call
maxEntities = 100000
Edited by Alejandro De Maria Antolinos