Bug ID: JDK-4429811 Application launched by JWS 1.0.1 has no Swing Display at all (B57)

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
1.0.1 1.0.1Fixed

Test case link:
http://comanche/jawstest/merlin/hellojaws/

Step to reproduce (On Window):
- Install Merlin B57.
- Due to another bug, after installing Merlin B57, you have to remove JWS
  1.0.1, which was bundled inside Merlin. (By default, that JWS 1.0.1 was
  installed into "C:\Program Files\JavaSoft\Java Web Start", that caused
  another bug.)
- From /usr/local/java/javaws1.0.1fcs/bundles, get 
  javaws-1_0_1-win-us.exe
  Install this one into a dir which does not contain ' ', such as C:\JWS101.
- Restart your browser, from above page, click the first jnlp link. You will
  see the application is running. But there is nothing displayed.

yu.wang@eng 2001-03-23

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.0.1 INTEGRATED IN: 1.0.1 VERIFIED IN: 1.0.1

31-08-2004

EVALUATION When I modified this code to do an invokeLater, the Runnable was never run. This may be related to java web start spanning its own AppContext and thus its own EventQueue. I'm reassigning to awt for further investigation. scott.violet@eng 2001-03-26 Commit to fix in Merlin-beta (blocks java webstart). eric.hawkes@eng 2001-03-27 This is possibly a duplicate of 4429816. michael.martak@Eng 2001-03-29 The source code shown at.. http://comanche/jawstest/merlin/hellojaws/code.html#file4 (src/hellojaws.java) is not consistent with the actual behavior of the application in jar/hellojaws.jar. I need the actual source code of the provided application to investigate this bug further. Please attach the current hellojaws.java and the hellojaws.jar to this bug. richard.ray@eng 2001-04-03 Updated the code.html for new test source. The workspace could be found: /net/sqesvr/deployment2/yuwang/ws/tests/jaws/merlin/hellojaws yu.wang@eng 2001-04-03 This looks like a WebStart problem. Notice in the comments that the AppContext in the application has two AWT-EventQueue threads. There should only be one. richard.ray@eng 2001-04-05 The above problem is caused by a change to EventQueue.java. Prior to Merlin EventQueue.java created the AWT-EventQueue thread in the constructor, now it is created on the posting of the first event. This causes trouble for WebStart. I believe this is related to the fixes for 4271416 and 4030718. See the comments section for the code snippet WebStart uses to create an AppContext richard.ray@eng 2001-04-06 This has been fixed by running application in it's own thread group. andy.herrick@East 2001-04-13

06-04-2001

Relates :	JDK-4421552 - Jaws1.0.1-ea build 06 on JRE1.4.0-beta-build 54 on Solaris 8 64-bit seems DOA
Relates :	JDK-4711515 - Wrong AppContext used in RMI threads
Relates :	JDK-4434688 - Application hang after frame is shown using merlin (B58)
Relates :	JDK-4429816 - JWS 1.0.1 Seems to be hang waiting for remote application (Merlin B57)