The failure looks like because the
jboss.org has been down for
maintenance and it looks like the parsing of a hibernate-cfg.xml in a
deployment leads to failures like:
Caused by: java.lang.Exception: {"JBAS014671: Failed services" =>
{"jboss.persistenceunit.\"jpa_cfgfile.jar#mypc\"" =>
"org.jboss.msc.service.StartException in service
jboss.persistenceunit.\"jpa_cfgfile.jar#mypc\":
org.hibernate.metamodel.source.MappingException: Error accessing stax stream
Caused by: org.hibernate.metamodel.source.MappingException: Error accessing stax
stream
Caused by: com.ctc.wstx.exc.WstxIOException: Server returned HTTP response code: 503
for
URL:http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd
Caused by: java.io.IOException: Server returned HTTP response code: 503 for
URL:http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd"}}
<
http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd>
Looks like we aren't resolving the dtd within the hibernate jars.
-Jaikiran
On Saturday 15 June 2013 03:19 PM, ci-builds(a)redhat.com wrote:
wildfly-master-testsuite-ip6 - Build # 7354 - Failure:
Check console output at to view the results.
Public:
http://hudson.jboss.org/hudson/job/wildfly-master-testsuite-ip6/7354
Internal:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-master-tes...
Test summary:
1 tests failed.
FAILED:
org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase.org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase
Error Message:
Cannot deploy: jpa_cfgfile.jar
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev