[MGNLWORKFLOW-297] NullPointerException when serializing process under certain conditions Created: 23/Apr/15  Updated: 22/Jun/15  Resolved: 23/Apr/15

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.6, 5.5

Type: Bug Priority: Neutral
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: 5.3.9, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

A NullPointerException was thrown when aborting a failed publication. This also happened when following the email notification sample with the former workflow version.

The fix is to make sure that org.jbpm.persistence.processinstance.JcrSignalManager.SignalAction and org.jbpm.persistence.processinstance.JcrSignalManager.SignalProcessInstanceAction don't just return null as they do in the jBPM implementation. Why this is needed, I don't know.. possibly just circumventing some weird bug in jBPM?


Generated at Mon Feb 12 10:08:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.