|
Quick Lists
|
|
Bug ID:
|
6721619
|
|
Votes
|
0
|
|
Synopsis
|
Java Web Start 1.6.0 shows intermittent https communication breakdown
|
|
Category
|
java:classes_net
|
|
Reported Against
|
1.6
|
|
Release Fixed
|
,
6u12(b01) (Bug ID:2168832)
|
|
State
|
7-Fix in Progress,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
6722333
|
|
Submit Date
|
02-JUL-2008
|
|
Description
|
Java Web Start application started on Java Web Start 1.6.0 intermittently
fails to download resource files over https. The problem can be reproduced
with 1.6.0_03, 1.6.0_06 and 1.6.0_10 b25.
Everything is fine when using Java Web Start 1.5.0 on JRE 1.6.0 in exactly
the same enviroment.
So, Java Web Start 1.6.0 is less robust/reliable wrt https communication
than Java Web Start 1.5.0.
Posted Date : 2008-07-02 08:02:21.0
|
|
Work Around
|
use -Dhttp.keepAlive=false for Java Web Start 1.6
|
|
Evaluation
|
There is a race condition in the KeepAliveStream implementation that may allow a KeepAliveStream instance to be cleaned up by the KeepAliveStreamCleaner before it has its queuedForCleanup flag set. This may lead to the Http(s)Client instance being put in the KeepAliveCache twice. This may result in the KeepAliveCache closing the underlying socket while the jaws implementation is downloading on the same socket.
The solution is to synchronize on the KeepAliveStream instance while offering it to the cleaner queue as well as setting its queuedForCleanup flag. This will block the clearner from performing any action on the KeepAliveStream instance before it gets its queuedForCleanup flag set.
Posted Date : 2008-07-25 14:55:43.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
