This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 102170 - Profiler should be able to determine server's JDK
Summary: Profiler should be able to determine server's JDK
Status: VERIFIED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-23 15:23 UTC by Alexander Kouznetsov
Modified: 2007-05-08 13:37 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-04-23 15:23:44 UTC 
Profiler 070420
NetBeans IDE Dev (Build 070423)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

Steps to reproduce:
- Make sure that <Use Java Platform Defined In Project> is selected in Profiler
Options.
- Try to Profile Enterprise Application, EJB Module or Web Application
- RESULT: A dialog with an incorrect message is shown (issue 101806) that asks
user to select the JDK for profiling. It looks strange since there is an
information about JDK version in Project's Options. However, the root of this
problem is inability of profiler to get JDK info for any particular Application
or Web server. It would be nice if profiler was able to get this information
from server.
Comment 1 Jiri Sedlacek 2007-04-23 15:33:03 UTC 
I think that the problem is that you don't understand how profiling J2EE 
applications work. The Profiler doesn't need to detect anything, the Profiler 
*controls* which JDK will be used for starting the server using J2EE profiling 
API in serverplugin.

The Java Platform defined in Project properties isn't related to the Java 
Platform the server will be started on in any way. This is being determined 
from serverplugin when the server&its plugin supports it (currently only 
Tomcat), for running & debugging projects this can be set in server's 
customizer (currently Tomcat & JBoss).

FYI, the Profiler is able to detect JDK the target application is running on 
(and it does so), but this is absolutely useles in this case because the 
Profiler needs to create correct -agentpath argument *before* the server starts.
Comment 2 Alexander Kouznetsov 2007-04-23 16:27:16 UTC 
I agree that my understanding of this functionality is different from yours.
Probably this is because I appeal to the facts. The facts are as following:
- GlassFish is never invoked using the selected JDK (issue 93395)
- Even there is an option for platform in JBoss Server Customizer, Profiler is
still asking for JDK for JBoss-targeted projects
Comment 3 Jiri Sedlacek 2007-04-23 17:07:18 UTC 
As for the first item - this is covered by that issue.
As for the second item - please file an issue to jboss serverplugin.
Comment 4 Alexander Kouznetsov 2007-04-24 09:44:43 UTC 
Filed new Issue 102286 for JBoss server. Feel free to file corresponding issue
to serverplugins.
Comment 5 Alexander Kouznetsov 2007-04-25 15:05:43 UTC 
Verified as invalid
Comment 6 Alexander Kouznetsov 2007-05-08 13:37:15 UTC 
There is an RFE for GlassFish: Issue 83315