harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Markov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-4501) [drlvm][init][netbeans] NetBeans Profiler doesn't recognize DRLVM
Date Thu, 20 Dec 2007 13:28:43 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mikhail Markov updated HARMONY-4501:
------------------------------------

    Summary: [drlvm][init][netbeans] NetBeans Profiler doesn't recognize DRLVM  (was: [drlvm][netbeans]
NetBeans Profiler doesn't recognize DRLVM)

> [drlvm][init][netbeans] NetBeans Profiler doesn't recognize DRLVM
> -----------------------------------------------------------------
>
>                 Key: HARMONY-4501
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4501
>             Project: Harmony
>          Issue Type: Bug
>          Components: App-Oriented Bug Reports, DRLVM
>            Reporter: Vasily Zakharov
>            Priority: Minor
>
> NetBeans Profiler doesn't recognize Harmony as a Java platform usable for profiling.
> The problem was detected while running NetBeans 5.5 and 5.5.1 on Windows, with NetBeans
Profiler installed.
> How to reproduce:
> - Install NetBeans.
> - Install NetBeans Profiler.
> - Start NetBeans (on RI).
> - Add RI 1.4, 1.5, 1.6, BEA 1.4, 1.5, and Harmony DRLVM to the Java Platform Manager
(see HARMONY-4498 for instructions).
> - Go to Tools - Options - Profiler.
> - Open the 'Profiler Java Platform' drop-down list.
> - RI 1.5, 1.6, BEA 1.5 is there, RI 1.4, BEA 1.4 and Harmony are not there.
> When adding a JDK to Java Platform Manager, NetBeans performs a 'Detecting JDK' operation
where it calls the JDK and finds out its features. It seems that only JDKs with certain features
get to the Profiler Java Platform list.
> I replaced java.exe with a dummy executable that dumps its parameters to a file. It revealed
that Detecting JDK runs the following command line:
> java.exe -classpath "C:\Program Files\netbeans-5.5.1\ide7\modules\ext\org-netbeans-modules-java-j2seplatform-probe.jar"
org.netbeans.modules.java.j2seplatform.wizard.SDKProbe <temporal file>
> SDKProbe class, as seen from its source, simply dumps the system properties to the specified
file.
> So, it's very probable that the reason for NetBeans Profiler not recognizing Harmony
lays in values of some system properties set by VMs. Otherwise, the situation is unclear and
needs additional investigation. Probably Profiler expects "1.5" or "1.6" substring in java.vm.version
property.
> This issue can be a bug in NetBeans (binding to RI/BEA too tightly), or a compatibility
issue in DRLVM.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message