Bug 1015314 - Navigating to Administration -- > Topology --> Servers has Globally Uncaught Exception
Navigating to Administration -- > Topology --> Servers has Globally Uncaught ...
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2013-10-03 18:04 EDT by Mike Thompson
Modified: 2013-10-07 12:02 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-03 19:08:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Thompson 2013-10-03 18:04:26 EDT
Description of problem:
Navigating to Administration -- > Topology --> Servers results in Globally Uncaught Exception

Version-Release number of selected component (if applicable):
RHQ 4.10 (master: 6784f2a)

How reproducible:

Steps to Reproduce:
1. Goto Administration -- > Topology --> Servers
2. Observe Error

Actual results:
No Servers and the loading gif is left spinning

Error with Globally Uncaught Exception

Error Message:
com.google.gwt.core.client.JavaScriptException:(null): null
(null): null
   at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:248)
   at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
   at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)
   at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)
   at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
   at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
   at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)
   at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
   at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
   at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
   at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)
   at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:546)
   at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363)
   at java.lang.Thread.run(Thread.java:724

Expected results:
No Errors
Comment 1 Jirka Kremser 2013-10-03 18:15:37 EDT
afaik, it happens only in the GWT debug mode not in production
Comment 2 Mike Thompson 2013-10-03 19:08:49 EDT
Looks like you are correct Jirka GWT Debug mode only. Production is fine.

I'll close it then.
Comment 3 Jirka Kremser 2013-10-04 07:52:16 EDT
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:


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.
Comment 4 Mike Thompson 2013-10-04 14:02:27 EDT
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().
Comment 5 Jirka Kremser 2013-10-07 12:02:56 EDT
It should be fine, I've seen it used in the coregui somewhere else. CoreGUI.isDebugMode() calls !GWT.isScript()


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