Increase in cache-context.xml or ehcache-custom.xml

[loftux]

I'm getting this error

14:13:41,584 WARN  [org.alfresco.repo.cache.TransactionalCache.org.alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
14:13:58,579 WARN  [org.alfresco.repo.cache.TransactionalCache.org.alfresco.cache.node.propertiesTransactionalCache] Transactional update cache 'org.alfresco.cache.node.propertiesTransactionalCache' is full (5000).
14:14:20,832 WARN  [org.alfresco.repo.cache.TransactionalCache.org.alfresco.cache.node.aspectsTransactionalCache] Transactional update cache 'org.alfresco.cache.node.aspectsTransactionalCache' is full (10000).
‍‍‍‍

I can find these bean names in cache-context.xml, and thus create a custom-cache-context.xml. But is it this one to edit to resolve errors above, or should cache changes always be done in ehcach-custom.xml as per http://wiki.alfresco.com/wiki/Repository_Cache_Configuration

[jperilla]

We are getting the same errors. Is it safe to up these values?

11:23:18,698 User:wstephens WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:23:19,369 User:System INFO  [activities.feed.FeedTaskProcessor] >>> Generated 10 activity feed entries for 1 activity posts (in 8908 msecs)
11:23:42,848 User:jperilla WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:23:55,000 User:jperilla WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:23:58,230 User:jperilla WARN  [cache.node.propertiesTransactionalCache] Transactional update cache 'org.alfresco.cache.node.propertiesTransactionalCache' is full (5000).
11:24:43,049  INFO  [jodconverter.office.PooledOfficeManager] connection lost unexpectedly; attempting restart
11:25:04,359 User:wstephens WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:25:08,961 User:jperilla WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:25:11,925 User:jperilla WARN  [cache.node.propertiesTransactionalCache] Transactional update cache 'org.alfresco.cache.node.propertiesTransactionalCache' is full (5000).
11:25:58,009 User:dnichols WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:27:06,603 User:jperilla WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).
11:27:30,097 User:dnichols WARN  [alfresco.cache.contentDataTransactionalCache] Transactional update cache 'org.alfresco.cache.contentDataTransactionalCache' is full (1000).‍‍‍‍‍‍‍‍‍‍‍‍‍

[jperilla]

Oops I meant to say that our system runs slow when these errors are in the log. So it seems to be more than just a warning.

[sameer1sharma]

Hi,
    I am getting below error. I have gone through the website(http://wiki.alfresco.com/wiki/Repository_Cache_Configuration) and enabled ehcache debugging. Please let me know solution for it. In advance thank you.

10:44:55,207 User:admin ERROR [ehcache.store.DiskStore] org.alfresco.cache.ticketsCacheCache: Elements cannot be written to disk store because the spool thread has died.

[loftux]

Hi,
    I am getting below error. I have gone through the website(http://wiki.alfresco.com/wiki/Repository_Cache_Configuration) and enabled ehcache debugging. Please let me know solution for it. In advance thank you.

10:44:55,207 User:admin ERROR [ehcache.store.DiskStore] org.alfresco.cache.ticketsCacheCache: Elements cannot be written to disk store because the spool thread has died.

sammeer1sharma, please start a new thread instead, this is a different issue and you are more likely to get an answer if you do.