<?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: Error Handling in MultiInstance parallel Subprocess in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/error-handling-in-multiinstance-parallel-subprocess/m-p/96832#M66575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you don't specify the "async=true", the calling thead (your app thread that calls the activiti API) will be used to make the process flow. if one of the 4 paths cause an error during this flow, the whole transaction is rolled back and the calling thread gets an Exception. It's up to your app to handle it than.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you use "async=true" on the subprocesses, they will be executed asynchronously. The calling thread will return immediately, and the only way of knowing something went wrong is to check the process afterwards. Indeed, failed jobs will be available in the job-table. In case you retry the job, only the failed execution will be retried again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;On top of that, only WHEN ALL of the 4 async executions have succeeded (either instantly or after retry), the process will continue with the steps after this.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Sep 2012 14:10:38 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2012-09-27T14:10:38Z</dc:date>
    <item>
      <title>Error Handling in MultiInstance parallel Subprocess</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/error-handling-in-multiinstance-parallel-subprocess/m-p/96831#M66574</link>
      <description>Hi,I need to handle technical exceptions, for ex: remote server host is down while making a webservice call, inside multi instance parallel subprocess.For ex: Subprocess is executed on list of 4 items. I have a webservice call inside the subprocess logic. Hence all these 4 execution paths will make</description>
      <pubDate>Tue, 21 Aug 2012 09:45:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/error-handling-in-multiinstance-parallel-subprocess/m-p/96831#M66574</guid>
      <dc:creator>riddhishah1604</dc:creator>
      <dc:date>2012-08-21T09:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: Error Handling in MultiInstance parallel Subprocess</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/error-handling-in-multiinstance-parallel-subprocess/m-p/96832#M66575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you don't specify the "async=true", the calling thead (your app thread that calls the activiti API) will be used to make the process flow. if one of the 4 paths cause an error during this flow, the whole transaction is rolled back and the calling thread gets an Exception. It's up to your app to handle it than.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you use "async=true" on the subprocesses, they will be executed asynchronously. The calling thread will return immediately, and the only way of knowing something went wrong is to check the process afterwards. Indeed, failed jobs will be available in the job-table. In case you retry the job, only the failed execution will be retried again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;On top of that, only WHEN ALL of the 4 async executions have succeeded (either instantly or after retry), the process will continue with the steps after this.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2012 14:10:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/error-handling-in-multiinstance-parallel-subprocess/m-p/96832#M66575</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-09-27T14:10:38Z</dc:date>
    </item>
  </channel>
</rss>

