JDK-4775777 : "Invalid Cache Location" window incorrect behavior
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2002-11-07
  • Updated: 2003-02-28
  • Resolved: 2002-11-19
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.4.2 mantisFixed
Description
"Invalid Cache Location" window incorrect behavior on all platforms
Java Web Start 1.4.2-beta-b05

Steps:
- make sure your jaws java console enabled
- download one or two jaws applications
- go to the view View/Downloaded applications
- go to File/Preferences/Advanced
- click on Clear Folder, now Yes
- click 'OK' button to close Preference
"Invalid Cache Location" window saying:
"Cannot change cache location to:
/home/owner/.javaws/cache. Invalid cache location. A valid cache location must be either an empty directory, or a previous Java Web Start cache location." coming.

You need  to click on OK button to close this window.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b08 VERIFIED IN: mantis-beta
31-08-2004
EVALUATION I can only reproduce the problem on solaris with the latest version of javaws ###@###.### 2002-11-08 On solaris, sometimes the cache will contains a ".nfsxxx" file, where xxx are some random characters. After the cache is cleared, these .nfs file will regenerate right the way. which cause the AdvancedPanle.isCacheDirValid check to fail, because the cache is not empty and it does not contain the lastAccessed file. So the invalid cache location dialog poped up. A fix could be putting the lastAccessed file back after we clear the cache, which makes the cache a valid cache again even some file system private files (e.g .nfsxxx file in this case) cannot be removed. ###@###.### 2002-11-08
08-11-2002
SUGGESTED FIX http://javaweb.sfbay/~ngthomas/webrevs/4775777/webrev/ ###@###.### 2002-11-08
08-11-2002