[
https://issues.apache.org/jira/browse/FINERACT-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146282#comment-17146282
]
Petri Tuomola commented on FINERACT-1022:
-----------------------------------------
I've sent a PR that should fix this - looks like it required changes to a
number of configuration files and also to dependencies.
Also checked on the integrationTests for this: there's a test that turns on
caching and turns it off. Unfortunately from client side it's not easy to see
if that actually has had any effect. I've added a log error message to log if
cache is turned on which has not been populated/configured - so going forward
we should at least see an error in the logs. Ideally of course would be good to
have the test fail if the cache is not configured / working - but not sure how
to best achieve this from client side...
> Update ehcache: 2.10.6 to current 3.8.1
> ---------------------------------------
>
> Key: FINERACT-1022
> URL: https://issues.apache.org/jira/browse/FINERACT-1022
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Yemdjih Kaze Nasser
> Assignee: Yemdjih Kaze Nasser
> Priority: Blocker
> Fix For: 1.4.0
>
>
> Update artifactory and version number
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
