search

philippejer / jvmmonitor

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

path with spaces not allowed #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the defect?
1.
try java "-javaagent:c:/jvm monitor/jvmmonitor-agent.jar" -version
or
try java -javaagent:"c:/jvm monitor/jvmmonitor-agent.jar" -version

What is the expected behavior?
to work fine
What was the actual behavior?

SEVERE: Cannot not register CpuBciProfilerMXBean.
java.io.FileNotFoundException: c:\jvm (The system cannot find the file 
specified)
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:127)
        at java.util.jar.JarFile.<init>(JarFile.java:135)
        at java.util.jar.JarFile.<init>(JarFile.java:72)
        at org.jvmmonitor.internal.agent.Agent.init(Agent.java:107)
        at org.jvmmonitor.internal.agent.Agent.premain(Agent.java:43)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
        at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b03)
Java HotSpot(TM) Client VM (build 20.8-b03, mixed mode)

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

What is your environment for Eclipse?
  OS: Windows
  Eclipse: Indigo
  JVM Monitor: current
  Java: Sun JDK 6 Update 33

What is your environment for the monitored JVM?
  OS: Windows
  Java: Sun JDK 6 Update 33

Original issue reported on code.google.com by mbada...@gmail.com on 2 Nov 2012 at 10:36

GoogleCodeExporter commented 9 years ago 
ok answering myself .. it is a JVM bug and fixed in JDK7
http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=f84d44729bd8affffffffeb9b
87963e2d752?bug_id=6459832

Original comment by mbada...@gmail.com on 2 Nov 2012 at 1:26

GoogleCodeExporter commented 9 years ago 
FAQ in User Guide has been updated

Original comment by yoshitak...@gmail.com on 2 Feb 2013 at 3:42