FULL PRODUCT VERSION :
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)


ADDITIONAL OS VERSION INFORMATION :
Linux saturn.bcplus.local 2.6.9-1.667 #1 Tue Nov 2 14:41:25 EST 2004 i686 athlon i386 GNU/Linux

(Fedora Core 3)

A DESCRIPTION OF THE PROBLEM :
Webstart cannot be startet, everything else is working fine and as expected.

When I try to start javaws, nothing happens. The process list shows:

hstahlm  21384 46.0  0.0  2540  708 pts/1    R+   21:03   0:04 javaws
hstahlm  21385  0.8  0.0     0    0 pts/1    Z+   21:03   0:00 [java] <defunct>

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
[  xxxxx@xxxxx   ~]$ javaws

ACTUAL -
Nothing happens, there is no VM error message.

The process list shows:

hstahlm  21384 46.0  0.0  2540  708 pts/1    R+   21:03   0:04 javaws
hstahlm  21385  0.8  0.0     0    0 pts/1    Z+   21:03   0:00 [java] <defunct>

ERROR MESSAGES/STACK TRACES THAT OCCUR :
no error messages

REPRODUCIBILITY :
This bug can be reproduced always.
  xxxxx@xxxxx   2004-11-15 23:07:58 GMT

N/A

Is this a dupe of a recently fixed problem ?
  xxxxx@xxxxx   2004-12-06 15:32:21 GMT

This is probably a dupe of 6188963; Can the original submitter try with the latest mustang build or latest 5.0 update 2 build?


  xxxxx@xxxxx   2005-1-03 18:13:18 GMT

this is a duplicate of 6188963: java web start cannot start on linux with newer glibc; and is fixed in 6.0 and 5.0 update 2
  xxxxx@xxxxx   2005-1-04 18:39:38 GMT

It seems to depend on Fedora Core 3. The jdk1.4.2_x produces the same error.

Maybe it

Nope, not Fedora specific. Getting exactly the same here on Gentoo. See http://bugs.gentoo.org/show_bug.cgi?id=69542 for details.

I also have problems with Fedora Core 3.
Fedora Core 2 just worked.
Here is a part of the command "strace javaws" :

stat64("/usr/local/kees/java/jdk1.5.0/jre/bin/java", {st_mode=S_IFREG|0755, st_s ize=64492, ...}) = 0
pipe([3, 4])                            = 0
pipe([5, 6])                            = 0
pipe([7, 8])                            = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, chil d_tidptr=0x923708) = 3454
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
waitid(P_PID, 3454, 0xfeffd5d0, 0, NULL) = -1 EINVAL (Invalid argument)
.....


The waitid repeats itself

On my FC3, Firefox downloaded the .jnpl file and nothing else happened.

The same here - FC2 and JRE 1.4.2_xx worked fine, FC3 and 1.5 causes the described problems.

I have the same Problem with SuSE 9.2.  SuSE 9.1 worked fine

try blackdown java J2SE v1.4.2-01 
-> Fixed Java Web Start startup deadlock

The same bug is marked as "Closed, fixed" for "5.0u2(b03)" at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6188963.

What about the votes for this bug report? Certainly that fix will also be backported to 1.4.x, will it?

It's not fixed in the latest 1.5.0 jdk,

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)

which still cannot run javaws  on Suse 9.2 with glibc-2.3.3.

Same problem with 1.5.0_01
System: Fedora 3 on Fedora 2 it works.

Here's a temp fix for now:

Get this version of javaws http://www.jbg.f2s.com/javaws-1_2_0_06-linux-i586-i.zip


unzip in a suitable location (not the current java directory) and execute install.sh to install this version of javaws.

Now open a web start link (eg one from here http://java.sun.com/products/javawebstart/demos.html but specify the newly installed javaws as the program to execute rather than the old (not working one)

Note, if you have already set the default web start app in FireFox then just go to Edit->Preferences->Downloads and edit the entry for JNLP file types

The evaluation asks the submitter to try with the latest mustang or 5.0 update 2 build. I

Drat, my comment got cut off somehow. Should have read:
I am not the original submitter, but I am one of the people hit with this bug. The evaluation asks to try with the latest mustang or 5.0 update 2 build. Where do we get unreleased builds like that to test with?