topic Re: Error waking up a receice task with a boundary timer event in Alfresco Archive

Error waking up a receice task with a boundary timer event

danilo1 — Fri, 18 Oct 2013 07:40:15 GMT

Hi,In my process I have a Receive Task that wait for an external signal made by activiti rest api.It works fine, but If I associate to that task a boundary timer to simulate a timeout:- if the timer fires is ok calling the next task,- if the signal arrives before the timeout an internal exception is

Re: Error waking up a receice task with a boundary timer event

danilo1 — Fri, 18 Oct 2013 14:38:38 GMT

Seems that when the timer is attached to the receive task lose the capability of intercept the signal.

In fact if the signal is sent before the timeout, activiti raise the "internal error" and then calls however the "timeout task".

Re: Error waking up a receice task with a boundary timer event

jbarrez — Mon, 21 Oct 2013 11:08:43 GMT

That sounds like a bug. Which exception do you get?

Re: Error waking up a receice task with a boundary timer event

danilo1 — Mon, 21 Oct 2013 15:37:37 GMT

I am using rest-api and the returned message (after the http call) is : {"errorMessage":"Internal Server Error","statusCode":500}.
The I am working with the original rest-api.war (5.13) and I do not know how I can produce a more verbose log. The modification of the log4j.properties have do not made any effect.

Re: Error waking up a receice task with a boundary timer event

danilo1 — Tue, 22 Oct 2013 12:17:29 GMT

Update:
I have investigated about the problem, so I got the sources, put a a try/catch in ExecutionActionRequest ( called by rest-api ) and then recompiled the activiti-rest package.

The outcome exception is a NullPointerException raised in the ExecutionEntity.signal(String signalName, Object signalData) method : the activiti attribute is set to null.

The modified ExecutionActionRequest rows (version 5.13)
<code>
@Put
public ExecutionResponse performExecutionAction(ExecutionActionRequest actionRequest) {
    if(!authenticate()) {
      return null;
    }

    Execution execution = getExecutionFromRequest();

    if(ExecutionActionRequest.ACTION_SIGNAL.equals(actionRequest.getAction())) {
try{ //<————— ADDED BY ME
        ActivitiUtil.getRuntimeService().signal(execution.getId());
}catch (Throwable e){ //<————— ADDED BY ME
if( execution == null ) //<————— ADDED BY ME
   System.out.println( "execution ==null" ); //<————— ADDED BY ME
e.printStackTrace(); //<————— ADDED BY ME
} //<————— ADDED BY ME
    } else if(ExecutionActionRequest.ACTION_SIGNAL_EVENT_RECEIVED.equals(actionRequest.getAction())) {
……………
</code>

And the outcome stack trace
<code>
java.lang.NullPointerException
org.activiti.engine.impl.persistence.entity.ExecutionEntity.signal(ExecutionEntity.java:348)
org.activiti.engine.impl.cmd.SignalCmd.execute(SignalCmd.java:45)
org.activiti.engine.impl.cmd.NeedsActiveExecutionCmd.execute(NeedsActiveExecutionCmd.java:55)
org.activiti.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:24)
org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:61)
org.activiti.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:42)
org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130)
org.activiti.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:40)
org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:37)
org.activiti.engine.impl.RuntimeServiceImpl.signal(RuntimeServiceImpl.java:184)
org.activiti.rest.api.runtime.process.ExecutionResource.performExecutionAction(ExecutionResource.java:50)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.restlet.resource.ServerResource.doHandle(ServerResource.java:449)
org.restlet.resource.ServerResource.put(ServerResource.java:1173)
org.restlet.resource.ServerResource.doHandle(ServerResource.java:524)
org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:590)
org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:302)
org.restlet.resource.ServerResource.handle(ServerResource.java:849)
org.restlet.resource.Finder.handle(Finder.java:513)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Router.doHandle(Router.java:500)
org.restlet.routing.Router.handle(Router.java:740)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:155)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.engine.ChainHelper.handle(ChainHelper.java:114)
org.restlet.engine.application.ApplicationHelper.handle(ApplicationHelper.java:75)
org.restlet.Application.handle(Application.java:391)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Router.doHandle(Router.java:500)
org.restlet.routing.Router.handle(Router.java:740)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.routing.Router.doHandle(Router.java:500)
org.restlet.routing.Router.handle(Router.java:740)
org.restlet.routing.Filter.doHandle(Filter.java:159)
org.restlet.routing.Filter.handle(Filter.java:206)
org.restlet.engine.ChainHelper.handle(ChainHelper.java:114)
org.restlet.Component.handle(Component.java:391)
org.restlet.Server.handle(Server.java:491)
org.restlet.engine.ServerHelper.handle(ServerHelper.java:74)
org.restlet.engine.http.HttpServerHelper.handle(HttpServerHelper.java:153)
org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1031)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
java.lang.Thread.run(Thread.java:662)
</code>

Re: Error waking up a receice task with a boundary timer event

chkal — Thu, 10 Apr 2014 12:26:47 GMT

Any news on this one? I'm running into the same issue in 5.13.1. So basically sending a signal to the execution fails with a NPE as described above. But only if a boundary timer is attached to the receive task.

Re: Error waking up a receice task with a boundary timer event

frederikherema1 — Tue, 22 Apr 2014 10:21:46 GMT

In case a boundary-event is attached to the receive-task, an additional execution is created under the hood (add scoping is needed for the boundary-event). So you should make sure you signal that child-execution, instead of the parent (== the execution you whould normally use to signal if no boundary is attached).

Can you try the proposed solution and come back if this is not the solution?

Re: Error waking up a receice task with a boundary timer event

chkal — Wed, 23 Apr 2014 08:17:11 GMT

Thanks a lot for your response. You are absolutely right. I was sending the signal to the wrong execution which resulted in the NPE mentioned above.

Basically I was doing something like this:

<java>
Execution execution = runtimeService.createExecutionQuery()
.processInstanceBusinessKey( "foobar" )
.singleResult();

runtimeService.signal( execution.getId() );
</java>

I've changed it to something like this and now it works fine:

<java>
ProcessInstance processInstance = runtimeService.createProcessInstanceQuery()
.processInstanceBusinessKey( "foobar" )
.singleResult();

Execution execution = runtimeService.createExecutionQuery()
.processInstanceId( processInstance.getId() )
.activityId( "receiveActivityId" )
.singleResult();

runtimeService.signal( execution.getId() );
</java>

Thanks a lot for your help.

Re: Error waking up a receice task with a boundary timer event

jaikumar — Thu, 10 Jul 2014 07:15:05 GMT

Hi,

I have used receive task with timer boundary event, bu timer boundary event fires continuously, its not wait until the duration ends. In timer event I have set value as PT10M for repeated every 10 minutes it should fire. But firing continuously.

Re: Error waking up a receice task with a boundary timer event

trademak — Thu, 10 Jul 2014 10:07:12 GMT

Hi,

Could you provide a unit test showing your issue and create a JIRA issue with it?

Thanks,