| Summary: | Navigating to Administration -- > Topology --> Servers has Globally Uncaught Exception | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Mike Thompson <mithomps> |
| Component: | Core UI | Assignee: | RHQ Project Maintainer <rhq-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.10 | CC: | hrupp, jkremser |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-03 23:08:49 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: | |
|
Description
Mike Thompson
2013-10-03 22:04:26 UTC
afaik, it happens only in the GWT debug mode not in production Looks like you are correct Jirka GWT Debug mode only. Production is fine. I'll close it then. These issues are annoying, the same problem was happening on the storage node detail page. Bad thing about it is, it doesn't report the line where the problem happened. On the StorageNodeDetailView, however, I was able to find out (by bisecting (commenting out half of the code and running it again.. and again ..)) that the the problematic line was, surprisingly: https://git.fedorahosted.org/cgit/rhq/rhq.git/tree/modules/enterprise/gui/coregui/src/main/java/org/rhq/enterprise/gui/coregui/client/admin/storage/StorageNodeDetailView.java#n395 So I've added the CoreGUI.isDebugMode() if there. What is even more weird is that this (the JavaScriptException:(null): thing) doesn't happen in Chromium. I'm not sure that CoreGUI.isDebugMode() is necessary or accurate. We don't have a way to tell if we are in running under the GWT debugger (as far as I know anyway). All that we know is that we are running under GWT Dev mode or Production Mode. And that already exists as GWT.isProdMode(). It should be fine, I've seen it used in the coregui somewhere else. CoreGUI.isDebugMode() calls !GWT.isScript() http://stackoverflow.com/questions/223373/is-there-way-for-a-gwt-program-to-tell-if-its-in-hosted-or-web-mode |