<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Activiti caching strategy / cache lifespan in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-caching-strategy-cache-lifespan/m-p/56222#M33943</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi there,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;while performing some performance measurements against our application I noticed that Activiti seems to utilize a kind of unexpected caching strategy: Retrieved objects seem to be cached only within a DbSqlSession (attached to a CommandContext) instead of a cache lifetime that spans a transaction (which I would have naively expected).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Even after fixing &lt;/SPAN&gt;&lt;A href="https://jira.codehaus.org/browse/ACT-1040" rel="nofollow noopener noreferrer"&gt;ACT-1040&lt;/A&gt;&lt;SPAN&gt; this causes multiple retrievals of the same TaskEntity within the same transaction when invoking multiple TaskService methods for the same task (e.g., getIdentityLinksForTask, getVariablesLocal, etc.).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is this intentional? Are there any recommendations how to extend the cache life-span to the complete transaction duration?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thilo&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Dec 2011 15:38:25 GMT</pubDate>
    <dc:creator>thilo_ginkel</dc:creator>
    <dc:date>2011-12-22T15:38:25Z</dc:date>
    <item>
      <title>Activiti caching strategy / cache lifespan</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-caching-strategy-cache-lifespan/m-p/56222#M33943</link>
      <description>Hi there,while performing some performance measurements against our application I noticed that Activiti seems to utilize a kind of unexpected caching strategy: Retrieved objects seem to be cached only within a DbSqlSession (attached to a CommandContext) instead of a cache lifetime that spans a trans</description>
      <pubDate>Thu, 22 Dec 2011 15:38:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-caching-strategy-cache-lifespan/m-p/56222#M33943</guid>
      <dc:creator>thilo_ginkel</dc:creator>
      <dc:date>2011-12-22T15:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti caching strategy / cache lifespan</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-caching-strategy-cache-lifespan/m-p/56223#M33944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;*bump*&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jan 2012 08:14:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-caching-strategy-cache-lifespan/m-p/56223#M33944</guid>
      <dc:creator>thilo_ginkel</dc:creator>
      <dc:date>2012-01-09T08:14:27Z</dc:date>
    </item>
  </channel>
</rss>

