Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2565

New Designer for case mng leads to NPE while solveVariable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • 7.5.1.GA
    • jBPM Designer

    • local development env BC and kieserver in EAP

    • Hide

      Here the reproducer: https://gitlab.com/pam-issues/designer-case-mgm-npe

      there are 2 commits in the repository: the first failing design and then the legacy designer working properly.

      Steps:

      1. clone the repo
      2. git reset --hard 5d87c94
      3. mvn clean install
      4. install on the kieserver
      5. start the main-case
      6. perform the first "Triage" task (no matter the input)
      7. find out the error in the kieserver log
      8. git reset --hard e3aec30
      9. mvn install
      10. install on the kieserver
      11. start the main-case
      12. perform the first "Triage" task (no matter the input)
      13. no error is generated

      Show
      Here the reproducer: https://gitlab.com/pam-issues/designer-case-mgm-npe there are 2 commits in the repository: the first failing design and then the legacy designer working properly. Steps: 1. clone the repo 2. git reset --hard 5d87c94 3. mvn clean install 4. install on the kieserver 5. start the main-case 6. perform the first "Triage" task (no matter the input) 7. find out the error in the kieserver log 8. git reset --hard e3aec30 9. mvn install 10. install on the kieserver 11. start the main-case 12. perform the first "Triage" task (no matter the input) 13. no error is generated

      I designed a simple case using a the new designer.
      Completing the first task, I got the following error:

      11:00:09,702 ERROR [org.jbpm.runtime.manager.impl.error.ExecutionErrorHandlerImpl] (default task-3) Unexpected error during processing : java.lang.NullPointerException
	at java.util.regex.Matcher.getTextLength(Matcher.java:1283)
	at java.util.regex.Matcher.reset(Matcher.java:309)
	at java.util.regex.Matcher.<init>(Matcher.java:229)
	at java.util.regex.Pattern.matcher(Pattern.java:1093)
	at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.resolveVariable(WorkflowProcessInstanceImpl.java:712)
	at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.lambda$getResolver$0(WorkflowProcessInstanceImpl.java:677)
	at org.jbpm.workflow.core.node.DynamicNode.acceptsEvent(DynamicNode.java:43)
	at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:616)
	at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.completeWorkItem(JPAWorkItemManager.java:167)
	at org.drools.core.command.runtime.process.CompleteWorkItemCommand.execute(CompleteWorkItemCommand.java:75)

      From my understanding this is caused evaluating a dynamic task that is not present in the equivalent BPMN coming from legacy designer.

      I'm not sure if the new designer introduce a faulty element or if the runtime is not able to handle a correct definition.

              romartin@redhat.com Roger Martinez
              dmarrazz@redhat.com Donato Marrazzo
              Kirill Gaevskii Kirill Gaevskii
              Kirill Gaevskii Kirill Gaevskii
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: