<?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: what is the best architecture? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/what-is-the-best-architecture/m-p/102273#M71144</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's really difficult to answer this question without all the context.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you go for option 2 and run Activiti embedded there should be no issue with running multiple Activiti Engines.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The only component that you have take into consideration is the job executor. If the job executor is active on multiple Activiti Engines it will poll for the same jobs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We implemented a locking strategy so that only one Engine is able to execute a job, so that's also fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You may get some exceptions because a job executor is accessing an already locked job, but that's on our todo list to change to a info message instead of the current log level.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Aug 2012 10:01:47 GMT</pubDate>
    <dc:creator>trademak</dc:creator>
    <dc:date>2012-08-29T10:01:47Z</dc:date>
    <item>
      <title>what is the best architecture?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/what-is-the-best-architecture/m-p/102272#M71143</link>
      <description>I'm considering using Activiti in one of my projects, but I'm a bit uncertain about the best architecture. Activiti basically is an active component. This means that when the environment triggers a "compete task", the workflow will move forward to the next task in the workflow, and possibly execute</description>
      <pubDate>Tue, 28 Aug 2012 11:48:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/what-is-the-best-architecture/m-p/102272#M71143</guid>
      <dc:creator>tbee</dc:creator>
      <dc:date>2012-08-28T11:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: what is the best architecture?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/what-is-the-best-architecture/m-p/102273#M71144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's really difficult to answer this question without all the context.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you go for option 2 and run Activiti embedded there should be no issue with running multiple Activiti Engines.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The only component that you have take into consideration is the job executor. If the job executor is active on multiple Activiti Engines it will poll for the same jobs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We implemented a locking strategy so that only one Engine is able to execute a job, so that's also fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You may get some exceptions because a job executor is accessing an already locked job, but that's on our todo list to change to a info message instead of the current log level.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Aug 2012 10:01:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/what-is-the-best-architecture/m-p/102273#M71144</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2012-08-29T10:01:47Z</dc:date>
    </item>
  </channel>
</rss>

