[
https://issues.apache.org/jira/browse/CAMEL-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993355#comment-16993355
]
Jens Kleine-Herzbruch commented on CAMEL-14281:
-----------------------------------------------
No promises. It's something we need, but it's not the highest priority.
> Support sync reads/read locking in JCachePolicyProcessor
> --------------------------------------------------------
>
> Key: CAMEL-14281
> URL: https://issues.apache.org/jira/browse/CAMEL-14281
> Project: Camel
> Issue Type: New Feature
> Components: camel-jcache
> Affects Versions: 3.0.0
> Reporter: Jens Kleine-Herzbruch
> Priority: Major
> Fix For: 3.x
>
>
> Currently, if two requests for the same cache key come in simultaneously,
> both requests will execute the route decorated with the cache policy. If this
> route includes expensive calculations/integrations this may be undesirable.
> Instead, only the first request should kick of the real route, and the second
> should block on the cache read until the result of the first route has
> entered the cache.
>
> Spring, for example, supports this with the "sync" parameter on @Cacheable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
