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 40172 - [JDK1.5.0] Problem with instalation 3.6 beta with JDK1.5 beta
Summary: [JDK1.5.0] Problem with instalation 3.6 beta with JDK1.5 beta
Status: VERIFIED FIXED
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords: JDK_SPECIFIC
: 41002 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-17 13:42 UTC by paoyu
Modified: 2005-07-14 11:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Output from cmd (java -verbose) (20.04 KB, application/octet-stream)
2004-02-26 06:24 UTC, paoyu
Details
Command line output from debug install (11.84 KB, text/plain)
2004-03-17 02:27 UTC, deeptinker
Details
Install log inside target directory from install with debugging turned on. (11.53 KB, text/plain)
2004-03-17 02:29 UTC, deeptinker
Details
3.6 final on JDK 1.4.2_03 (14.30 KB, text/plain)
2004-04-14 06:53 UTC, paoyu
Details
3.6 final on JDK 1.5.0 (14.19 KB, text/plain)
2004-04-14 06:53 UTC, paoyu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description paoyu 2004-02-17 13:42:23 UTC
I cannot install Netbeans 3.6 beta with JDK 
1.5.0 Beta. I ran installator in cmd :
java -jar NetBeansIDE-release36-Beta-setup.jar

Install program recognized JDK 1.5. When 
progress bar is displayed instalation crash. see 
log file.

(Feb 17, 2004 2:14:24 PM), 
Setup.product.install, 
com.installshield.product.service.product.PureJav
aProductServiceImpl$Installer, err, 
ProductException: (error code = 601; 
message="JVM not found")
STACK_TRACE: 8
ProductException: (error code = 601; 
message="JVM not found")
	at 
com.installshield.product.actions.JVMResolution.i
nstall(JVMResolution.java:171)
	at 
com.installshield.product.service.product.PureJav
aProductServiceImpl$InstallProduct.checkUninstall
erJVMResolution
(PureJavaProductServiceImpl.java:4747)
	at 
com.installshield.product.service.product.PureJav
aProductServiceImpl$InstallProduct.install
(PureJavaProductServiceImpl.java:4523)
	at 
com.installshield.product.service.product.PureJav
aProductServiceImpl$Installer.execute
(PureJavaProductServiceImpl.java:3727)
	at 
com.installshield.wizard.service.AsynchronousOper
ation.run(AsynchronousOperation.java:40)
	at java.lang.Thread.run(Unknown Source)
Comment 1 George Hernandez 2004-02-20 01:37:31 UTC
I haven't been able to reproduce this using the beta build or any 
other build. Is this reproducible for you?
Comment 2 paoyu 2004-02-20 06:37:45 UTC
Yes, I can reproduce this error. I tried to reproduce on two 
computers (Windows XP Pro).I think that is similar as issue 39559.
Comment 3 George Hernandez 2004-02-23 18:25:44 UTC
Your problem is in the middle of the installation, correct? If so, can
you attach the entire debug output please?
Comment 4 paoyu 2004-02-26 06:24:26 UTC
Created attachment 13659 [details]
Output from cmd (java -verbose)
Comment 5 paoyu 2004-02-26 06:27:06 UTC
Yes, you are right. Instalation crashed when progress bar shows 6%
I send attachment output.zip

java -verbose -jar NetBeansIDE-release36-Beta-setup.jar > Output.txt

Comment 6 George Hernandez 2004-03-16 15:42:54 UTC
*** Issue 41002 has been marked as a duplicate of this issue. ***
Comment 7 deeptinker 2004-03-17 02:24:15 UTC
At George's request I ran the following command:

java -Dis.debug=1 -jar NetBeansIDE-release36-200403141830-setup.jar > NB.debug 
2>&1

For me, it runs to completion and says that the install was successful, but it was not.  I will 
attach the NB.debug file that was created.  I will also attach the install.log that is in the 
target NB directory.

Environment:  OS X 10.3.2, 
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-122)
Java HotSpot(TM) Client VM (build 1.4.2-34, mixed mode)
(Full OS and Java Developer Tools installed)

Need anything else?  Let me know.

Travis
Comment 8 deeptinker 2004-03-17 02:27:26 UTC
Created attachment 14005 [details]
Command line output from debug install
Comment 9 deeptinker 2004-03-17 02:29:07 UTC
Created attachment 14006 [details]
Install log inside target directory from install with debugging turned on.
Comment 10 George Hernandez 2004-03-17 18:46:10 UTC
Can you both use the -is:javahome <javahome> option to see if that
gets you by the problem.
Comment 11 deeptinker 2004-03-18 01:10:13 UTC
Hi George,

Here is what I ran:

java -Dis.javahome=/Library/Java/home -Dis.debug=1 -jar NetBeansIDE-release36
-200403141830-setup.jar > NB.debug 

I got the same results.  Is this what you wanted me to run?  (-is:javahome /Library/Java/
home gave me a bad parameter error.)

Travis
Comment 12 George Hernandez 2004-03-18 22:24:50 UTC
The following is the resolution that I think will fix this problem as
stated in the installshield docs. So I think the problem that Paoyu
has may be taken care of in release 3.6 RC1. The mac issue is still to
be resolved. I am going to update all the jvm files, including the mac
ones, then will need the users to verify this is fixed before closing
the bug. I will add another comment when all the jvms have been
updated in the trunk.

