<?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: Scalability of the Activiti Engine in an Enterprise environment in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152413#M107064</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1) Don't think there is another approach, other than having a process with a service-task in it (with async=true) that starts any number of instances, using the EngineServices. Due to the fact that the activity is async, this will be run in the job-executor, and not using the thread that actually starts this "special" process.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Not sure if it's related to 1, but you could have multiple of these processes, spawining batches of lat's say 100 processes each time, perhaps using sequential multi-instance with timeouts in between?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Activiti uses a transaction when executing a process. So when VM goes down, all pending transactions are rolled back and all processes are left in the state they were before the ongoing action.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Oct 2013 08:51:28 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2013-10-02T08:51:28Z</dc:date>
    <item>
      <title>Scalability of the Activiti Engine in an Enterprise environment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152412#M107063</link>
      <description>Hello All,I have a couple of questions related to the scalability of Activiti as follows:1) What is the best way to execute multiple process instances of a workflow? One good recommendation was from Joram in another post where he gave the usage of a Java ThreadPool executor with each thread starting</description>
      <pubDate>Thu, 26 Sep 2013 09:37:02 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152412#M107063</guid>
      <dc:creator>ambharath</dc:creator>
      <dc:date>2013-09-26T09:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: Scalability of the Activiti Engine in an Enterprise environment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152413#M107064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1) Don't think there is another approach, other than having a process with a service-task in it (with async=true) that starts any number of instances, using the EngineServices. Due to the fact that the activity is async, this will be run in the job-executor, and not using the thread that actually starts this "special" process.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Not sure if it's related to 1, but you could have multiple of these processes, spawining batches of lat's say 100 processes each time, perhaps using sequential multi-instance with timeouts in between?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Activiti uses a transaction when executing a process. So when VM goes down, all pending transactions are rolled back and all processes are left in the state they were before the ongoing action.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Oct 2013 08:51:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152413#M107064</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-10-02T08:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: Scalability of the Activiti Engine in an Enterprise environment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152414#M107065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello frederikheremans,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks for the answers - they've opened a new stream of thoughts in me &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I shall proceed in this direction!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A M Bharath&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Oct 2013 10:02:29 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/scalability-of-the-activiti-engine-in-an-enterprise-environment/m-p/152414#M107065</guid>
      <dc:creator>ambharath</dc:creator>
      <dc:date>2013-10-03T10:02:29Z</dc:date>
    </item>
  </channel>
</rss>

