[ http://jira.qos.ch/browse/LBCORE-231?page=com.atlassian.jira.plugin.system.i... ] Greg Thomas commented on LBCORE-231: ------------------------------------ I found the underlying problem - and it's nothing to do with logback. My ISP decided to install one of those DNS redirectors a while back without me realising, so typing in a unknown host takes you to a landing page covered in advertising. That meant that the deliberately bad URL in unknownURL did in fact resolve, so the test failed in an unexpected way. Thankfully, my ISP did at least have the grace to make this "facility" optional, so I've disabled it and now all is well. Please feel free to close this issue.
unknownURL Test fails on Ubuntu 10.04 -------------------------------------
Key: LBCORE-231 URL: http://jira.qos.ch/browse/LBCORE-231 Project: logback-core Issue Type: Bug Components: Joran Affects Versions: 1.0.0 Environment: Ubuntu 10.04, Sun jdk1.5.0_22, latest logback snapshot Reporter: Greg Thomas Assignee: Logback dev list
When trying to build logback on Ubuntu 10.04, the test unknownURL in ch.qos.logback.core.joran.action.IncludeActionTest fails. The test is currently looking for either a UnknownHostException or IOException to be raised. In practice, on the stated environment, the following exceptions are raised; 19:04:20,488 |-ERROR in ch.qos.logback.core.joran.event.SaxEventRecorder@1016632 - XML_PARSING - Parsing fatal error on line 6 and column 113 org.xml.sax.SAXParseException: The reference to entity "ClientLocation" must end with the ';' delimiter. at org.xml.sax.SAXParseException: The reference to entity "ClientLocation" must end with the ';' delimiter. ... 19:04:20,488 |-ERROR in ch.qos.logback.core.joran.action.IncludeAction - Error while parsing http://logback2345.qos.ch ch.qos.logback.core.joran.spi.JoranException: Problem parsing XML document. See previously reported errors. at ch.qos.logback.core.joran.spi.JoranException: Problem parsing XML document. See previously reported errors. The simplest solution would to add the SAXParseException to the list of acceptable exceptions, but wonder if that's masking a wider problem ...
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira