Timestamp mismatch between log entries and machine time on HP JDK

(Doc ID 1320648.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version: 9.2 to 10.0
Information in this document applies to any platform.


Sometimes we may observe time drifting (between JDK and system time) is occurring on HP systems. It may result is current system (or machine) time not getting reflected in the timestamps for entries in access log and/or server log and/or domain log.

The issue can also manifest into an odd behavior where SAML assertions are rejected at WebLogic Service Provider (SP) end because they are being treated as expired ones given the constraints "NotBefore" and "NotOnOrAfter". Sample condition (extracted from SAML2 assertion) is:

<saml:Conditions NotBefore="2011-03-24T22:54:45.312Z" NotOnOrAfter="2011-03-24T22:56:45.312Z">


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms