[
https://issues.jboss.org/browse/JBIDE-18238?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-18238:
---------------------------------------
But Rob, this happens on every JBDS start. So the question is what this mysteriously
disappearing java process is.
For example right now I started JBDS, it has a PID of 29833. And the error mentions 29838
which is a higher number.
Another attempt: 29841 and 29846. So it seems that this must be a process that is briefly
launched by JBDS itself.
Could not get monitored JVM error when Eclipse is started
---------------------------------------------------------
Key: JBIDE-18238
URL:
https://issues.jboss.org/browse/JBIDE-18238
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.2.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Labels: respin-a
Fix For: 4.2.0.CR1
When I start JBDS 8.0.0.CR1, I get this error in the error view:
{code}
Could not get monitored JVM.
org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException:
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:248)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.reflect.InvocationTargetException
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.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
... 5 more
Caused by: sun.jvmstat.monitor.MonitorException: 14202 not found
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
at
sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
... 10 more
Caused by: java.lang.IllegalArgumentException: Process not found
at sun.misc.Perf.attach(Native Method)
at sun.misc.Perf.attachImpl(Perf.java:270)
at sun.misc.Perf.attach(Perf.java:200)
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
... 13 more
{code}
This is in the workspace log:
{code}
!ENTRY org.jboss.tools.jmx.jvmmonitor.tools 4 0 2014-09-02 17:53:07.981
!MESSAGE Could not get monitored JVM.
!STACK 1
org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException:
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:248)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.reflect.InvocationTargetException
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.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
... 5 more
Caused by: sun.jvmstat.monitor.MonitorException: 14202 not found
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
at
sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
... 10 more
Caused by: java.lang.IllegalArgumentException: Process not found
at sun.misc.Perf.attach(Native Method)
at sun.misc.Perf.attachImpl(Perf.java:270)
at sun.misc.Perf.attach(Perf.java:200)
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
... 13 more
!SUBENTRY 1 org.jboss.tools.jmx.jvmmonitor.core 4 0 2014-09-02 17:53:07.983
!MESSAGE
!STACK 0
java.lang.reflect.InvocationTargetException
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.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: sun.jvmstat.monitor.MonitorException: 14202 not found
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
at
sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
... 10 more
Caused by: java.lang.IllegalArgumentException: Process not found
at sun.misc.Perf.attach(Native Method)
at sun.misc.Perf.attachImpl(Perf.java:270)
at sun.misc.Perf.attach(Perf.java:200)
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
... 13 more
Root exception:
sun.jvmstat.monitor.MonitorException: 14202 not found
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
at
sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
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.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
at
org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.IllegalArgumentException: Process not found
at sun.misc.Perf.attach(Native Method)
at sun.misc.Perf.attachImpl(Perf.java:270)
at sun.misc.Perf.attach(Perf.java:200)
at
sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
... 13 more
{code}
One interesting thing is that it complains about "14202 not found", but the
Eclipse process is actually 14197 and is shown in the JMX Navigator view. So I'm not
sure where is other number comes from.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)