Bug 748003 - Tables: globally uncaught exception (NPE) occurs in AuthorizedTableAction.onPermissionsLoaded() if RPC call to fetch global perms fails
Summary: Tables: globally uncaught exception (NPE) occurs in AuthorizedTableAction.onP...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: rhq42
TreeView+ depends on / blocked
 
Reported: 2011-10-21 17:04 UTC by Ian Springer
Modified: 2013-08-06 00:41 UTC (History)
2 users (show)

Fixed In Version: 4.2
Clone Of:
Environment:
Last Closed: 2012-02-07 19:24:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Ian Springer 2011-10-21 17:04:30 UTC
[INFO] (ErrorHandler.java:60) 2011-10-21 12:49:45,905 [WARN ] Globally uncaught exception
[INFO] java.lang.NullPointerException:
[INFO] null
[INFO]     at org.rhq.enterprise.gui.coregui.client.components.table.AuthorizedTableAction$1.onPermissionsLoaded(AuthorizedTableAction.java:81)
[INFO]     at org.rhq.enterprise.gui.coregui.client.PermissionsLoader$1.onFailure(PermissionsLoader.java:71)
[INFO]     at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:218)
[INFO]     at org.rhq.enterprise.gui.coregui.client.util.rpc.TrackingRequestCallback.onResponseReceived(TrackingRequestCallback.java:89)
[INFO]     at com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:287)
[INFO]     at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:393)
[INFO]     at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
[INFO]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[INFO]     at java.lang.reflect.Method.invoke(Method.java:597)
[INFO]     at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
[INFO]     at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
[INFO]     at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:157)
[INFO]     at com.google.gwt.dev.shell.BrowserChannel.reactToMessagesWhileWaitingForReturn(BrowserChannel.java:1714)
[INFO]     at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:165)
[INFO]     at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:120)
[INFO]     at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:507)
[INFO]     at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:264)
[INFO]     at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
[INFO]     at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
[INFO]     at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:188)
[INFO]     at sun.reflect.GeneratedMethodAccessor131.invoke(Unknown Source)
[INFO]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[INFO]     at java.lang.reflect.Method.invoke(Method.java:597)
[INFO]     at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
[INFO]     at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
[INFO]     at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:157)
[INFO]     at com.google.gwt.dev.shell.BrowserChannel.reactToMessages(BrowserChannel.java:1669)
[INFO]     at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:401)
[INFO]     at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:222)
[INFO]     at java.lang.Thread.run(Thread.java:662)

Comment 1 Ian Springer 2011-10-21 17:32:25 UTC
Fixed - [master 2a56db4] (http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=2a56db4).

Comment 2 Mike Foley 2011-10-21 21:09:45 UTC
i would need some details to expressly verify this.  if i see it, i will re-open it.

Comment 3 Ian Springer 2011-10-22 00:45:14 UTC
Failure of RPC calls typically occurs if the Server is not reachable, either because it is down or because it has been restarted since you logged into the GUI.

Comment 4 Mike Foley 2012-02-07 19:24:03 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.