PH56229: TIMESTAMP IN HTTP_ACCESS.LOG (NCSA ACCESS LOG) IS INCORRECT AFTER UPGRADE TO 9.0.5.16

APAR status

• Closed as program error.

Error description

• Timestamp in http_access.log (NCSA access  log) is incorrect
  after upgrading WAS patch from WAS 9.0.5.14 JAVA 8.0.7.20 to WAS
  9.0.5.16 JAVA 8.0.8.5 on AIX 7.2.0.0. Timestamp in another
  log(sysout, syserr, application log) is correct."
  The sample is as below:
  Before patch
  - 192.168.11.254 - - [14/Jul/2023:18:11:21 +0700] "GET /snoop
  HTTP/1.1" 200 199 0 - -
  After 9.0.5.16
  - 192.168.11.1 - - [08/Mar/499075:09:14:57 +0700] "GET /snoop
  HTTP/1.1" 200 199 56532 - -
  
  This problem does not occur if using the default global setting
  (i.e enable NCSA but don't set the "accessLogFormat" custom
  properties).
  

Local fix

• This problem does not occur if using the default global setting
  (i.e enable NCSA but don't set the custom properties).
  
  Please use that workaround for now until I'm investigating
  this.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using NCSA log with the              *
  *                  "accessLogFormat" custom property on        *
  *                  8.5.5.24, 9.0.5.16 and 9.0.5.17.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the "accessLogFormat" custom       *
  *                      property is configured in a HTTP        *
  *                      inbound channel, the NCSA log has the   *
  *                      year timestamp displayed incorrectly.   *
  *                      For example:                            *
  *                      192.168.1.1 - - [08/Aug/499075:09:14:57 *
  *                      +0700] "GET /snoop HTTP/1.1" 200 199    *
  *                      56532                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The "accessLogFormat" was changed to use nanosecond instead of
  millisecond.  The year timestamp was inadvertently calculated
  during this change over.
  

Problem conclusion

• The year timestamp has been adjusted to display correctly when
  customized with the "accessLogFormat" custom property.  The
  problem does not occur if using the default global setting
  (i.e enable NCSA but do not set the custom property).
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 8.5.5.25 and 9.0.5.18
  
  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