United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4734417 : Unable to install JWS1.2rc shipped with JDK 1.4.1-rc

Details
Type:
Bug
Submit Date:
2002-08-21
Status:
Closed
Updated Date:
2002-08-22
Project Name:
JDK
Resolved Date:
2002-08-22
Component:
deploy
OS:
solaris_8,windows_2000
Sub-Component:
webstart
CPU:
x86,sparc
Priority:
P2
Resolution:
Not an Issue
Affected Versions:
1.2.0,1.4.1
Fixed Versions:

Related Reports

Sub Tasks

Description
I installed the JDK 1.4.1-rc and later tried installing Java Web start. I followed the installation directions from the guide but was unsuccessful. Here is the error reported: -
Do you agree to the above license terms? [yes or no] 
yes
In order to use Java(tm) Web Start you must have a version of Java 2 standard edition
installed. If you do not, you can download one from http://java.sun.com.
Please enter the path of your installation (eg /usr/local/java/jdk1.2):
/local_java/j2sdk1.4.1
Obtaining version...
Creating javaws.cfg...
Extracting...
Updating action...
Updating ~/.mailcap...
Updating ~/.mime.types...
Determining full JRE versions...
Bad installation. Error invoking Java VM (execv): No such file or directory

I was successful in installing the Java Web start once but when I tried to launch,it went into an infinite loop trying to connect to my Xserver, forced me to reboot the machine (unable to kill it).


Name: gm110360			Date: 08/21/2002


FULL PRODUCT VERSION :
J2SE version: java version "1.4.1-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-beta-b14)
Java HotSpot(TM) Client VM (build 1.4.1-beta-b14, mixed mode)

FULL OPERATING SYSTEM VERSION : Microsoft Windows 2000
[version 5.00.2195]


A DESCRIPTION OF THE PROBLEM :
After installation of the SDK "1.4.1-beta" -which
automatically installes Java Web Start- I started Java Web
Start and the problem occurred.

At first I checked the file 'javaws.cfg'to see whether the
correct JRE could be found, because a message was
indicating that the correct JRE could not be found (" Java
(TM) Web Start 1.2-beta : Bad installation. No JRE found in
configuration file " and "Java(TM) Web Start 1.2-beta : Bad
installation. Error invoking Java VM (SysExec) "). I
Corrected the name-value pairs, values containing path alle
double slashed.

After that, started Java Web Start again and my machine
went down to reboot

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Install SDK 1.4.1-beta, Java Web Start is automatically
installed as well;
2. Try to start Java Web Start the normal way (e.g. with
installation defaults). In my case this resulted in an
error (" Java(TM) Web Start 1.2-beta : Bad installation. No
JRE found in configuration file " and "Java(TM) Web Start
1.2-beta : Bad installation. Error invoking Java VM
(SysExec) ");
3. Change 'javaws.cfg' file as to reflect the correct
location of the JRE;
4. Start Java Web Start again. In my case the result was a
core dump and full reboot;

EXPECTED VERSUS ACTUAL BEHAVIOR :
Expected: Java Web Start Application Manager startup.
Actual result: blue system screen with one single memory
adress, after that automatic reboot

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Java(TM) Web Start 1.2-beta : Bad installation. No JRE found in configuration
file, no stack trace;
Java(TM) Web Start 1.2-beta : Bad installation. Error invoking Java VM
(SysExec), no stack trace

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER WORKAROUND :
I have uninstalled Java Web Start for the moment.
(Review ID: 160764)
======================================================================

                                    

Comments
EVALUATION


Asking submitter for more info, contents of his homedir/.javaws/javaws.cfg, we
find: 
> javaws.cfg.jre.1.product=1.4.0 
> javaws.cfg.jre.1.platform=1.4 
> javaws.cfg.jre.1.location=http\://java.sun.com/products/autodl/j2se 
> javaws.cfg.jre.1.path=/local_java/j2sdk1.4.1/jre/javaws/javaws

The problem is clearly this line in the javaws.cfg file: 
> javaws.cfg.jre.1.path=/local_java/j2sdk1.4.1/jre/javaws/javaws
This says that the executable for your jre is the javaws executable.
This will naturally keep invoking javaws over and over.

The installation dosn't write anything to the home dir's javaws.cfg file 
(only to the javaws.cfg in the installation directory) so the problem 
here was not the installation but your configuration file before launching 
the installation. 

###@###.### 2002-08-22
                                     
2002-08-22



Hardware and Software, Engineered to Work Together