<?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 High Availability Behavior in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/high-availability-behavior/m-p/223030#M176160</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;SPAN&gt;I am testing activiti in high availability scenario (two activiti web apps with activiti engines and only one DB).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;During the tests I observe that if one of the engines takes a task for execution the task (job) is locked in the DB. Then I kill the engine OS process that locked the job. I observe that the job is actually marked as unprocessed and unlocked only after 5 minutes (the default value of lockTimeInMillis as I see in other topics). Only then another engine could take take the job for processing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So my question is whether there is any other mechanism by which the available activiti engines could 'see' that the acquired and locked in the DB job is not anymore processed by a dead engine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Dec 2015 15:53:24 GMT</pubDate>
    <dc:creator>nvulchev1</dc:creator>
    <dc:date>2015-12-16T15:53:24Z</dc:date>
    <item>
      <title>High Availability Behavior</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/high-availability-behavior/m-p/223030#M176160</link>
      <description>Hi,I am testing activiti in high availability scenario (two activiti web apps with activiti engines and only one DB).During the tests I observe that if one of the engines takes a task for execution the task (job) is locked in the DB. Then I kill the engine OS process that locked the job. I observe t</description>
      <pubDate>Wed, 16 Dec 2015 15:53:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/high-availability-behavior/m-p/223030#M176160</guid>
      <dc:creator>nvulchev1</dc:creator>
      <dc:date>2015-12-16T15:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability Behavior</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/high-availability-behavior/m-p/223031#M176161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No, that's currently the way it works. If you want to have like a heartbeat that updates that column when the heartbeat dies, that would be custom code.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Dec 2015 14:16:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/high-availability-behavior/m-p/223031#M176161</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2015-12-18T14:16:14Z</dc:date>
    </item>
  </channel>
</rss>

