Description of problem: When navigating to the Group View summary page there is continuous "Loading data..." message on the Group Operations portlet. When trying to get the portlet settings the following exceptions are thrown: Message : Globally uncaught exception Severity : Error Time : Friday, March 16, 2012 1:53:55 PM Etc/GMT-1 Detail : com.google.gwt.core.client.JavaScriptException:(TypeError): Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert description: Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert number: -2146823281--- STACK TRACE FOLLOWS ---(TypeError): Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert description: Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert number: -2146823281 Message : Failure in datasource while processing FETCH request. Severity : Error Time : Friday, March 16, 2012 1:55:40 PM Etc/GMT-1 Detail : com.google.gwt.core.client.JavaScriptException:(TypeError): Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert description: Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert number: -2146823281--- STACK TRACE FOLLOWS ---(TypeError): Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert description: Für die Eigenschaft "length" kann kein Wert abgerufen werden: Das Objekt ist Null oder undefiniert number: -2146823281 The following SQL: select c.* from rhq_dashboard_portlet p inner join rhq_config_property c on p.configuration_id = c.configuration_id inner join rhq_dashboard d on p.dashboard_id = d.id inner join rhq_subject s on d.subject_id = s.id where s.name = 'rhqadmin' and p.name = 'Group: Operations' returns null for the OPERATION_STATUS property value. Version-Release number of selected component (if applicable): RHQ 4.2 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
JON bugzilla for the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=805210
per BZ triage ... make this a high. JON had no locale requirements. So these are not release blocking for JON.
Please note that the locale requirement mentioned in Comment 2 is assuming that this issue is actually due to locale support.
Looking at this portlet it doesn't have the "unlimited" configuration value that was causing the "locale" issue in some other portlets. Having said that, I haven't reproduced in any simple way, with a single element group and the default locale. Has anyone reproduce this?
master commit 8ffe2a02a8a8fb6b12e78ea02b3c4ee588c82fd7 I couldn't reproduce the issue directly but I did find a few problems in the portlet which I fixed here. I think it's likely that the problem will be solved by these fixes. Primarily, it adds support in this portlet and others to better handle having all of the enum filter values (in this case the operation status enums) unset. Also, changes in config were not being applied to the current instantiation of the portlet. A workaround for existing, problematic portlets is to delete it and then add it back using "Edit Mode" and "Add Portlet". Test Notes: Make sure you try the global/group/resource level operation history portlets. Alter various config and make sure it affects the current portlet and is also stored properly (leave global dash or the detail view, and then and come back and see if it is correct).
This issue is a direct result of Oracle and its VARCHAR2 type treating null and empty string as one in the same and returning null in both cases. This was originally reported in Bug 536526. The fix for this needs to be to handle the null values returned properly (i.e. we can not use empty string as a valid/meaningful value as it will be no different then null).
Interesting/worrying https://bugzilla.redhat.com/show_bug.cgi?id=805210#c7
master commit 246d533ac9d1ff238f52b643696f7f362823e606 Cleaned up a bunch of dangerous code in the portlets including several instances of where we didn't handle the null returning from oracle when storing "" for a varchar2 field. Test Notes: This will be a bit tedious, but test the configuration of all portlets, at the global, resource and group dashboards, on oracle (especially) and postgres. Make changes to result counts, metric ranges, and any enumerated filters (like Alert priorty, operation status, etc). For the enumerated filters ensure you set all,some and none (note - when unchecking all of the enumerated values the filter should go back to checking all of them.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.