<?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: Record in ACT_HI_ACTINST was rollback in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/record-in-act-hi-actinst-was-rollback/m-p/172682#M125884</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The row in ACT_RU_EXECUTION represent the ongoing execution, this is there from the moment the process (or parallel path) has been started. Once a job fails, ALL modifications to the database (including creating ACT_HI_ACTINST entries and altering the ACT_RU_EXECUTION state) are rolled back. So there are no entries in ACT_HI_ACTINST because, from an engine/db perspective, those were never executed successfully.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So failing executions of any activity will NOT be marked in the history, as it never really happened. The only way to find out, is by inspecting the ACT_RU_JOB entity that is responsible for running the asynchronous task, which has zero retries left. In case you're using JTA or integrating with your own app's domain-entities, the changes to those entities that are done during the "failed" execution will also be rolled back.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Jan 2014 12:34:23 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2014-01-09T12:34:23Z</dc:date>
    <item>
      <title>Record in ACT_HI_ACTINST was rollback</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/record-in-act-hi-actinst-was-rollback/m-p/172681#M125883</link>
      <description>Dear Activiti Developer,In the workflow definition, we configure the ServiceTask with asynchronous to true.There is a few ExecutionListener configured in the ServiceTask, and one of the execution listener executed with exception. After the default retries 3 times, I check DB, there is no record crea</description>
      <pubDate>Thu, 09 Jan 2014 12:13:39 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/record-in-act-hi-actinst-was-rollback/m-p/172681#M125883</guid>
      <dc:creator>shanegirl</dc:creator>
      <dc:date>2014-01-09T12:13:39Z</dc:date>
    </item>
    <item>
      <title>Re: Record in ACT_HI_ACTINST was rollback</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/record-in-act-hi-actinst-was-rollback/m-p/172682#M125884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The row in ACT_RU_EXECUTION represent the ongoing execution, this is there from the moment the process (or parallel path) has been started. Once a job fails, ALL modifications to the database (including creating ACT_HI_ACTINST entries and altering the ACT_RU_EXECUTION state) are rolled back. So there are no entries in ACT_HI_ACTINST because, from an engine/db perspective, those were never executed successfully.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So failing executions of any activity will NOT be marked in the history, as it never really happened. The only way to find out, is by inspecting the ACT_RU_JOB entity that is responsible for running the asynchronous task, which has zero retries left. In case you're using JTA or integrating with your own app's domain-entities, the changes to those entities that are done during the "failed" execution will also be rolled back.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jan 2014 12:34:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/record-in-act-hi-actinst-was-rollback/m-p/172682#M125884</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2014-01-09T12:34:23Z</dc:date>
    </item>
  </channel>
</rss>

