JDK-4396040 : Some negative TCK tests are hanging on Windows
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: jaws-1.0,1.0.1
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.6,windows_nt
  • CPU: x86,sparc
  • Submitted: 2000-12-07
  • Updated: 2001-05-03
  • Resolved: 2001-05-03
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
Related Reports
Relates :  
JDK-4447985 - TCK 1.0.1 B04 has java.net.SocketException issues on Windows (B15)
Description

Name: acR10002			Date: 12/07/2000


After a fix for 4390297, the client/launcher works stable on Windows NT,
however the test :

jnlp_file/SimpleJnlpTest/index.html#negative

hangs and passes due to timeout instead of be correctly failed.
This happens because the negative error code doesn't come from the client
for some reason.

======================================================================
###@###.### 2000-12-07

Both hanging and failing with -1 code are still observed on Windows 98.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.0.1 FIXED IN: 1.0.1 INTEGRATED IN: 1.0.1 VERIFIED IN: 1.0.1
31-08-2004
EVALUATION This seems to be a problem with TCK. thomas.v.ng@east 2001-04-05 Name: aaR10142 Date: 04/12/2001 Because of the TCK needs feedbacks from the JNLP client, JNLP client developers should provide an entry point and feedbacks mechanism, called JNLPLauncher. The JaWS JNLPLauncher contains two parts, The First com/sun/tck/jnlp/lib/JNLPProcess.java com/sun/tck/jnlp/lib/CommandJNLPLauncher.java placed in JNLP TCK workspace. The JNLPProcess open tcp socket, start the javaws and pass to it point to the socket. The Second placed somewhere in the JaWS. When the javaws started, it connect to the First part and send debug information over the tcp connect. Something like "Java started", "JNLP launched" and so on. But because of the JaWS does not correctly flush and close the TCP socket before exit, some (sometimes all) such messages are lost, and the First part hangs o reports that the JaWS does not finish correctly. Please fix this JaWS problem, because it causes �� lot of JaWS failures on Windows platforms, especially when The TCK runs with latest JaWS builds. ====================================================================== Name: aaR10142 Date: 04/18/2001 Because the first priority bugs were closed as duplicate of this one, I high the priority of the bug. ====================================================================== This is fixed by the fix to 4447985 thomas.v.ng@east 2001-04-26
26-04-2001