From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8c564a80b820db35,start
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.129.105 with SMTP id nv9mr616744pbb.3.1330607212560;
        Thu, 01 Mar 2012 05:06:52 -0800 (PST)
Path: 
 h9ni26730pbe.0!nntp.google.com!news1.google.com!goblin1!goblin.stu.neva.ru!txtfeed2.tudelft.nl!tudelft.nl!txtfeed1.tudelft.nl!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!rz.uni-karlsruhe.de!news.belwue.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Thu, 01 Mar 2012 14:06:50 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Any leap year issues caused by Ada yesterday?
Message-ID: <4f4f746a$0$6565$9b4e6d93@newsspool3.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 01 Mar 2012 14:06:50 CET
NNTP-Posting-Host: 55d25a03.newsspool3.arcor-online.net
X-Trace: 
 DXC=CYIl4?@ccS^HigV@eW57PQMcF=Q^Z^V3X4Fo<]lROoRQ8kF<OcfhCO[5LCKWkH=]U_nc\616M64>ZLh>_cHTX3j]N27kM37<2G_
X-Complaints-To: usenet-abuse@arcor.de
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Date: 2012-03-01T14:06:50+01:00
List-Id: <comp.lang.ada>

News travels the wires of the internet telling us about MS Azure outages
in several places. These were seemingly caused by a piece of software
handling calendar dates involving February 29, 2012.

 Which makes me think, presuming it is as simple as it looks,
is there a software setup that prevents this kind of damage by
definition?

(The bigger companies are too big fail just because of a software bug,
even if it is of the ravenous bugblatter beast of Traal kind.
Maybe a bug that was fixed is even generating attention.
But it might help the businesses surviving only if such things do not
happen ... again.)


>From [1]:
"Yesterday, February 28th, 2012 at 5:45 PM PST Windows Azure operations
became aware of an issue impacting the compute service in a number of
regions.  The issue was quickly triaged and it was determined to be caused by
a software bug.  While final root cause analysis is in progress, this issue
appears to be due to a time calculation that was incorrect for the leap
year. Once we discovered the issue we immediately took steps to protect
customer services that were already up and running, and began creating a fix
for the issue.  The fix was successfully deployed to most of the Windows
Azure sub-regions and we restored Windows Azure service availability to the
majority of our customers and services by 2:57AM PST, Feb 29th."

http://blogs.msdn.com/b/windowsazure/archive/2012/03/01/windows-azure-service-disruption-update.aspx

via

http://www.forbes.com/sites/ciocentral/2012/02/29/microsoft-windows-azure-cloud-service-suffers-big-outage/