<?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 to send signal in ReciveTask At Clustered Enviorment in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-to-send-signal-in-recivetask-at-clustered-enviorment/m-p/103120#M71856</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In case the second signal is called before the first signal thread returns (so when the signal's execution is still flowing), a second execution will be started indeed. But when the second execution tries to persist the process-state, it will receive a "ActivitiOptimisticLockException", rolling back all changes done.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unless, in the case the receive-task is at the end of the process (see &lt;/SPAN&gt;&lt;A href="https://jira.codehaus.org/browse/ACT-1259" rel="nofollow noopener noreferrer"&gt;https://jira.codehaus.org/browse/ACT-1259&lt;/A&gt;&lt;SPAN&gt;) but this is a bug…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One solution would be to make the stuff that happens AFTER the signal-task (eg. a service-taks that does some magic) be marked as async:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Disadvantage: the calling-thread that signals() the execution, will be returned, before the rest of the process is actually executed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Advantage: when an async-task is reached (and is only active execution), the process is persisted to the database BEFORE executing the actual stuff you wanted to do when signaled (the service task). This way, the second calling thread will get a ActivitiOptimisticLockException BEFORE it actually executed the servicetaks a second time.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Jun 2012 14:15:06 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2012-06-25T14:15:06Z</dc:date>
    <item>
      <title>How to send signal in ReciveTask At Clustered Enviorment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-send-signal-in-recivetask-at-clustered-enviorment/m-p/103119#M71855</link>
      <description>Hi, is there any way that i can control concurrency of signals that signal same activiti from different instances?When multiple signals send to recivetask, Multiple executions start.</description>
      <pubDate>Mon, 25 Jun 2012 13:34:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-send-signal-in-recivetask-at-clustered-enviorment/m-p/103119#M71855</guid>
      <dc:creator>er3n</dc:creator>
      <dc:date>2012-06-25T13:34:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to send signal in ReciveTask At Clustered Enviorment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-send-signal-in-recivetask-at-clustered-enviorment/m-p/103120#M71856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In case the second signal is called before the first signal thread returns (so when the signal's execution is still flowing), a second execution will be started indeed. But when the second execution tries to persist the process-state, it will receive a "ActivitiOptimisticLockException", rolling back all changes done.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unless, in the case the receive-task is at the end of the process (see &lt;/SPAN&gt;&lt;A href="https://jira.codehaus.org/browse/ACT-1259" rel="nofollow noopener noreferrer"&gt;https://jira.codehaus.org/browse/ACT-1259&lt;/A&gt;&lt;SPAN&gt;) but this is a bug…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One solution would be to make the stuff that happens AFTER the signal-task (eg. a service-taks that does some magic) be marked as async:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Disadvantage: the calling-thread that signals() the execution, will be returned, before the rest of the process is actually executed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Advantage: when an async-task is reached (and is only active execution), the process is persisted to the database BEFORE executing the actual stuff you wanted to do when signaled (the service task). This way, the second calling thread will get a ActivitiOptimisticLockException BEFORE it actually executed the servicetaks a second time.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jun 2012 14:15:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-send-signal-in-recivetask-at-clustered-enviorment/m-p/103120#M71856</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-06-25T14:15:06Z</dc:date>
    </item>
  </channel>
</rss>

