install java web start into linux os using newer version of glibc (2.3.3+)

for example, RH AS 4.0 beta

java web start cannot start and hang
  xxxxx@xxxxx   11/1/04 20:00 GMT

N/A

the problem is because we call waitid in linux with no options set;  Older
glibc does not have the sanity check for waitid options, so "0"
is accepted, and interpreted as if it's WEXITED, so it works in older glibc.
  xxxxx@xxxxx   11/1/04 20:09 GMT

this bug is fixed in 5.0 update 2 and 6.0
  xxxxx@xxxxx   2005-2-07 18:16:42 GMT

where is the fix? the following version of jdk 1.5 still has the bug:

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

on Suse 9.2 with glibc-2.3.3.

grrrrr,

jdk1.5.0_01 still has this bug.
This bug stops me from using this jdk.

jdk1.5.0_01 still has this bug (tested on SuSE9.2)

what about JDK 1.4.2? 

This is also broken in 1.4.2_06 (running on Fedora Core 3).

Is there a work around for 1.4 users?

I knew I've seen this bug somewhere. Took me few hours of trying various thing, and here are the results:

Suse 9.2, glibc 2.3.3
Mustang builds work, at least b16 and b17
Somehow (and do not ask me how), javaws from JRE download of 1.5.0-b64 works. At least on one of my machines.

Everything else fails.

Please fix, guys!

Ups, my bad, my JRE1.5.0-b64 that works was installed on Suse 9.1, which was then upgraded to 9.2 (and newer glibc2.3.3). So the workaround is pretty clear, he he.

Is javaws going to be fixed so that it will work with glibc 2.3.4 on FC3?

I realise that the fix will be available as part of update 02 whenever that is scheduled for release but since 01 is just out it will take some time. Is there an internediate fix for us who really need it?

/Morten
morten_schousen@hotmail.com

I agree is there a workaround whilst we wait for the actual fix in 1.5_02

Here

Here's a temp fix for Fedora Core 3 etc:

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.

To test, 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

This temp fix isn't working with signed applications...

1.4.2_07 has just been released and this bug is still there. Will it be fixed in 1.4 or only in 5.0? 
I guess that users with newer distros shouldn't be forced to use jdk 5.0.

Can someone please give a hint as to when Java 5 update 2 will be available?  This bug really is a showstopper for those of us developing under Linux.  

As armhold has said,  a release date for the fixed version  would be nice since the has heavy impact on several projects.

J2SE 5.0 Update 2 should be out by the end of march. It will contain the update addressing this bug.

As others have asked:  Will this fix be backported to 1.4.2?

I tried with 6.0 update 2 : it works (Linux Slackware10.1)

Sorry for the typo : I meant 5.0 update 2 ;-)

I found a workaround:

http://www.advogato.org/person/rmathew/diary.html?start=70

It's a little tedious, but it works.

A better workaround using a pre-loaded DSO to redirect the call to waitid() is:

http://www.advogato.org/person/rmathew/diary.html?start=71