PI47542: INVALID TIMESTAMP ERRORS IN ANALYTICS LOGS

IBM MobileFirst Platform Foundation Interim Fix README for 7.1
IBM MobileFirst Platform Foundation Interim Fix README for 7.0
IBM MobileFirst Platform Foundation Interim Fix README for 6.3
IBM Worklight Interim Fix README for 6.2.0.1

APAR status

• Closed as program error.

Error description

• In the MobileFirst Platform 7.1 Analytics log file, there are
  lots of invalid timestamp errors:
  
  [8/20/15 10:53:58:547 CDT] 000000e7
  bm.mobile.analytics.server.processors.v1.ClientLogsProcessor W
  MSAN222W: Event received with an invalid value:
  -61,295,582,302,573 for field: timestamp while processing data:
  {"msg":"WLAFHTTPClient
  logOutboundRequest","metadata":{"$time":1439817697426,"$tracking
  id":"08463E08-5365-40E0-BBCD-EF9865AC0E56","$category":"network"
  ,"$path":"\/ibm\/apps\/services\/loguploader","$type":"request
  "},"level":"ANALYTICS","pkg":"wl.request","timestamp":"17-08-002
  7 09:21:37:427"}.
  com.ibm.mobile.analytics.sdk.internal.AnalyticArgumentException:
  java.lang.IllegalArgumentException: MSAN018E: The supplied value
  was invalid: 8/17/27 3:21 AM.
   at
   com.ibm.mobile.analytics.sdk.model.EventReportBase.setTimestamp
  (
  EventReportBase.java:1504)
   at
  com.ibm.mobile.analytics.sdk.model.MfpAppLogs.setTimestamp(MfpAp
  pLogs.java:277)
   at
  com.ibm.mobile.analytics.server.processors.v1.ClientLogsProcesso
  r.parseClientLogs(ClientLogsProcessor.java:134)
   at
  com.ibm.mobile.analytics.server.processors.v1.ClientLogsProcesso
  r.processData(ClientLogsProcessor.java:81)
   at
  com.ibm.mobile.analytics.server.servlet.DataReceiver.processData
  (DataReceiver.java:167)
   at
  com.ibm.mobile.analytics.server.servlet.DataReceiver.processData
  Legacy(DataReceiver.java:107)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This impacts client log files generated by application       *
  * instances whose users  are utilizing devices which utilize a *
  * non-Gregorian calendar on iOS.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When users have a non-Gregorian calendar set on their iOS    *
  * device, client log timestamps will be converted into a       *
  * non-normalized string representation and so will not appear  *
  * correctly in the client logs.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• All dates are now normalized before converting to a string
  representation and so appear correctly in the client logs.
  

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

  MFPF/WORKLIGHT

• Fixed component ID

  5725I4301

Applicable component levels

• R620 PSY

     UP

• R630 PSY

     UP

• R700 PSY

     UP

• R710 PSY

     UP