<?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: Concurrent signals to same process instance. in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/concurrent-signals-to-same-process-instance/m-p/235406#M188536</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I don't think there's an easy solution for this, except putting a queue in front of the receive task …&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The thing is, on the lowest level, you've got two transactions trying to do the same thing, and one wins … leading to the optimistic locking exception … that's fundamental to Activiti and not easy to circumvent.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Jan 2016 09:11:51 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2016-01-25T09:11:51Z</dc:date>
    <item>
      <title>Concurrent signals to same process instance.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/concurrent-signals-to-same-process-instance/m-p/235405#M188535</link>
      <description>HiI have a process that makes heavy use of the camel integration within activiti. I have a process that waits on a receive task for a message to come in via Camel, does some processing on the event, then loops back around to the receive activity and waits for the next message. The activity after the</description>
      <pubDate>Sat, 23 Jan 2016 14:00:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/concurrent-signals-to-same-process-instance/m-p/235405#M188535</guid>
      <dc:creator>mhanrahan</dc:creator>
      <dc:date>2016-01-23T14:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: Concurrent signals to same process instance.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/concurrent-signals-to-same-process-instance/m-p/235406#M188536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I don't think there's an easy solution for this, except putting a queue in front of the receive task …&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The thing is, on the lowest level, you've got two transactions trying to do the same thing, and one wins … leading to the optimistic locking exception … that's fundamental to Activiti and not easy to circumvent.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jan 2016 09:11:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/concurrent-signals-to-same-process-instance/m-p/235406#M188536</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-01-25T09:11:51Z</dc:date>
    </item>
  </channel>
</rss>

