JDK-6435287 : Last execution date field is blank for javaws application
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-06-07
  • Updated: 2016-04-26
  • Resolved: 2015-09-18
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.
9 b85Fixed
Related Reports
Relates :  
Last execution date field is blank for javaws application

Tested OS : generic
Tested build : mustang b86

Steps to reproduce :

1. Install mustang b86
2. Clear cache
3. Launch java cache viewer
4. Launch any application (e.g, notepad application)

It can be noticed that the date field is blank for notepad application in java cache viewer.
Date is displayed only when java cache viewer is closed and relaunched.

Crucible review: https://java.se.oracle.com/code/cru/CR-JDK9CLIENT-1349

seems some other problem now, date is always blank on applications page. Ok - the above problem is (when launching jcp from javacpl.exe) we set (since JDK-8034819) the system property: -Djava.locale.providers=HOST,JRE,SPI We do not do this when launching javaws -viewer, or other cases of running java web start or plugin. As a result, the DateFormat used in writing the lastAccessed property into the lap (written from Java Web Start) differs from the DateFormat used to read it out (from JCP since 8u20). The fix is just to make the date format constant, using SimpleDateFormat, instead of DateFormat.getDateFormateInstance() There is still a problem caused by JDK-8034819, that the date as displayed in the cache viewer, or the Update Tab, is not the same format when JCP is invoked from webstart as opposed when it is invoked from javacpl.exe, but this will go awat with the new JCP re-alignment in JDK9.

fix looks trivial now - all lap is written from Cache.putLapData(), it seems all we need to do is call Cache.recordLastAccessed()

but currently lap files are written to in many places, not centralized , we need to add write method to Lap interface, and change all calls that write out the lap file to call that. Then we can call Cache.setLastAccessed() from there.

EVALUATION the startWatchers method in CacheViewer.java only refreshes the page when the cached content is changed, not also when the local application properties have changed. to fix, Cahce.setLastAccessed needs to be called when the LAP file is written.