|
Quick Lists
|
|
Bug ID:
|
4775777
|
|
Votes
|
0
|
|
Synopsis
|
"Invalid Cache Location" window incorrect behavior
|
|
Category
|
javawebstart:general
|
|
Reported Against
|
mantis
|
|
Release Fixed
|
1.4.2(mantis)
|
|
State
|
10-Fix Delivered,
Verified,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
07-NOV-2002
|
|
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.
|
|
Work Around
|
N/A
|
|
Evaluation
|
I can only reproduce the problem on solaris with the latest version of javaws
xxxxx@xxxxx 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.
xxxxx@xxxxx 2002-11-08
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |