topic Re: Getting NullPointer exception when timer job fires in Alfresco Archive

Getting NullPointer exception when timer job fires

ganeshr — Wed, 17 Jul 2013 10:47:48 GMT

Hi, I have seen the following exception in log file,[2013-07-17 05:01:43,557][ERROR][pool-1-thread-41][impl.jobexecutor.TimerCatchIntermediateEventJobHandler][exception during timer execution]java.lang.NullPointerException at org.activiti.engine.impl.bpmn.behavior.AbstractBpmnActivityBehavior.has

Re: Getting NullPointer exception when timer job fires

frederikherema1 — Wed, 17 Jul 2013 12:37:52 GMT

Can you add your BPMN XML in a code-block?

Re: Getting NullPointer exception when timer job fires

ganeshr — Thu, 18 Jul 2013 07:46:38 GMT

Hi,

I have attached the BPMN xml code.

Re: Getting NullPointer exception when timer job fires

frederikherema1 — Thu, 18 Jul 2013 09:57:19 GMT

Seems like an issue with the execution the activity is waiting in. Probabily the inclusive gateway causing one of the executions the timers are no, to be "inactive". Don't really wee what you're trying to reach with the inclusive gateway. Why not use boundary-events for the time-alerts?

Re: Getting NullPointer exception when timer job fires

ganeshr — Thu, 18 Jul 2013 14:22:37 GMT

Initially I have used the boundary event but we are getting TimerEntity concurrent exception when we are trying to complete the task when timer job fires, because of this task complete operation is getting rollbacked. To avoid that we have used inclusive gateway and we are not getting that exception. Instead we are getting Null pointer exception but that it not causing the execution flow, I guess.

Re: Getting NullPointer exception when timer job fires

frederikherema1 — Fri, 19 Jul 2013 06:21:09 GMT

Completing the task when the timer fires seems to me to be an edge-case (off course, depending on the timeout). If the timeout of a task to be completed is a couple of hours or even days, the chance of the user completing the task when the job is being executed is very small. And if that happens, the ConcurrentModificationException should be handled by your code. In your specific use case it means the user was too late to complete the task, as it's expired already. You'll get similar issues with the inclusive layaway when both event occur, as they both try to update the same process-instance eventually.

Re: Getting NullPointer exception when timer job fires

ganeshr — Fri, 19 Jul 2013 12:03:05 GMT

Yes, there is a small chance that timer and task complete happen at the same time, but as we have 3 timer boundary events there is a chance that both task complete and one of the time fires at the same time. Problem with timer boundary events is that complete event is getting triggered even though the task complete operation is getting rollback when timer job fires at the same time. As we are sending the notification event as part of complete event, So notification is going even though complete operation is not completed. For that reason we have used the inclusive gateway and we are not facing this issue of complete operation getting rollback even though both fires at the same time, may be because of both are running with different execution id's, I guess.