"A JVM has been specified for the JVM Search Instructions property
which is not present on the target system. For example, if a search
instruction for only the "Java 1.2.2 by IBM Corporation" is specified,
and only a Sun 1.3 JVM is present on the target system, the above
error occurs. Note also that if a search instruction is made for a
very specific version of a JVM, then this exact version must be
present in order for the JVM resolution to succeed. To avoid this, use
more general search instructions ("Java 1.4.x by Sun Microsystems") or
include search instructions for several different JVM versions and
vendors."
Comment 13 George Hernandez 2004-03-19 15:53:17 UTC
I've updated the jvm files. They should be in today's build. If you
can test to see if the changes have any impact, I would appreciate it.
Thanks.
Comment 14 deeptinker 2004-03-24 16:22:34 UTC
Hi George,

I tried it again (with build 200403151900) and it still didn't work.
Specifically it didn't create a runide.sh file.  Here is the
install.log file (without debugging turned on). 

(Mar 24, 2004 11:12:34 AM), Setup.product.install,
com.sun.installer.PostInstallCoreAction, err, Shell Script does not
exist -
/Volumes/PB_Common/PB_Development/NB-Test-Jar-Installer/bin/runide.sh
(Mar 24, 2004 11:12:35 AM), Setup.product.install,
com.installshield.product.service.product.PureJavaProductServiceImpl$Installer,
err, ProductException: (error code = 601; message="jvm "jvm" is not
defined")
STACK_TRACE: 9
ProductException: (error code = 601; message="jvm "jvm" is not defined")
	at
com.installshield.product.actions.Launcher.installFailed(Launcher.java:417)
	at com.installshield.product.actions.Launcher.install(Launcher.java:315)
	at
com.installshield.product.actions.UninstallerLauncher.install(UninstallerLauncher.java:190)
	at
com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(PureJavaProductServiceImpl.java:4618)
	at
com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(PureJavaProductServiceImpl.java:3727)
	at
com.installshield.wizard.service.AsynchronousOperation.run(AsynchronousOperation.java:40)
	at java.lang.Thread.run(Thread.java:552)

Do you want me to run it with the verbose option turned on?  Is
InstallShield looking for 1.4.1 when what I have is:

java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-122)
Java HotSpot(TM) Client VM (build 1.4.2-34, mixed mode)

If there is some way I can help, let me know.

Travis
Comment 15 George Hernandez 2004-03-24 22:03:18 UTC
Travis, I checked in my changes on the 18th so you need the next
build. Unfortunately, I haven't seen a dev build since the 15th. Don't
know why.
Comment 16 deeptinker 2004-03-29 05:23:32 UTC
Hi George,

Your latest changes worked perfectly with build 200403281800.  Do you need someone 
else to verify it works on OS X?  

Probably need at test to verify that the original problem reported here is still fixed?

Travis
Comment 17 George Hernandez 2004-03-29 15:59:54 UTC
Travis, the more the merrier! Since we rely on the community for mac
support, we really appreciate anyone who can verify a fix. 

Paoyu, since we couldn't repproduce this, can you verify that the
problem no longer exists with the latest dev build?

Thank you all!
Comment 18 deeptinker 2004-04-14 03:27:59 UTC
Hi George,

Since this fix didn't make it into 3.6 final, will it have to wait
until 4.0?  Is this waiting on a response from paoyu or more testing
on OS X by someone else?
Comment 19 paoyu 2004-04-14 06:53:01 UTC
Created attachment 14378 [details]
3.6 final on JDK 1.4.2_03
Comment 20 paoyu 2004-04-14 06:53:35 UTC
Created attachment 14379 [details]
3.6 final on JDK 1.5.0
Comment 21 paoyu 2004-04-14 07:06:32 UTC
Hi Travis

I tested this problem with version 3.6 final. But on my two PC 
problem is still here. I added two attachments, I ran installation 
with command 
c:\java\j2sdk1.4.2_03\bin>java -Dis.javahome=c:\java\j2sdk1.4.2_03 -
Dis.debug=1 -jar 
D:\users\jakub\data\download\java\ide\netbeans\netbeans-3_6-setup.jar
and
C:\java\j2sdk1.5.0\bin>java -Dis.javahome=c:\java\j2sdk1.5.0 -
Dis.debug=1 -jar 
D:\users\jakub\data\download\java\ide\netbeans\netbeans-3_6-
setup.jar > NB.debug

When I started with JDK version 1.5.0 I could select only one JDK -  
1.5.0, with version 1.4.2_3 I could select from two JDK - 1.4.3_03 
and 1.5.0
But maybe problem is in my PC (software installation), so I tried to 
install with clear PC with next step :
1) Install J2SDK 1.5.0 Beta1
2) Install Netbeans 3.6 final

jakub
Comment 22 mslama 2005-02-11 09:50:47 UTC
It is already fixed for NB 4.0. I think problem was with missing JVM
resolution for JDK 1.5 in uninstaller. (During installation
uninstaller is created and installer tries to find JVM for uninstaller
according to uninstaller JVM resolution rules. Rules are stored in jvm
files for both installer and uninstaller. As you run installer using
jar not native launcher it fails when creating uninstaller. If you
would run native launcher it would probably fail at installer startup.)
Comment 23 mslama 2005-02-11 09:51:27 UTC
Reopen to reassign.
Comment 24 mslama 2005-02-11 09:54:39 UTC
Closing again.
Comment 25 Michal Mocnak 2005-07-14 11:24:26 UTC
Verified