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 200607 - Glassfish v3 doesn't use correct jdk for profiling
Summary: Glassfish v3 doesn't use correct jdk for profiling
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.1
Hardware: PC Linux
: P2 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 15:33 UTC by Petr Cyhelsky
Modified: 2011-11-18 11:04 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 Petr Cyhelsky 2011-08-02 15:33:15 UTC 
Product Version: NetBeans IDE Dev (Build 201108010600)
Java: 1.7.0; Java HotSpot(TM) Client VM 21.0-b17
System: Linux version 2.6.38-10-generic running on i386; UTF-8; en_US (nb)

Glassfish v3 uses its own jdk (the one defined in asenv.conf or in the glassfish properties accessible from services tab) for profiling. This is especially bad when GF runs on 32bit JDK and the profiled projects uses 64bit JDK. The other servers (ie Tomcat .., older GF) work fine. 

Steps to reproduce:
Have some 64bit system with 32bit and 64bit jdks and GFv3. Open some J2EE project in netbeans. In GFv3 properties set it to use one of the JDKs. Profile the J2ee project which uses the GFv3 with the other JDK.
Comment 1 Vince Kraemer 2011-08-02 19:15:02 UTC 
can reproduce
Comment 2 Quality Engineering 2011-08-03 13:52:55 UTC 
Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/0b191e734b8e
User: Vince Kraemer <vkraemer@netbeans.org>
Log: #200607 : overwriting the jdk selection before profiler is started
Comment 3 Vince Kraemer 2011-08-03 20:48:04 UTC 
in nightly
Comment 4 Petr Cyhelsky 2011-11-18 11:04:48 UTC 
verified