You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vasily Zakharov (JIRA)" <ji...@apache.org> on 2007/07/19 18:19:06 UTC
[jira] Created: (HARMONY-4501) [drlvm][ibm vme][netbeans] NetBeans
Profiler doesn't recognize Harmony
[drlvm][ibm vme][netbeans] NetBeans Profiler doesn't recognize Harmony
----------------------------------------------------------------------
Key: HARMONY-4501
URL: https://issues.apache.org/jira/browse/HARMONY-4501
Project: Harmony
Issue Type: Bug
Components: App-Oriented Bug Reports, DRLVM, VM
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 (either DRLVM or IBM VME) 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. One such reason is IBM VME reports version 1.4 instead of 1.5 (see HARMONY-3211), and Profiler seems to ignore pre-1.5 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 Harmony.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4501) [drlvm][init][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Mikhail Markov (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553661 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
Vladimir, as I said above, the source code in question is not available, so we just don't know how NetBeans judges if the particular JDK is suitable for profiling or not.
Maybe we could ask a direct question to NetBeans team about this issue.
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514666 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
The similar issue exists for IBM VME: HARMONY-4516.
> [drlvm][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 (either DRLVM or IBM VME) 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. One such reason is IBM VME reports version 1.4 instead of 1.5 (see HARMONY-3211), and Profiler seems to ignore pre-1.5 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 Harmony.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514679 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
The name of the property checked by NetBeans Profiler is unknown, and Profiler sources are not available, so further investigation of this issue seems only possible by trying different values to find the right one.
Probably simulating RI system properties can help, and then restoring them to original values one by one can reveal the one that's critical and acceptable values for it.
> [drlvm][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.
[jira] Updated: (HARMONY-4501) [drlvm][netbeans] NetBeans Profiler
doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vasily Zakharov updated HARMONY-4501:
-------------------------------------
Description:
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.
was:
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 (either DRLVM or IBM VME) 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. One such reason is IBM VME reports version 1.4 instead of 1.5 (see HARMONY-3211), and Profiler seems to ignore pre-1.5 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 Harmony.
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532426 ]
Vladimir Beliaev commented on HARMONY-4501:
-------------------------------------------
Vasily, please specify the property name required for NetBeans.
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553653 ]
Vladimir Beliaev commented on HARMONY-4501:
-------------------------------------------
H-m-m., Vasiliy, you did such a good initial evaluations of Geronimo issues & prepared pretty small stand along tests...
May be, it is possible to do the same for NB? Please.... :)
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][init][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553966 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
I've tried a one-by-one manual properties checking.
It seems that the critical property is java.version, it should have value starting with "1.5.0_" (including underscore) for NetBeans to recognize the JRE as suitable for profiling.
> [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.
[jira] Updated: (HARMONY-4501) [drlvm][netbeans] NetBeans Profiler
doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vasily Zakharov updated HARMONY-4501:
-------------------------------------
Component/s: (was: VM)
Summary: [drlvm][netbeans] NetBeans Profiler doesn't recognize DRLVM (was: [drlvm][ibm vme][netbeans] NetBeans Profiler doesn't recognize Harmony)
> [drlvm][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 (either DRLVM or IBM VME) 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. One such reason is IBM VME reports version 1.4 instead of 1.5 (see HARMONY-3211), and Profiler seems to ignore pre-1.5 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 Harmony.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514682 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
This issues is most probably NetBeans-specific and won't affect other applications.
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553650 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
Verified, yes, the issue is still actual.
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][init][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553681 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
If I have time, I would also try a one-by-one removal to isolate the critical property. Hopefully, that would help.
> [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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532437 ]
Vasily Zakharov commented on HARMONY-4501:
------------------------------------------
I would if I knew it. Sources for NetBeans Profiler are not avaiable, so finding out what exactly is needed is tricky.
> [drlvm][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.
[jira] Commented: (HARMONY-4501) [drlvm][netbeans] NetBeans
Profiler doesn't recognize DRLVM
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553386 ]
Vladimir Beliaev commented on HARMONY-4501:
-------------------------------------------
Is this issue is still actual? Did you try it on recent M4 snapshot?
> [drlvm][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.