Start is shown but nothing happens

[GoogleCodeExporter]

What steps will reproduce the defect?
 1. Open JVM Monitor view in Eclipse
 2. Double-click / right click + start monitoring on Eclipse process (org.eclipse.equinox)
 3. Look at "Start monitoring" in progress view
 4. see that nothing is happening
...

What is the expected behavior?
Timeline, Memory, CPU, ... shown in Properties view

What was the actual behavior?
"Monitoring is not started for the selected JVM" is shown in Properties view

What errors are shown on Error Log view or at <workspace>/.metadata/.log?
nothing related


What is your environment for Eclipse?
OS: Fedora 18 64bit
Eclipse: Juno Service Release 2 - Build id: 20130225-0426
JVM Monitor: 3.8.1
Java: OpenJDK 

What is your environment for the monitored JVM?
the same as for Eclipse

Original issue reported on code.google.com by [email protected] on 3 Jun 2013 at 3:27

[GoogleCodeExporter]

I Have exactly the same issue. Getting the following message.
"Monitoring is not started for the selected JVM"

OS: Fedora 20 
Eclipse: Version: Kepler Service Release 1
Build id: 20130919-0819

JVM Monitor: 3.8.1.201302030008
Java:
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

Original comment by [email protected] on 27 Feb 2014 at 4:21

[GoogleCodeExporter]

I have the same issue:

"Monitoring is not started for the selected JVM" with "Start Monitoring" 
getting stuck and disappering some time later, not actually starting the 
monitoring. Does not work with either running or debugging an application or 
trying to monitor the eclipse jvm.
The .log does not say anything related to JVM except a message when I quit 
Eclipse while "Start moitoring" still runs, telling me that plugins should 
terminate their processes on shutdown.

OS: Mac OS X 10.6.8
Eclipse: Juno 4.2.2, Build M20130204-1200
JVM Monitor: 3.8.1.201302030008

Java Runtime (Apple Inc.):
Java(TM) SE Runtime Environment
1.6.0_65-b14-462-10M4609

VM:
Java HotSpot(TM) Client VM
20.65-b04-462

Original comment by [email protected] on 8 Mar 2014 at 2:34

[GoogleCodeExporter]

Same problem. I double click on a vm, nothing happens except the properties tab 
opens with nothing inside. 
OS: Fedora 20
Java OpenJDK 1.7.0_45
Eclipe Version: 4.3.2

Original comment by [email protected] on 31 Jul 2014 at 3:05

[GoogleCodeExporter]

Any updates on this issue?

"Same problem. I double click on a vm, nothing happens except the properties 
tab opens with nothing inside."

I get the same on JDK 7, Windows 7, Eclipse Luna.

Original comment by [email protected] on 23 Mar 2015 at 12:28

[GoogleCodeExporter]

Same problem. I double click on a vm, nothing happens except the properties tab 
opens with nothing inside.
OS: Ubuntu 12.04
Java OpenJDK 1.6.0_33
Eclipe Version: 4.2.2

Original comment by [email protected] on 26 Mar 2015 at 11:31

[GoogleCodeExporter]

Same problem, but I have this in the log:

!ENTRY org.eclipse.ui 4 0 2015-06-02 14:30:51.503
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable 
(java.lang.NullPointerException)
    at org.eclipse.swt.SWT.error(SWT.java:4441)
    at org.eclipse.swt.SWT.error(SWT.java:4356)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
    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:483)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: java.lang.NullPointerException
    at org.jvmmonitor.internal.ui.views.StartMonitoringAction.openPropertiesView(StartMonitoringAction.java:265)
    at org.jvmmonitor.internal.ui.views.StartMonitoringAction.showPropertiesView(StartMonitoringAction.java:151)
    at org.jvmmonitor.internal.ui.views.StartMonitoringAction$1$1.run(StartMonitoringAction.java:103)
    at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:167)
    at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:165)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
    ... 24 more


Platform details:
Fedora 21 x86_64, eclipse 4.4.2 running on Oracle JDK 1.8 (1.8.0_25-b17), 
jvmmonitor 3.8.1.201302030008.
The processes I tried to attach to were launched with Java6, both Oracle's 
(1.6.0_45) and OpenJDK (1.6.0_24), always 64 bit.

Original comment by [email protected] on 2 Jun 2015 at 12:44