Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4449645
Votes 0
Synopsis b16 installer always fail on Solaris 2.6 IA
Category javawebstart:enterprise_support
Reported Against 1.0.1
Release Fixed
State 11-Closed, duplicate of 4626733, bug
Priority: 4-Low
Related Bugs 4477277 , 4626733
Submit Date 24-APR-2001
Description
On Solaris IA, the b16 installer cannot install correctly as follows.

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):
/usr/java
Obtaining version...
Creating javaws.cfg...
Extracting...
Updating action...
Updating ~/.mailcap...
Updating ~/.mime.types...
Determining full JRE versions...
Java Web Start splash screen process exiting .....
Bad installation. Error invoking Java VM (SysExec) 
/usr/java/bin/java: No such file or directory
% which java
/usr/java/bin/java
% java -version
java version "1.3.1-rc2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc2-b22)
Java HotSpot(TM) Client VM (build 1.3.1-rc2-b22, mixed mode)
% 

Though JRE exists and works properly, the b16 installer does not
work properly, not b15.  Only for Solaris 2.6 IA, not Solaris 2.6 SPARC.

  xxxxx@xxxxx   2001-04-24

The above error occurs only on Solaris 2.6 IA even if it uses released version of
java as follows.

Please enter the path of your installation (eg /usr/local/java/jdk1.2):
/usr/j2se
Obtaining version...
Creating javaws.cfg...
Extracting...
Updating action...
Updating ~/.mailcap...
Updating ~/.mime.types...
Determining full JRE versions...
Java Web Start splash screen process exiting .....
Bad installation. Error invoking Java VM (SysExec) 
/usr/j2se/bin/java: No such file or directory
% /usr/j2se/bin/java -version
java version "1.3.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_01)
Java HotSpot(TM) Client VM (build 1.3.0_01, mixed mode)
% 

  xxxxx@xxxxx   2001-04-26
Work Around
Remove config file /home/user_name/.javaws/javaws.cfg before installing
on other platform (Solaris sparc vs Linux vs Solaris intel)
Evaluation
Java Web Start Requires released version of java (non-beta) to match
wildcard request 1.3+, 1.2+.  Therefore on system with only beta version of 
java installed, you must install released version of java.
  xxxxx@xxxxx   2001-04-25

Can get into fatal problem if user has installed java web start for Solaris
Sparc,  And then installs Solaris x86 version.  The system config file
will have the right jre's in it, but the user specific config file
in your home directoyr/.javaws will have sparc jres.  this will cause
error launching on Solaris intel.  Although work around is to remove user-
specific javaws.cfg before installing java web start for a new platform,
it would be better if JRE information in config file was platform specific.
and then multiple platforms could share the other config info.

Downgrading to P4 - postpone adding platform info to cfg file til next version .
  xxxxx@xxxxx   2001-04-30
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang