Over the past few months, there have been myriad occasions when I was not able to deploy servers running Fuse's ActiveMQ because a crucial XSD hosted by Fuse was not available. Is there anything that can be done about this? I am looking for either advice on hardening my system against this (mirroring tools, configuration options, etc), or acknowledgement from Fuse that there is a problem.
http://repo.fusesource.com/maven2/org/apache/activemq/activemq-core/5.3.1-fuse-02-00/activemq-core-5.3.1-fuse-02-00.xsd
We've been tracking this through Pingdom and with additional checks in our deployment scripts. Pingdom's graph of this service for the last 30 days is at the URL below, and I will attach a CSV report of the same.
http://share.pingdom.com/banners/23b63b9b
Edited by: jelder on Jul 19, 2011 6:28 PM
