Skip to Content
1
Former Member
May 15, 2015 at 04:57 PM

Cache issues when having long running transaction

466 Views

We have a long running job synchronizing Facet Search Configuration from staging to live config. The job first removes existing linked models using "modelService.removeAll" and then copies over from staging to live. All of this is in a single transaction and takes about a minute. When the job is running and in the same time a search is made or viewing a category in the live catalog in the storefront we get the following exception:

Caused by: item 8796551809180 no longer valid (was removed): object no longer valid
at de.hybris.platform.jalo.Item$CachedGetter.get(Item.java:675)                                
Clearly the problem is not with the isolation level as by default Repeatable Read is used. For some reason the removeAll operation makes the cache inconsistent.

Any help or suggestions will be appreciated?