Bug 1052131
| Summary: | NPE in server log when creating new rule | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Jiri Locker <jlocker> | ||||
| Component: | Business Central | Assignee: | manstis | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Locker <jlocker> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0.0 | CC: | etirelli, manstis, rrajasek | ||||
| Target Milestone: | ER1 | ||||||
| Target Release: | 6.0.1 | ||||||
| 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:58:34 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: |
|
||||||
Looking at the log, it does appear that this could be a synchronization issue. I added synchronization to the full and incremental build process for https://bugzilla.redhat.com/show_bug.cgi?id=1055632. Can you please re-check with your automated tests? I reproduced. Reopening... OK, I cannot reproduce with the current master branch following the commit for https://bugzilla.redhat.com/show_bug.cgi?id=1055632 to address the synchronization issues. Putting back to MODIFIED. Comment #2 related to CR2 (that does not contain the synchronization fix). The issue seems to be gone. |
Created attachment 849258 [details] server.log with NPE Description of problem: I am often seeing this exception after running certain automated tests. However it is hard to reproduce manually. After some experimenting, I am convinced it is caused by creating new resource while an incremental build is already running (or has been triggered shortly before creating the new resource). I have revealed two situation when this occurs: 1. creating a new resource (rule) immediately after changing project. This how it happens when I run automated tests. Couldn't reproduce manually. 2. creating new rules quickly in a loop. This the only way I have found to trigger the exception manually. See steps to reproduce. The exception can only be found in server log. I am unsure if it can affect the Business Central user. Version-Release number of selected component (if applicable): ER7 How reproducible: Hardly. Looks like a synchronization issue. Steps to Reproduce: 1. select any project 2. keep creating new rules repeatedly. Don't wait after submitting the Create new rule dialog, start creating new rule as soon as the dialog disappears. You have to be quick -- make sure you just hit a few random keys when typing the rule name. Actual results: NPE in server log. Expected results: It shouldn't happen. Additional info: