zlab / jvmmonitor

Automatically exported from code.google.com/p/jvmmonitor
0 stars 0 forks source link

Profiling only works as super user under Ubuntu 11.10 #64

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the defect?
1. Install the environment as described below
2. Install jvmmonitor through the Eclipse market place
3. Try to profile an arbitrary application

Additional information:
As a normal user I am able to attach jvmmonitor to the equinox launcher it 
detects. Jvmmonitor behaves as expected if eclipse is run as root. The error 
messages hints at a non-readable pid/socket file.

What is the expected behaviour?
jvmmonitor should attach to the process, showing profiling information

What was the actual behaviour?
The eclipse console dumps the threads' stack trace and the jvmmonitor fails to 
attach with the error message "unable to open socket file: target process not 
responding or HotSpot JVM not loaded"

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

What is your environment for Eclipse?
Ubuntu Linux 11.10 amd64
Eclipse 3.7.0 installed through apt and Eclipse 3.7.1 (.gz from eclipse.org) 
were tested
OpenJDK6 and 7 and sun-java-6 were tested
Latest jvmmonitor from update site

What is your environment for the monitored JVM?
localhost

Original issue reported on code.google.com by t.mahlm...@gmail.com on 14 Nov 2011 at 3:21

GoogleCodeExporter commented 9 years ago
The error message is generated form outside JVM Monitor. The same error would 
occur when using other monitoring tools (e.g. jstack, jmap, jconsole) in the 
same environment. This is most likely an environmental issue.

As a fix in JVM Monitor, online documentation has been updated to give user a 
hint to solve the issue. When the error occurs, user can find a link next to 
the error message, and corresponding page in online documentation will be 
opened by clicking the link. 

Original comment by yoshitak...@gmail.com on 12 Feb 2012 at 2:16