For some reason, we are not able to start any of our sakai servers today and are getting this error right after the components load:

INFO: init() (2006-09-14 19:32:47,285 main_org.sakaiproject.component.kernel.function.FunctionManagerComponent)
ERROR: Could not configure datastore from input stream (2006-09-14 19:35:56,323 main_net.sf.hibernate.cfg.Configuration)
org.dom4j.DocumentException: Connection timed out Nested exception: Connection timed out
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:287)
at org.springframework.orm.hibernate.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:446)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1059)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:363)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:226)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
...


I found some info here:
http://permalink.gmane.org/gmane.comp.cms.sakai.devel/6030
"That's the damned XML parser trying to download the Hibernate DTD." ...

Has anybody else experienced this issue? Is there a workaround for this? We are running sakai v2.1.x.

Some more info. When I look at any of our HBM files in eclipse. I get a little exclamation mark right next to the header: http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd
and the message is: "The file cannot be validated as there was a connection problem."

This is a followup. As expected once "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" became available again. Sakai started up just fine. So the questions is, is it possible to have the HBM files look for the dtd in the file system so that we don't have that dependency?