[JBoss JIRA] (JBIDE-18262) exception on startup
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18262?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18262:
----------------------------------------
Fix Version/s: 4.2.0.CR1
> exception on startup
> --------------------
>
> Key: JBIDE-18262
> URL: https://issues.jboss.org/browse/JBIDE-18262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> not sure what causes it but I'm getting this:
> java.lang.IllegalArgumentException: invalid version "6.0.0.CR01.1": invalid qualifier "CR01.1"
> at org.osgi.framework.Version.validate(Version.java:205)
> at org.osgi.framework.Version.<init>(Version.java:156)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher$RuntimeRangeRepresentation.matchesVersion(RuntimeMatcher.java:83)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:171)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130)
> at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:818)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.... ]
Rastislav Wagner commented on JBDS-2948:
----------------------------------------
Ok. I can do the same with enabled maven and pre-seed repo - to see the impact of maven.
All tests passed. I cant figure out why it shows a red cross - maybe its a bug but anyways you can click on test suite (ValidationPerfTest) to see the results of particular test.
You can also compare two test runs http://perflin64.mw.lab.eng.brq.redhat.com:8180/PerfServer/faces/view2.xh...
AFAIK you wont be able to run the tests locally - you need a server & DB to be able to see the results.
> Improve Performance of small and large projects
> -----------------------------------------------
>
> Key: JBDS-2948
> URL: https://issues.jboss.org/browse/JBDS-2948
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: integration
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Fix For: 8.0.0.GA
>
>
> Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues.
> Unfortunately perceived issues for the user feels just as slow as real issues.
> Suggestion:
> Look in jira for performance issues and add "performance" label to them
> Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings
> Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse.
> Setup goals to reach for these performance measurements.
> Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved.
--
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 commented on JBIDE-18238:
-------------------------------------
To be more clear, if I set breakpoints and manually terminate a process, I can replicate the issue. So this isn't just conjecture on my part.
> 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)
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 commented on JBIDE-18238:
-------------------------------------
>From my analysis, it would seem it detected a java process 14202, and, while processing it and beginning to monitor it, the process was terminated or exited naturally. So basically
1) Discover java process 14202
2) Initiate process to attach
3) Process 14202 terminates
4) Attempt to attach to 14202 fails.
Should we just not log this and simply abort monitoring that specific process?
> 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)
11 years, 7 months