The Java Apache Project

Apache JServ Year 2000 Compliance and Safety

Every organization serious about avoiding Year 2000 (Y2K) crashes and errors is checking each piece of software in use as we near the turn of the century. The Apache JServ servlet engine is Y2K complaint/safe. However, there are dependencies on other associated software. And various software out there have more kinds of "date rollover" bugs than just January 1, 2000. This document will provide an overview. Note that these clock rollover bugs also occur before the actual time arrives, when any forward-referencing time is used, such as an expiration date.

Y2K Dependencies on Other Software

The Y2K compliance status of a system that includes the Apache JServ servlet engine will also depend on the following factors:

Categories of Clock Rollover Bugs

When making sure your servlets and system software will behave correctly, there are several clock rollover bugs that need to be considered, not just January 1, 2000.

The original Unix developers at Bell Labs in the late 1960's and early 1970's used this number because they had no way to know how popular Unix would become. So they just chose a time scale that would outlast their own lifetimes.

Y2K and Clock-Rollover Bug Links

Copyright (c) 1997-98 The Java Apache Project.
$Id: y2k.html,v 1.6 1999/06/09 05:21:23 jonbolt Exp $
All rights reserved.