<?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 Boundary message event subscriptions removed when deploying new version. in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234381#M187511</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Scenario (version 6.0.0.Beta2) :&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Create new workflow with boundary message event on specific user task.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Create process instance, and activate above task (so subscription to message event comes in)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. Re-deploy new version of the workflow.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. Send message event.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;=&amp;gt; This results in the event subscription not being triggered due to following code being executed when re-deploying:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;org.activiti.engine.impl.bpmn.deployer.BpmnDeploymentHelper&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;public void updateTimersAndEvents(ProcessDefinitionEntity processDefinition, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProcessDefinitionEntity previousProcessDefinition, ParsedDeployment parsedDeployment) {&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; …&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; eventSubscriptionManager.removeObsoleteMessageEventSubscriptions(previousProcessDefinition);&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; …&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I understand that this is normal behavior for start message events. However I'm not sure about boundary message events. In our use case it shouldn't. I was hesitating to file this as a bug report since I'm not sure if this is expected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If this is expected, how can we work-around this issue?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jan 2016 18:49:29 GMT</pubDate>
    <dc:creator>wblancqu</dc:creator>
    <dc:date>2016-01-19T18:49:29Z</dc:date>
    <item>
      <title>Boundary message event subscriptions removed when deploying new version.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234381#M187511</link>
      <description>Scenario (version 6.0.0.Beta2) :1. Create new workflow with boundary message event on specific user task.2. Create process instance, and activate above task (so subscription to message event comes in)3. Re-deploy new version of the workflow.4. Send message event.=&amp;gt; This results in the event subsc</description>
      <pubDate>Tue, 19 Jan 2016 18:49:29 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234381#M187511</guid>
      <dc:creator>wblancqu</dc:creator>
      <dc:date>2016-01-19T18:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary message event subscriptions removed when deploying new version.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234382#M187512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hmm I think you are correct: for boundary message events it doesn't make sense to remove them (for start events it does), as in-flight process instances would be lost.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for doing the research already and pointing usin the right direction.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll investigate (and hopefully fix) and post back here.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2016 22:16:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234382#M187512</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-01-20T22:16:18Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary message event subscriptions removed when deploying new version.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234383#M187513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Joram,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any updates regarding this issue?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2016 18:17:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234383#M187513</guid>
      <dc:creator>wblancqu</dc:creator>
      <dc:date>2016-03-29T18:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Boundary message event subscriptions removed when deploying new version.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234384#M187514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The plan is to release a new version next week (most likely). both for 5.x and 6.x line.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Apr 2016 13:58:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/boundary-message-event-subscriptions-removed-when-deploying-new/m-p/234384#M187514</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-04-04T13:58:59Z</dc:date>
    </item>
  </channel>
</rss>

