PH37476: IN AIX AND LINUX, LASTMODIFIED() TIMESTAMP IS NOT DETAILED TO MILLISECOND

APAR status

• Closed as program error.

Error description

• By using the JDK of WAS, the lastModified()  timestamp record in
  Windows, can be detailed to  millisecond, like 1617866544341,
  but in WAS for AIX or Linux, although it also record to
  millisecond, the last 3 numbers are always 000, like
  1617866544000, it means in AIX and Linux, the lastModified()
  timestamp is only detailed to second, not millisecond.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Automatic application restarts can be   *
  *                      triggered by OS differences in file     *
  *                      timestamps                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server provides an automatic reload
  mechanism (also known as "hot deployment"), which automatically
  restarts an application if an update is detected to the files
  within it. "Update" in the reload logic refers to a change in
  the last-modified time of the file, as returned by the Java File
  API's lastModified() method.
  The sensitivity of the timestamp attached to the file can vary
  across operating systems, as some use millisecond precision
  while others use second precision. This can cause false
  positives when a file is copied, unchanged, from one OS to
  another, potentially receiving a different timestamp despite
  having no changes in that span, which can then lead to an
  unexpected restart of the application when automatic reloading
  is enabled.
  

Problem conclusion

• The reload logic no longer restarts applications when file
  timestamps differ by less than 1000 milliseconds.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.22 and 9.0.5.11. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels