Bug 1318966 - Generic 'null' error after removing the last repository
Summary: Generic 'null' error after removing the last repository
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER2
: 6.3.0
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 09:29 UTC by Jiri Locker
Modified: 2020-03-27 19:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:13:16 UTC
Type: Bug

Attachments (Terms of Use)
Null error dialog (20.67 KB, image/png)
2016-03-18 09:29 UTC, Jiri Locker 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1319650 0 unspecified CLOSED NPE when open an Organization Unit that doesn't have a repository yet 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker GUVNOR-2459 0 None None None Never

Internal Links: 1319650

Description Jiri Locker 2016-03-18 09:29:00 UTC 
Created attachment 1137727 [details]
Null error dialog

Description of problem:
When I remove the last repository through Administration perspective, a modal error dialog is shown with the following message: "Unable to complete your request. The following exception occurred: null." The same error also appears each time I switch to Authoring perspective (when no repository exists).

No error found in server log so there is no stack trace.

Version-Release number of selected component (if applicable):
6.3.0.ER1

How reproducible:
-

Steps to Reproduce:
1. Delete all repositories in Administration perspective.
2. Navigate to Authoring perspective.

Actual results:
Error message after steps 1 and 2 (repeatable).

Expected results:
No errors.

Additional info:
Comment 1 manstis 2016-03-18 10:01:17 UTC 
This was identified and fixed as part of the referenced JIRA.
Comment 2 Jiri Locker 2016-04-05 11:19:53 UTC 
Verified in 6.3.0.ER2.
Note You need to log in before you can comment on or make changes to this bug.