Hide Forgot
Description of problem: Occasionally on Resource/Group Activity page loads, but consistently when F5 refreshing a Group/Activity page the asynchronous requests for resource type metadata timeout with the following message in ui 'Failed to load resource type metadata'. Version-Release number of selected component (if applicable): How reproducible: Most of the time. Steps to Reproduce: 1.Login and navigate to a resource like 'RHQ Agent'. 2. Hit F5 refresh and reload a few times. Actual results: Most of the time throws Failed to load resource type metadata Severity : Error Time : Thursday, April 7, 2011 9:23:46 AM Etc/GMT+4 Detail : com.google.gwt.http.client.RequestTimeoutException:A request timeout has expired after 10000 ms --- STACK TRACE FOLLOWS --- A request timeout has expired after 10000 ms at Unknown.com_google_gwt_core_client_impl_StackTraceCreator_createStackTrace__Lcom_google_gwt_core_client_JsArrayString_2(Unknown source:0) at Unknown.com_google_gwt_core_client_impl_StackTraceCreator$Collector_fillInStackTrace__Ljava_lang_Throwable_2V(Unknown source:0) at Unknown.com_google_gwt_core_client_impl_StackTraceCreator_fillInStackTrace__Ljava_lang_Throwable_2V(Unknown source:0) at Unknown.java_lang_Throwable_fillInStackTrace__Ljava_lang_Throwable_2(Unknown source:0) at Unknown.java_lang_Throwable_$$init__Ljava_lang_Throwable_2V(Unknown source:0) at Unknown.java_lang_Throwable_$Throwable__Ljava_lang_Throwable_2Ljava_lang_String_2Ljava_lang_Throwable_2(Unknown source:0) at Unknown.java_lang_Exception_$Exception__Ljava_lang_Exception_2Ljava_lang_String_2Ljava_lang_Exception_2(Unknown source:0) Expected results: No error message. Additional info:
this is due to the server-side query taking a long time when it needs to initially load the types
Created attachment 490662 [details] tree load issue.
During other refresh F5 work the following "BZ 694537, 693886 - do not double load" were addressed which improved overall load times. After much further investigation this was found to be the result of database corruption. With all other factors the same the problem was no longer seen after dbsetup. It is likely that the database was experiencing some sort of defragmentation or some form of corruption. See attached screen shot for more details showing dramatic effects to just one asynch operation. Repeated complete builds with clean had no effect before dbsetup was run. Closing this issue. Nothing more to do.