<?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: Timeouts on servicetask in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/timeouts-on-servicetask/m-p/12633#M5182</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Tom,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You are right, the boundry timer-event won't be fired since it never ends up in the DB for the jobexecutor to pick up. So putting a timer on a non-waitstate in activiti is quite useless.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You could work around this using some subprocess and waitstate-magic I guess, but seems best to handle this in your service-code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once asyncronous continuations are available in activiti, the boundry timer would work, if the service-task is execute asynchronously (timer will be comitted). But currently no concrete timing on that, so I'd stick with the Java-solution.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Feb 2011 13:09:06 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2011-02-25T13:09:06Z</dc:date>
    <item>
      <title>Timeouts on servicetask</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timeouts-on-servicetask/m-p/12632#M5181</link>
      <description>I'm using a servicetask to call some bussiness logic (using Spring beans).Suppose that for some reason or another the Java code hangs (doesn't respond anymore, no exception is thrown). Can I handle this in the Activiti flow ?I tried it using a bounderyEvent with a timer but doesn't seem to work beca</description>
      <pubDate>Fri, 25 Feb 2011 12:20:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timeouts-on-servicetask/m-p/12632#M5181</guid>
      <dc:creator>stroobat</dc:creator>
      <dc:date>2011-02-25T12:20:59Z</dc:date>
    </item>
    <item>
      <title>Re: Timeouts on servicetask</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timeouts-on-servicetask/m-p/12633#M5182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Tom,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You are right, the boundry timer-event won't be fired since it never ends up in the DB for the jobexecutor to pick up. So putting a timer on a non-waitstate in activiti is quite useless.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You could work around this using some subprocess and waitstate-magic I guess, but seems best to handle this in your service-code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once asyncronous continuations are available in activiti, the boundry timer would work, if the service-task is execute asynchronously (timer will be comitted). But currently no concrete timing on that, so I'd stick with the Java-solution.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Feb 2011 13:09:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timeouts-on-servicetask/m-p/12633#M5182</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2011-02-25T13:09:06Z</dc:date>
    </item>
  </channel>
</rss>

