<?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: How process failover is handled on single nodes in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-process-failover-is-handled-on-single-nodes/m-p/165122#M118830</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Activiti commits the database transaction when it reaches a wait state (like a user task or an asynchronous task) or when the process is ended. So in your example the 5th task is executed in the same transaction as the 4th asynchronous task. Because the node goes down, this database transaction is not committed and the database state is still in the 4th asynchronous task. When the Activiti Engine is started again, the job executor will poll for remaining jobs to be executed and the process instance will continue again from the 4th task.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you mean with failed processes, failed jobs then we have a JobQuery that you can use to query on these failed jobs.&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>Tue, 26 Nov 2013 08:27:42 GMT</pubDate>
    <dc:creator>trademak</dc:creator>
    <dc:date>2013-11-26T08:27:42Z</dc:date>
    <item>
      <title>How process failover is handled on single nodes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-process-failover-is-handled-on-single-nodes/m-p/165121#M118829</link>
      <description>I have seen the http://forums.activiti.org/content/process-failover-cluster thread, but I am a little curious as to how failover works on a single node. Let's say that I have a process with 9 service tasks. I make the 1st, 4th and 7th service tasks asynchronous. Let's say that the 5th task is about</description>
      <pubDate>Mon, 25 Nov 2013 19:31:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-process-failover-is-handled-on-single-nodes/m-p/165121#M118829</guid>
      <dc:creator>hiravgandhi</dc:creator>
      <dc:date>2013-11-25T19:31:42Z</dc:date>
    </item>
    <item>
      <title>Re: How process failover is handled on single nodes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-process-failover-is-handled-on-single-nodes/m-p/165122#M118830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Activiti commits the database transaction when it reaches a wait state (like a user task or an asynchronous task) or when the process is ended. So in your example the 5th task is executed in the same transaction as the 4th asynchronous task. Because the node goes down, this database transaction is not committed and the database state is still in the 4th asynchronous task. When the Activiti Engine is started again, the job executor will poll for remaining jobs to be executed and the process instance will continue again from the 4th task.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you mean with failed processes, failed jobs then we have a JobQuery that you can use to query on these failed jobs.&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>Tue, 26 Nov 2013 08:27:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-process-failover-is-handled-on-single-nodes/m-p/165122#M118830</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2013-11-26T08:27:42Z</dc:date>
    </item>
  </channel>
</rss>

