topic Deployment fails when Intermediate Event is waiting for same message as start message in Alfresco Archive

Deployment fails when Intermediate Event is waiting for same message as start message

jakobtonn — Thu, 13 Nov 2014 07:59:00 GMT

According to the Activiti User Guide, only the IDs of start messages for processes should be unique over all process definitions. In our scenario (using Activiti 5.16.4), we have the situation that a currently running process instance is waiting for an intermediate or boundary message event. When we

Re: Deployment fails when Intermediate Event is waiting for same message as start message

martin_grofcik — Thu, 13 Nov 2014 08:13:31 GMT

Hi Jakob,

Thank you for the detailed description.
you are right


          // look for subscriptions for the same name in db:
          List<EventSubscriptionEntity> subscriptionsForSameMessageName = commandContext
            .getEventSubscriptionEntityManager()
            .findEventSubscriptionsByName(MessageEventHandler.EVENT_HANDLER_TYPE, 
              eventDefinition.getEventName(), processDefinition.getTenantId());

If you think it is a bug create jira ticket or even better pull request.

Regards
Martin

Re: Deployment fails when Intermediate Event is waiting for same message as start message

jakobtonn — Thu, 13 Nov 2014 08:37:26 GMT

Thank you Martin,
I have now created a JIRA ticket for this bug: http://jira.codehaus.org/browse/ACT-2151
Depending on my workload, I might be able to fix the problem myself and create a pull request, but right now I cannot make any promises.

Best regards,
Jakob