Petals SE Activiti

NPE on event listener about service task started event

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.5.0
  • Fix Version/s: 0.9.0
  • Component/s: Process service
  • Security Level: Public
  • Description:
    Hide

    The following NPE occurs in the processing of the Activiti event listener associated to the service task started event:

    2015/05/26 14:36:24,555 GMT+0200 WARNING [org.activiti.engine.delegate.event.impl.ActivitiEventSupport] : Exception while executing event-listener, which was ignored
java.lang.NullPointerException
	at org.ow2.petals.activitibpmn.event.ProcessInstanceCompletedEventListener.createLogData(ProcessInstanceCompletedEventListener.java:55)
	at org.ow2.petals.activitibpmn.event.AbstractMonitLoggerEventListener.processEvent(AbstractMonitLoggerEventListener.java:47)
	at org.ow2.petals.activitibpmn.event.AbstractEventListener.onEvent(AbstractEventListener.java:56)
	at org.activiti.engine.delegate.event.impl.ActivitiEventSupport.dispatchEvent(ActivitiEventSupport.java:105)
	at org.activiti.engine.delegate.event.impl.ActivitiEventSupport.dispatchEvent(ActivitiEventSupport.java:98)
	at org.activiti.engine.delegate.event.impl.ActivitiEventDispatcherImpl.dispatchEvent(ActivitiEventDispatcherImpl.java:65)
	at org.activiti.engine.impl.pvm.runtime.AtomicOperationActivityEnd.eventNotificationsCompleted(AtomicOperationActivityEnd.java:74)
        ...
    Show
    The following NPE occurs in the processing of the Activiti event listener associated to the service task started event: 
    2015/05/26 14:36:24,555 GMT+0200 WARNING [org.activiti.engine.delegate.event.impl.ActivitiEventSupport] : Exception while executing event-listener, which was ignored
java.lang.NullPointerException
	at org.ow2.petals.activitibpmn.event.ProcessInstanceCompletedEventListener.createLogData(ProcessInstanceCompletedEventListener.java:55)
	at org.ow2.petals.activitibpmn.event.AbstractMonitLoggerEventListener.processEvent(AbstractMonitLoggerEventListener.java:47)
	at org.ow2.petals.activitibpmn.event.AbstractEventListener.onEvent(AbstractEventListener.java:56)
	at org.activiti.engine.delegate.event.impl.ActivitiEventSupport.dispatchEvent(ActivitiEventSupport.java:105)
	at org.activiti.engine.delegate.event.impl.ActivitiEventSupport.dispatchEvent(ActivitiEventSupport.java:98)
	at org.activiti.engine.delegate.event.impl.ActivitiEventDispatcherImpl.dispatchEvent(ActivitiEventDispatcherImpl.java:65)
	at org.activiti.engine.impl.pvm.runtime.AtomicOperationActivityEnd.eventNotificationsCompleted(AtomicOperationActivityEnd.java:74)
        ...
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 26 May 2015 - 14:35:00 +0200 - edited

This problem occurs when a service task just follows the start event of the process definition.

See the Activiti thread to get more information: http://forums.activiti.org/comment/29475.

So, a workaround to this problem is to force the use of activiti:async="true" of the service task. We are thinking that is not the right way to solve the problem because the process definition has not to be fixed for a technical problem. We are thinking that the variables should be added to the fired event on the Activiti engine side.

Show
Christophe DENEUX added a comment - Tue, 26 May 2015 - 14:35:00 +0200 - edited This problem occurs when a service task just follows the start event of the process definition. See the Activiti thread to get more information: http://forums.activiti.org/comment/29475. So, a workaround to this problem is to force the use of activiti:async="true" of the service task. We are thinking that is not the right way to solve the problem because the process definition has not to be fixed for a technical problem. We are thinking that the variables should be added to the fired event on the Activiti engine side.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:13:32 +0200

Another solution was proposed by Activiti team: The attribute 'activiti:async="true"' can be force programmatically using a post BpmnParseHandler.
This proposition works fine. The user documentation should be updated to tell that at least one async job executor is required to process these asynchronous service tasks.

Show
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:13:32 +0200 Another solution was proposed by Activiti team: The attribute 'activiti:async="true"' can be force programmatically using a post BpmnParseHandler. This proposition works fine. The user documentation should be updated to tell that at least one async job executor is required to process these asynchronous service tasks.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:15:26 +0200 - edited

Fixed in branch PETALSSEACTIVITI-4. To merge in branch petals-4.3.x and master.

Show
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:15:26 +0200 - edited Fixed in branch PETALSSEACTIVITI-4. To merge in branch petals-4.3.x and master.
Hide
Permalink
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:57:38 +0200

Merged in petals-4.3.x

Show
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:57:38 +0200 Merged in petals-4.3.x
Hide
Permalink
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:57:51 +0200

Merged in master

Show
Christophe DENEUX added a comment - Mon, 8 Jun 2015 - 11:57:51 +0200 Merged in master

People

Dates

  • Created:
    Tue, 26 May 2015 - 14:33:36 +0200
    Updated:
    Fri, 5 Aug 2016 - 12:02:11 +0200
    Resolved:
    Mon, 8 Jun 2015 - 11:57:38 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.