Sending the signal to start a task that is in in Sub-process Adhoc, the task does not start - RHPAM

Solution Verified - Updated -

Issue

  • When sending the signal to start a task that is in in Sub-process Adhoc, the task does not start and is possible to see the following error
19:01:44,002 DEBUG [org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl] (EE-ManagedThreadFactory-default-Thread-1) Signal f087602f-1524-4922-9df7-c47236f20636 received with data null in process instance 22
19:01:44,002 WARN  [org.drools.persistence.PersistableRunner] (EE-ManagedThreadFactory-default-Thread-1) Could not commit session: java.lang.NullPointerException
    at deployment.ROOT.war//org.jbpm.workflow.instance.node.CompositeNodeInstance.useAsync(CompositeNodeInstance.java:438)
    at deployment.ROOT.war//org.jbpm.workflow.instance.node.CompositeNodeInstance.getNodeInstance(CompositeNodeInstance.java:271)
    at deployment.ROOT.war//org.jbpm.workflow.instance.node.AsyncEventNodeInstance.getFrom(AsyncEventNodeInstance.java:98)
    at deployment.ROOT.war//org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:414)
    at deployment.ROOT.war//org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:392)
    at deployment.ROOT.war//org.jbpm.workflow.instance.node.AsyncEventNodeInstance.triggerCompleted(AsyncEventNodeInstance.java:122)
    at deployment.ROOT.war//org.jbpm.workflow.instance.node.AsyncEventNodeInstance$AsyncExternalEventListener.signalEvent(AsyncEventNodeInstance.java:137)

Environment

  • Red Hat Process Automation Manager 7.10.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content