<?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: Logging of service tasks in  DB issue in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223538#M176668</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;As I remember, all these subsequent service tasks will be handled in a single transaction for performance reasons that's why you don't see in the DB the progress.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;if you want to demarcate the transactions even more granular then you have to use async flag for your tasks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Probably you need a new transaction for every service in the flow and catch all exception.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Dec 2015 10:32:35 GMT</pubDate>
    <dc:creator>vasile_dirla</dc:creator>
    <dc:date>2015-12-21T10:32:35Z</dc:date>
    <item>
      <title>Logging of service tasks in  DB issue</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223537#M176667</link>
      <description>I have number of service tasks which executes in a sequential order. In normal scenario when there are no exceptions in any of the service tasks, on completing all the tasks I can see the steps logged in the database with Process Instance ID, Start Time, End Time etc for each Service Tasks.But when</description>
      <pubDate>Fri, 18 Dec 2015 07:07:52 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223537#M176667</guid>
      <dc:creator>abhilashs</dc:creator>
      <dc:date>2015-12-18T07:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: Logging of service tasks in  DB issue</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223538#M176668</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;As I remember, all these subsequent service tasks will be handled in a single transaction for performance reasons that's why you don't see in the DB the progress.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;if you want to demarcate the transactions even more granular then you have to use async flag for your tasks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Probably you need a new transaction for every service in the flow and catch all exception.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Dec 2015 10:32:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223538#M176668</guid>
      <dc:creator>vasile_dirla</dc:creator>
      <dc:date>2015-12-21T10:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: Logging of service tasks in  DB issue</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223539#M176669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Abhilash, &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Instead of handling the exception, throw it to the function which is calling it. In this way, you get the exception out and you will have its details. I did the same and now I know where exactly the exception has occurred. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Hari&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jan 2016 11:57:40 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223539#M176669</guid>
      <dc:creator>hari</dc:creator>
      <dc:date>2016-01-04T11:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: Logging of service tasks in  DB issue</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223540#M176670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I mean if you are using a wrapper in between Activiti and your application, throwing the exception from the wrapper makes more sense. If there is no wrapper, when you get the exception, you can always log it to know where it has occurred. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Hari. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jan 2016 12:00:43 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/logging-of-service-tasks-in-db-issue/m-p/223540#M176670</guid>
      <dc:creator>hari</dc:creator>
      <dc:date>2016-01-04T12:00:43Z</dc:date>
    </item>
  </channel>
</rss>

