[JBoss JIRA] (JBIDE-20510) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20510?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-20510.
-----------------------------------
Resolution: Partially Completed
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-20510
> URL: https://issues.jboss.org/browse/JBIDE-20510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.CR1
>
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (JBIDE-20754) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20754?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-20754:
----------------------------------
Fix Version/s: (was: 4.3.0.CR1)
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20754
> URL: https://issues.jboss.org/browse/JBIDE-20754
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (JBIDE-20510) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20510?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20510.
---------------------------------
Closing.
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-20510
> URL: https://issues.jboss.org/browse/JBIDE-20510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.CR1
>
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (JBIDE-20510) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20510?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20510:
---------------------------------------
[~rob.stryker], so this is not very fortunate. You committed a fix, but said right off that this would not fix it on Windows which is the main thing that needs fixing. I'm not sure how to verify this partial fix, since I could not reproduce the original issue on Mac, only on Windows. But anyway, I am going to close this and I created a clone for the remaining work to fix this on Windows (I just checked and it's still happening): JBIDE-20754
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-20510
> URL: https://issues.jboss.org/browse/JBIDE-20510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.CR1
>
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (JBIDE-20754) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
by Martin Malina (JIRA)
Martin Malina created JBIDE-20754:
-------------------------------------
Summary: org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path - part 2
Key: JBIDE-20754
URL: https://issues.jboss.org/browse/JBIDE-20754
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.3.0.Beta2
Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
Reporter: Daniel Atallah
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.3.0.CR1
org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
{noformat}
java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:450)
at java.lang.Runtime.exec(Runtime.java:347)
at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
at java.lang.ProcessImpl.start(ProcessImpl.java:137)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 7 more
{noformat}
I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (JBIDE-20745) Livereload doesn't work stable with CordovaSim / BrowserSim
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20745?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20745:
---------------------------------------------
i would split this into two separate issues. The security issue and the small file issues since the security issue we can't really fix on our side since requires cordava/ionic side changes as I understand it ?
> Livereload doesn't work stable with CordovaSim / BrowserSim
> -----------------------------------------------------------
>
> Key: JBIDE-20745
> URL: https://issues.jboss.org/browse/JBIDE-20745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim, livereload
> Affects Versions: 4.3.0.CR1
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.3.1.Final
>
>
> Steps to reproduce:
> 1) create default THYM project
> 2) enable Livereload server
> 3) run THYM project on CordovaSim
> 4) edit index.html and save changes
> ERROR: refresh is not happening on Cordovasim
> Basically the things with Livereload are getting even more weird.
> In order to make it work one nee to remove the following meta tag from index.html:
> {code}
> <meta http-equiv="Content-Security-Policy" content="default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'; style-src 'self' 'unsafe-inline'; media-src *">
> {code}
> However, it seems that Livereload stopped working on simple pages like:
> {code}
> <!DOCTYPE html>
> <html>
> <head>
> <title>Insert title here</title>
> </head>
> <body>
> <h1>Hello World</h1>
> </body>
> </html>
> {code}
> But at the same time it works fine with some complex projects like & https://github.com/ibuziuk/cordovasim-demo
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (JBIDE-20669) Unhandled event loop exception when connecting to WildFly/EAP in JMX Navigator
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20669?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20669.
---------------------------------
Verified in JBDS 9.0.0.CR1 B105
> Unhandled event loop exception when connecting to WildFly/EAP in JMX Navigator
> ------------------------------------------------------------------------------
>
> Key: JBIDE-20669
> URL: https://issues.jboss.org/browse/JBIDE-20669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression, respin-a
> Fix For: 4.3.0.CR1
>
>
> I'm getting exceptions when I connect to a running server in JMX Navigator.
> I first noticed this with WildFly 10, but then verified it happens for WildFly 8.2.1 and EAP 6.4 also.
> The connection is established. But the only thing that works is MBeans - you can double click them and they will open, or you can just click one and the Property view will show details. But if you try to view properties of the connection itself, you will get more errors.
> The initial error is this:
> {code}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: null argument:)
> at org.eclipse.swt.SWT.error(SWT.java:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:583)
> at org.eclipse.jface.viewers.AbstractTreeViewer.setExpandedTreePaths(AbstractTreeViewer.java:2448)
> at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1$1.run(MBeanExplorerContentProvider.java:208)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
> {code}
> When you right-click the server in JMX Navigator, you get this:
> {code}
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.jmx.integration.jvmmonitor.JBossActiveJvm.<init>(JBossActiveJvm.java:70)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.getActiveJvm(JBossServerConnection.java:379)
> at org.jboss.tools.jmx.local.internal.actions.AttachActionProvider.fillContextMenu(AttachActionProvider.java:55)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:811)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5746)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:280)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4149)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3691)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
> And also a NPE:
> {code}
> java.lang.NullPointerException
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.jmx.integration.jvmmonitor.JBossActiveJvm.<init>(JBossActiveJvm.java:70)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.getActiveJvm(JBossServerConnection.java:379)
> at org.jboss.tools.jmx.local.internal.actions.AttachActionProvider.fillContextMenu(AttachActionProvider.java:55)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:811)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5746)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:280)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4149)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3691)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
> I'm using JBDS 9.0.0.CR1 B100 running on Oracle JDK 1.8 on OS X.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months