Bug 851484
Summary: | JBPM-3647 NullPointerException in jbpm-console when retrieving process definitions from guvnor | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Maciej Swiderski <mswiders> |
Component: | jBPM Console | Assignee: | Kris Verlaenen <kverlaen> |
Status: | VERIFIED --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | BRMS 5.3.0.GA | CC: | kverlaen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
A NullPointerException could occur when retrieving process definitions from the asset repository, which resulted in the process definitions not loading.
This has been resolved by ensuring the knowledge agent is null safe. The process definitions are now loaded without throwing a NullPointerException.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 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: |
Description
Maciej Swiderski
2012-08-24 09:53:35 UTC
backported into 5.2.x branch Could you please tell me a bit more about this? I'm not sure how to test this, since this is a bug reported for jBPM version 5.4.0-SNAPSHOT, if I understand correctly. I don't think I have seen this happen. Andrea Carpineti <acarpineti> made a comment on jira JBPM-3647 Affects Version/s: jBPM 5.3 Fix Version/s: jBPM 5.4 (In reply to comment #2) > Could you please tell me a bit more about this? I'm not sure how to test > this, since this is a bug reported for jBPM version 5.4.0-SNAPSHOT, if I > understand correctly. > I don't think I have seen this happen. As far as I remember it was reported as well for BRMS 5.3 after clean installation of 5.3.0.Final. It was not reproducable inall cases but I ran into it one or two times as well and that's why fix was applied. One thing you could try is to install fresh copy of brms standalone and after logging on go directly to processes pane and hit rifresh on process definitions directly to trigger package check. Hope this helps Using above mentioned method, I was able to reproduce with 5.3.0 version on 3rd try. With the current 5.3.1 build, this issue did not occur once in 10+ tries. I'd say verified. |