JDK-6693244 : Java Web Start app fails on 6u10 beta w/ AssertionError in AuthenticationInfo.requestCompleted
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 6u10
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-04-24
  • Updated: 2010-07-29
  • Resolved: 2008-05-13
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 JDK 6 JDK 7
1.4.2_21Fixed 6u10 b24Fixed 7Fixed
Related Reports
Relates :  
JDK-2157822 - Cancelling HTTP authentication causes subsequent deadlocks
Relates :  
JDK-6648001 - Cancelling HTTP authentication causes subsequent deadlocks
Description
Java Web Start application fails to start on JRE6u10 b14 (beta) with 
java.lang.AssertionError after authentication attempt.
The Java Web Start Error message is:
Application Error: Unable to launch the application


The Exception tab shows:

java.lang.AssertionError
   at sun.net.www.protocol.http.AuthenticationInfo.requestCompleted(Unknown Source)
   at sun.net.www.protocol.http.AuthenticationInfo.endAuthRequest(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
   at java.net.HttpURLConnection.getResponseCode(Unknown Source)
   at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
   at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source)
   at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
   at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
   at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
   at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
   at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
   at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
   at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
   at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
   at com.sun.javaws.Launcher.launch(Unknown Source)
   at com.sun.javaws.Main.launchApp(Unknown Source)
   at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
   at com.sun.javaws.Main$1.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source) 


The problem is strictly reproducible.
Comments
EVALUATION ChangeSet=http://hg.openjdk.java.net/jdk7/tl/jdk/rev/ec438f2b6886,ChangeRequest=6693244
10-02-2010
EVALUATION This is most likely as a result of the changes for CR 6648001. CR 6648001 was fixed in 6u10 b13. Aside from this, I can see the possibility that endAuthRequest can be invoked twice with the same key. endAuthRequest in turn invokes requestCompleted, which contains the assertion. If an authentication request succeeds it will be added to the cache, Authentication.addToCache, this method will invoke endAuthRequest. HttpURLConenction.getInputStream has a finally block that will also invoke endAuthRequest.
28-04-2008