Hi Brian, Many thanks for your quick response. After we disabled caching the collections (work around for now to keep our service running), this error never happen. Therefore most likely the bug is similar and still happening with other providers (i.e. ehcache which is we currently use).

For performance reason, we do need to cache the collections???

What is your recommendation... ?