[JBoss JIRA] (JBIDE-17940) JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17940?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-17940:
--------------------------------------
Yes, when switching to Generic it's working for a while. This issue is is somehow reproducible on older beta versions. My last experience is that sometimes JPA details works and sometimes not depending where you click and which Entity you use. Seems to me more I'm trying more it is working. For example I open Store entity and JPA Details view is blank. Then I open another Entity and after going back to the previuos entity and it works.
> JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17940
> URL: https://issues.jboss.org/browse/JBIDE-17940
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3, GNU/Linux 64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> JPA Details view is not working for entities in autodiscovery mode. It only works when entities are added into Managed Classes entities list. It's expected when JPA project is configured with "Discover annotated classes automatically" it should without manual listing entities in persistence.xml.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18258.
---------------------------------
> "Cannot find navigator content extension" when starting a local server after setting up a remote server
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18258
> URL: https://issues.jboss.org/browse/JBIDE-18258
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> When I set up a local server, then a remote server and then I start the local server, I get errors:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> {code}
> I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-18258.
-----------------------------------
Resolution: Cannot Reproduce Bug
I am sorry to say it, but I can't reproduce this any longer. It was happening to me repeatedly last week, but I cannot replicate it today no matter how hard I try. Rob says he saw this kind of error before, when he was missing plugin.xml, so it could be a borked jbds installation. But today I tried with exactly the same installation as before and nothing happened :(
Resolving for now. I will reopen if I ever see it again.
> "Cannot find navigator content extension" when starting a local server after setting up a remote server
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18258
> URL: https://issues.jboss.org/browse/JBIDE-18258
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> When I set up a local server, then a remote server and then I start the local server, I get errors:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> {code}
> I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-18258:
----------------------------------
Labels: (was: respin-a)
> "Cannot find navigator content extension" when starting a local server after setting up a remote server
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18258
> URL: https://issues.jboss.org/browse/JBIDE-18258
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> When I set up a local server, then a remote server and then I start the local server, I get errors:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895
> !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.
> {code}
> I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18238) Could not get monitored JVM error when Eclipse is started
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18238?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18238:
---------------------------------------
BTW, just in case you could not reproduce this. I just started JBDS with a new workspace and this error was not occurring. But when I quit and started the IDE again, it appeared again.
> 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-b
> 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)
11 years, 7 months
[JBoss JIRA] (JBIDE-18233) Unable to update nor install ADT within JBDS 7.1.1 to Android SDK 23+
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18233?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-18233:
-------------------------------------
No idea how these repositories got there. Let me remove them.
As you said, I'm not able to install it again after it got uninstalled.
> Unable to update nor install ADT within JBDS 7.1.1 to Android SDK 23+
> ---------------------------------------------------------------------
>
> Key: JBIDE-18233
> URL: https://issues.jboss.org/browse/JBIDE-18233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Environment: JBDS 7.1.1.GA
> Reporter: Karel Piwko
> Attachments: Screencast from 02-09-14 12.13.29.webm, Screenshot from 2014-09-02 12.18.32.png, Screenshot from 2014-09-02 12.18.56.png, Screenshot from 2014-09-02 12.19.09.png
>
>
> I'm not able to update ADT to handle Android SDK 23 that is installed on my machine.
> Added by Max: You can not even install the android tooling anymore - so something is definitely off.
> See attached screencast.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18238) Could not get monitored JVM error when Eclipse is started
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18238?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18238:
--------------------------------
Labels: respin-b (was: respin-a)
> 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-b
> 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)
11 years, 7 months