<?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 Re: Timer implementation clarification... in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35062#M18390</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;you should be able to run the job executor on multiple nodes as well.&amp;nbsp; but we don't have test coverage for that yet.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Jan 2011 08:23:45 GMT</pubDate>
    <dc:creator>tombaeyens</dc:creator>
    <dc:date>2011-01-06T08:23:45Z</dc:date>
    <item>
      <title>Timer implementation clarification...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35060#M18388</link>
      <description>I was wondering if there is some documentation that can explain more details on how timers are implemented. Specifically, in the case of embedding activiti in a cluster, and a timer event expires, how is the event executed by the timer processes? And on what thread does it run on? What system is in</description>
      <pubDate>Wed, 05 Jan 2011 23:42:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35060#M18388</guid>
      <dc:creator>wolpert</dc:creator>
      <dc:date>2011-01-05T23:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: Timer implementation clarification...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35061#M18389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Timers events are executed using the JobExecutor, it has a pool of threads which it uses for this. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you want to run activiti clustered, the best thing to do is to have the JobExecutor only running on one or two node to minimize risk of OptimisticLockingExceptions.&amp;nbsp; A retry-mechanism is built in to have the job executed again after failure.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regarding clustering of activiti, in the very near future there will be documentation available on this topic.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jan 2011 08:08:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35061#M18389</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-01-06T08:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: Timer implementation clarification...</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35062#M18390</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;you should be able to run the job executor on multiple nodes as well.&amp;nbsp; but we don't have test coverage for that yet.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jan 2011 08:23:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timer-implementation-clarification/m-p/35062#M18390</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2011-01-06T08:23:45Z</dc:date>
    </item>
  </channel>
</rss>

