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 93395 - It is not possible to select JDK for Glassfish
Summary: It is not possible to select JDK for Glassfish
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
: 96286 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-01-29 09:03 UTC by Tomas Hurka
Modified: 2007-04-24 11:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
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 Tomas Hurka 2007-01-29 09:03:17 UTC 
It is not possible to select JDK for Glassfish. When profiling application on Glassfish, it is not possible to 
select JDK. You can see the dialog with available JDKs, but use selection of JDK is not reflected in Glassfish.
Comment 1 Tomas Hurka 2007-01-29 09:04:15 UTC 
It needs more investigation. Maybe it is bug in Glassfish server plugin.
Comment 2 Jiri Sedlacek 2007-03-23 12:49:05 UTC 
*** Issue 96286 has been marked as a duplicate of this issue. ***
Comment 3 Alexander Kouznetsov 2007-04-09 12:58:23 UTC 
Preparations for HOL showed that this is a real usability issue. User is
confusing which JDK he/she is asked about. There are two JDKs that involved in
the process and there is no information that Profiler is not able to make sure
that they are both selected correctly and match each other.
Comment 4 Jiri Sedlacek 2007-04-11 14:10:04 UTC 
Looks like this doesn't work from beginning, the same happens to me also for NB 
5.5 and 5.0. 

To change the JDK GlassFish runs on the AS_JAVA entry in asenv config file has 
to be modified. Appropriate code provided by the Profiler to modify asenv is in 
ConfigureProfiler.modifyAsEnvScriptFile, however this method seems to be never 
called.
Comment 5 Vince Kraemer 2007-04-12 21:49:46 UTC 
Well... it looks like this doesn't work for any of the servers (except for Tomcat).

All the J2eePlatforms return null for getJavaPlatform.
Comment 6 Alexander Kouznetsov 2007-04-12 21:57:03 UTC 
Please, detail your request stated in INCOMPLETE keyword. What is missing from
this issue description?
Comment 7 Jiri Sedlacek 2007-04-12 22:02:34 UTC 
The problem isn't related to J2eePlatform.getJavaPlatform(). This issue reports
the problem that GlassFish doesn't use JavaPlatform defined in
ProfilerServerSettings.getJavaPlatform() when starting in profiling mode.
Comment 8 Jiri Sedlacek 2007-04-12 22:12:19 UTC 
BTW currently only 3 serverplugins support profiling: Tomcat, AppServer and
JBoss. Both Tomcat and JBoss use correct
ProfilerServerSettings.getJavaPlatform() for profiling so "this doesn't work for
any of the servers" is quite strong statement:o)
Comment 9 Vince Kraemer 2007-04-12 22:37:35 UTC 
whatever
Comment 11 Tomas Hurka 2007-04-24 11:13:22 UTC 
Verified in latest NetBeans continuous build.