Bug 1082111
| Summary: | NPE when sub-process handles an error code exception | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jim Rigsbee <jrigsbee> | ||||
| Component: | jBPM Core | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Svitak <jsvitak> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.1 | CC: | kverlaen, mbaluch, mswiders | ||||
| Target Milestone: | ER1 | ||||||
| Target Release: | 6.0.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 19:50:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
fixed on master, waiting for acks to backport jbpm master: https://github.com/droolsjbpm/jbpm/commit/bdc93de85e67a68c5fb9684eb4bf449f8b5e7323 backported to 6.0.x jbpm 6.0.x: https://github.com/droolsjbpm/jbpm/commit/3d6f837aff92d24aa643eeea3df16749918f118e Verified in BPMS 6.0.2.ER1. http://git.app.eng.bos.redhat.com/git/jbossqe/brms.git/commit/?id=c6a8c048f7c88e93a8c64db29f45b07af0212c24 |
Created attachment 879956 [details] Exception handling Maven project Description of problem: In the attached Maven project, an NPE is thrown after the sub-process successfully handles an exception thrown by the main process. Version-Release number of selected component (if applicable): 6.0.1.ER2 How reproducible: every time Steps to Reproduce: 1. unzip the Maven project 2. mvn clean test 3. Actual results: the second test will fail because an exception is thrown Expected results: test should pass with outcome = 90277 Additional info: In debugging, it appears the Action after the sub-process end event is null. Maciej discovered it is caused by empty script tags within the event sub-process, which are not supported but should be. Another issue is with the setting the outcome when aborting the process instance from within an event in the subprocess, that does not happen as the outcome is set only by fault node which is error end event. It is desirable to have the outcome set to the error code processed.