<?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: Clustering Activiti in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6884#M1689</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You don't have to do anything for that.&amp;nbsp; Maybe we should document that &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Activiti uses optimistic locking on the DB to deal with concurrency.&amp;nbsp; So it leverages the DB capabilities for the hard work of concurrency control.&amp;nbsp; DB's are optimised for that.&amp;nbsp; That works just the same from 2 threads from the same ProcessEngine as from 2 threads on different ProcessEngines on different machines.&amp;nbsp; It's most efficient if you configure the JobExecutor only on one machine.&amp;nbsp; That prevents that multiple JobExecutors compete for the same jobs resulting in unnecessary optimistic locking failures.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But we don't have a lot of QA/CI for this yet.&amp;nbsp; We only tested proper operation of the optimistic locking exceptions by controlling individual threads from the unit test thread.&amp;nbsp; We hope to expand this soon to full load and stress testing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you experiment with this, let us know your findings.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Dec 2010 07:02:51 GMT</pubDate>
    <dc:creator>tombaeyens</dc:creator>
    <dc:date>2010-12-02T07:02:51Z</dc:date>
    <item>
      <title>Clustering Activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6883#M1688</link>
      <description>In looking over the documentation, does Activiti have built in capabilities for clustering?&amp;nbsp;&amp;nbsp; If so, how do to configure it.Thanks in advance</description>
      <pubDate>Wed, 01 Dec 2010 15:08:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6883#M1688</guid>
      <dc:creator>kenyoung</dc:creator>
      <dc:date>2010-12-01T15:08:12Z</dc:date>
    </item>
    <item>
      <title>Re: Clustering Activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6884#M1689</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You don't have to do anything for that.&amp;nbsp; Maybe we should document that &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Activiti uses optimistic locking on the DB to deal with concurrency.&amp;nbsp; So it leverages the DB capabilities for the hard work of concurrency control.&amp;nbsp; DB's are optimised for that.&amp;nbsp; That works just the same from 2 threads from the same ProcessEngine as from 2 threads on different ProcessEngines on different machines.&amp;nbsp; It's most efficient if you configure the JobExecutor only on one machine.&amp;nbsp; That prevents that multiple JobExecutors compete for the same jobs resulting in unnecessary optimistic locking failures.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But we don't have a lot of QA/CI for this yet.&amp;nbsp; We only tested proper operation of the optimistic locking exceptions by controlling individual threads from the unit test thread.&amp;nbsp; We hope to expand this soon to full load and stress testing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you experiment with this, let us know your findings.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 07:02:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6884#M1689</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-12-02T07:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: Clustering Activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6885#M1690</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;created &lt;/SPAN&gt;&lt;A href="http://jira.codehaus.org/browse/ACT-417" rel="nofollow noopener noreferrer"&gt;http://jira.codehaus.org/browse/ACT-417&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 07:04:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6885#M1690</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-12-02T07:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: Clustering Activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6886#M1691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We use quartz in a similar fashion.&amp;nbsp; I'll test and report back if I have issues.&amp;nbsp; Thank you.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 13:13:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/clustering-activiti/m-p/6886#M1691</guid>
      <dc:creator>kenyoung</dc:creator>
      <dc:date>2010-12-02T13:13:21Z</dc:date>
    </item>
  </channel>
</rss>

