[jbosstools-issues] [JBoss JIRA] (JBIDE-12060) Unhandled event loop exception: NPE in SelectServerActionDelegate.java

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698422#comment-12698422 ] 

Rob Stryker commented on JBIDE-12060:
-------------------------------------

{code}
### Eclipse Workspace Patch 1.0
#P org.jboss.ide.eclipse.as.ui
Index: jbossui/org/jboss/ide/eclipse/as/ui/actions/SelectServerActionDelegate.java
===================================================================
--- jbossui/org/jboss/ide/eclipse/as/ui/actions/SelectServerActionDelegate.java	(revision 41665)
+++ jbossui/org/jboss/ide/eclipse/as/ui/actions/SelectServerActionDelegate.java	(working copy)
@@ -56,7 +56,7 @@
 	private void update0() {
 		if(action == null) return;
 		IServer server = ServerManager.getInstance().getSelectedServer();
-		if( server != null ) {
+		if( server != null && server.getServerType() != null ) {
 			ImageDescriptor id = ImageResource.getImageDescriptor(server.getServerType().getId());
 			action.setImageDescriptor(id);
 		}
{code}

that's a patch. Again, a workspace should not have a server with a null servertype. This seems very broken. I have never heard of this ever. 
                
> Unhandled event loop exception: NPE in SelectServerActionDelegate.java
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-12060
>                 URL: https://issues.jboss.org/browse/JBIDE-12060
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.2.1.CR1
>            Reporter: George Lindholm
>            Priority: Minor
>
> Versions:
> JMX Console: 1.2.0.v20120526-0204-H835-CR1
> Project Examples:	1.2.1.v20120526-0515-H675-CR1
> JBoss Runtime Initializer: 1.3.0.v20120131-1005-H550-Beta1
> JBoss Runtime AS Detector: 1.3.0.v20120526-0503-H740-CR1
> Jboss RuntimeDetection: 1.3.0.v20120526-0503-H740-CR1
> JBoss Maven Project Examples: 1.3.0.v20120526-0648-H641-Final
> JBossAS Tools: 2.3.0.v20120526-0215-H1341-CR1
> JBossAS Tools Server/Compression Integration: 2.3.0.v20120526-0215-H1341-CR1
> JBossAS Tools Server/JMX Integration: 2.3.0.v20120526-0215-H1341-CR1
> JBossAS Tools Server/Remote Systems Integration: 2.3.0.v20120526-0215-H1341-CR1
> JBOSS Archives Tools: 3.2.1.v20120526-0206-H925-CR1
> What steps will reproduce the problem?
> 1.  Start eclipse
> 2. 
> 3. 
> -- Error Details --
> Date: Wed May 30 12:41:22 PDT 2012
> Message: Unhandled event loop exception
> Severity: Error
> Product: Eclipse 1.5.0.20120131-1544 (org.eclipse.epp.package.jee.product)
> Plugin: org.eclipse.ui
> Session Data:
> eclipse.buildId=I20120518-2145
> java.version=1.7.0_04
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_CA
> Framework arguments:  -product org.eclipse.epp.package.jee.product
> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product
> Exception Stack Trace:
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> 	at org.eclipse.swt.SWT.error(SWT.java:4361)
> 	at org.eclipse.swt.SWT.error(SWT.java:4276)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> 	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1021)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> 	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:915)
> 	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> 	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.ide.eclipse.as.ui.actions.SelectServerActionDelegate.update0(SelectServerActionDelegate.java:60)
> 	at org.jboss.ide.eclipse.as.ui.actions.SelectServerActionDelegate.access$0(SelectServerActionDelegate.java:56)
> 	at org.jboss.ide.eclipse.as.ui.actions.SelectServerActionDelegate$1.run(SelectServerActionDelegate.java:51)
> 	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> 	... 23 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira