Bug 720063 - Clicking on link to a dynagroup definition sometimes throws exception
Summary: Clicking on link to a dynagroup definition sometimes throws exception
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.1
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: jon30-bugs rhq41 rhq41-ui
TreeView+ depends on / blocked
 
Reported: 2011-07-08 22:21 UTC by Charles Crouch
Modified: 2015-02-01 23:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:26:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Charles Crouch 2011-07-08 22:21:39 UTC
Description of problem:
When clicking on a link here:

http://jon06.mw.lab.eng.bos.redhat.com:7080/coregui/#Inventory/Groups/DynagroupDefinitions



Version-Release number of selected component (if applicable):
Ian's perf env

How reproducible:
2 out of 3 times so far

Steps to Reproduce:
1. Create dynagroup
2. View the lists of groups generated
3. Go back and try to view the dynagroup definition
  
Actual results:
In the message center you see this:
com.google.gwt.core.client.JavaScriptException:(TypeError): Cannot call method 'markForRedraw__V' of null
--- STACK TRACE FOLLOWS ---
(TypeError): Cannot call method 'markForRedraw__V' of null
    at Unknown.anonymous(Unknown source:0)
    at Unknown.at org_rhq_enterprise_gui_coregui_client_CoreGUI$RootCanvas_$renderView__Lorg_rhq_enterprise_gui_coregui_client_CoreGUI$RootCanvas_2Lorg_rhq_enterprise_gui_coregui_client_ViewPath_2V(Unknown source:0)
    at Unknown.at Object.org_rhq_enterprise_gui_coregui_client_CoreGUI_onValueChange__Lcom_google_gwt_event_logical_shared_ValueChangeEvent_2V [as onValueChange__Lcom_google_gwt_event_logical_shared_ValueChangeEvent_2V](Unknown source:0)
    at Unknown.at Object.com_google_gwt_event_logical_shared_ValueChangeEvent_dispatch__Lcom_google_gwt_event_shared_EventHandler_2V [as dispatch__Lcom_google_gwt_event_shared_EventHandler_2V](Unknown source:0)
    at Unknown.at com_google_gwt_event_shared_HandlerManager$HandlerRegistry_$fireEvent__Lcom_google_gwt_event_shared_HandlerManager$HandlerRegistry_2Lcom_google_gwt_event_shared_GwtEvent_2ZV(Unknown source:0)
    at Unknown.at com_google_gwt_event_shared_HandlerManager_$fireEvent__Lcom_google_gwt_event_shared_HandlerManager_2Lcom_google_gwt_event_shared_GwtEvent_2V(Unknown source:0)
    at Unknown.at Object.com_google_gwt_user_client_impl_HistoryImpl_fireEvent__Lcom_google_gwt_event_shared_GwtEvent_2V [as fireEvent__Lcom_google_gwt_event_shared_GwtEvent_2V](Unknown source:0)
    at Unknown.at com_google_gwt_event_logical_shared_ValueChangeEvent_fire__Lcom_google_gwt_event_logical_shared_HasValueChangeHandlers_2Ljava_lang_Object_2V(Unknown source:0)
    at Unknown.at Object.com_google_gwt_user_client_impl_HistoryImpl_newItemOnEvent__Ljava_lang_String_2V [as newItemOnEvent__Ljava_lang_String_2V](Unknown source:0)
    at Unknown.anonymous(Unknown source:0)
    at Unknown.at com_google_gwt_core_client_impl_Impl_entry0__Ljava_lang_Object_2Ljava_lang_Object_2Ljava_lang_Object_2Ljava_lang_Object_2(Unknown source:0)


Expected results:
View the dynagroup definition

Additional info:

Comment 1 Charles Crouch 2011-08-11 03:55:47 UTC
Mike can you reproduce this? Any particular actions make it occur?

Comment 2 Mike Foley 2011-08-15 20:26:59 UTC
retested RHQ 4.1 on 8/15 on my local machine, and  could not repro.  
retested RHQ 4.? on 8/15 on perf env ... and could not repro.

perhaps it is one of the "quick click" issues, i am not able to repro following the bug loggers steps.

Comment 3 John Mazzitelli 2011-08-16 21:07:18 UTC
this might be a quick-click issue

Comment 4 John Mazzitelli 2011-08-18 17:27:41 UTC
I cannot reproduce this. I tried quick clicking around, too, to see if I can get it to happen and could not.

Comment 5 John Mazzitelli 2011-08-19 15:51:45 UTC
this does not seem to be a problem anymore - at least, I can't see it.

Comment 6 Mike Foley 2012-02-07 19:26:17 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


Note You need to log in before you can comment on or make changes to this bug.