Maintenance Notice

The bugs.java.com site will be undergoing maintenance on 15th Dec 2017 21:00 PST to 16th Dec 2017 1:00 AM PST.
JDK-7064861 : CacheUtilTest.testRemove hangs
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7-client
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-07-09
  • Updated: 2013-09-12
  • Resolved: 2011-08-17
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 Availabitlity Release.

To download the current JDK release, click here.
JDK 7 JDK 8
7u2 b03Fixed 8Fixed
Related Reports
Relates :  
Description
After fix 7062597 CacheUtilTest starts to fail/hang.

There are multiple issues:

1) We now launch new thread in the Launcher but if main method throws uncatched exception then launch thread will not get notified about this

2) If applet desc in the test has codebase="." it will cause malformed URL exception
   If applet desc has no codebase or codebase="" then it will eventually fail with "codebase can not be empty for applet"
    in the XMLFormat:145

3) It seem that security manager installed will impact Junit tests as they will throw security exceptions all over the place.
   This may be related to the fact it code path now goes through new useappletLifecycle() method

I've not tested it but it may also mean that shortcuts to AWT applets do not work?

I'll temporary disable this test assertion to get other tests to run but we need to find out what is going on and fix it.

Comments
EVALUATION A few problems that is fixed: 1. import of applet-desc or javafx-desc is broken because of the webstart changes. the code path got incorrectly bypassed. 2. remove throwing of MissingFieldException in XMLFormat - it's not correct. codebase is not required in JNLP file. 3. changed test jnlp to not specify any codebase - it's not needed. 4. Add testNoCodeBaseJNLP in XMLFormatTest to make sure we do not throw MissingFieldException when parsing no-codebase JNLP file
2011-07-15