Daily Log for #alfresco IRC Channel

Alfresco discussion and collaboration. Stick around a few hours after asking a question.

Official support for Enterprise subscribers: support.alfresco.com.

Joining the Channel:

Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.

More information about the channel is in the wiki.

Getting Help

More help is available in this list of resources.

Daily Log for #alfresco

2017-03-11 12:22:04 GMT <alfbot> AFaust: Sent 15 hours and 46 minutes ago: <yregaieg> I can see in the config of the executor from the thread dump that caches should be disabled (cacheEnabled=false) Neverthless, it is taking 2.8Gb of my precious heap !

2017-03-11 12:22:05 GMT <alfbot> AFaust: Sent 15 hours and 31 minutes ago: <yregaieg> s/thread dump/memory dump/

2017-03-11 12:28:53 GMT <AFaust> yregaieg: The cacheEnabled setting is only relating to use of the TransactionalCacheManager. This has nothing to do with the statement-level caching. When cacheEnabled is false it only means that there are no caches + listeners in place to handle propagation of stuff changed within the transaction to a global, cross-transaction cache.

2017-03-11 12:29:45 GMT <AFaust> If you would just look at the BaseExecutor constructor and rest of class you would see that NOTHING influences the use of localCache

2017-03-11 12:39:37 GMT <yregaieg> AFaust, are you saying I will need to add flushCache attribute to my statements ?

2017-03-11 12:39:43 GMT <yregaieg> like this : http://stackoverflow.com/a/26482095/2307988

2017-03-11 12:39:44 GMT <alfbot> Title: java - MyBatis: how to bypass a local cache and directly hit the DB on specific select - Stack Overflow (at stackoverflow.com)

2017-03-11 12:43:01 GMT <AFaust> flushCache clears the cache before the select - not after as the SO comment suggests

2017-03-11 12:43:45 GMT <AFaust> LocalCacheScope.STATEMENT will clear the cache after the statement

2017-03-11 12:44:32 GMT <AFaust> the former is configured on statement level, the latter on global level

2017-03-11 12:45:39 GMT <AFaust> Did you see the small change that is necessary to reduce the memory footprint due to the select SQL strings?

2017-03-11 15:58:23 GMT <yregaieg> AFaust, Yes, I have seen that line you added..

2017-03-11 16:01:43 GMT <yregaieg> I am thinking about giving it a run and seeing if it really does make a big difference (according to this : http://stackoverflow.com/questions/10578984/what-is-string-interning it should, but why isn't it don automatically on each and every string? string are immutable any way, or is the CPU footprint for that call too heavy)

2017-03-11 16:01:44 GMT <alfbot> Title: java - What is String interning? - Stack Overflow (at stackoverflow.com)

2017-03-11 16:03:21 GMT <AFaust> It is not done on each and every string because there is a global overhead to managing the interned String pool

2017-03-11 16:03:59 GMT <AFaust> And it would be inefficient e.g. to have each and every intermediary String (i.e. in a concatenation use case) interned

2017-03-11 16:05:14 GMT <AFaust> In Java 6 and earlier it was effectively a no-go to intern due to PermGen issues

End of Daily Log

The other logs are at http://esplins.org/hash_alfresco