Red Hat Bugzilla – Bug 148910
LTC18619- Javaws dont work/cant start
Last modified: 2007-11-30 17:07:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; da-DK; rv:1.7.5) Gecko/20041215 Firefox/1.0 Red Hat/1.0-12.EL4
Description of problem:
The IBM version of java 1.4.2 cant start javaws. Not from firefox browser and not from Terminal.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
3.Try lunch the javaws
I've reported this problem to IBM.
I am seeing this problem also with the Bea jdk 1.4.2.
Possible workaround: The RHEL3 java-1.4.1-ibm package for me works correctly on
*** Bug 150684 has been marked as a duplicate of this bug. ***
I just found this. Looks like it is a known problem.
And there is a fix:
That's all fine and good but there are applications that require 1.4.2 or
better (sun is now on 1.5). And 1.4.2 works fine on RHEL3 but not RHEL4, looks
like a step back to me.
please post the results from the java -version.
[pmatilai@esdhc939-17773 ~]$ java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20041210 (JIT enabled:
Oh and here's a nicer workaround, tried it and seems to work (that is, at least
javaws starts): http://www.advogato.org/person/rmathew/diary.html?start=71
---- Additional Comments From firstname.lastname@example.org(prefers email via email@example.com) 2005-09-26 11:16 EDT -------
I reported the bug to IBM Java support via our internal reporting system. The
generated PMR # is 93656,001,866.
---- Additional Comments From firstname.lastname@example.org(prefers email via email@example.com) 2005-09-27 17:06 EDT -------
IBM Java support raised a request with Sun for source diffs in regards to this
---- Additional Comments From firstname.lastname@example.org(prefers email via email@example.com) 2005-09-30 09:43 EDT -------
I had an update from Java support:
\"We were not able to recreate this problem, with
the latest 142 sr2 JDK on RHEL 4. Provide us sequence
of steps how to recreate this problem.
Sun bug 6195591 might be specific to there implementation.
Action Plan :
Provide us sequence of steps to recreate this problem.\"
So, it appears that the java version being used is fairly old now. The upcoming
RHEL 4 U2 service update contains the mentioned Java 1.4.2 SR2 (service release
2). Can you please give that a try and if that still does not help, please
provide more detailed recreation steps? Thanks.
Yup, the java package (java-1.4.2-ibm-18.104.22.168-1jpp_10rh) from RHEL 4 Extras Beta
appears to fix this issue.
What |Removed |Added
------- Additional Comments From firstname.lastname@example.org(prefers email via email@example.com) 2005-10-03 10:03 EDT -------
Thanks for the quick feedback! Closing bug as FIX_ALREADY_AVAIL.
This is fixed in U3.