Dashboard > CruiseControl > ZeroLengthFiles
ZeroLengthFiles Log In View a printable version of the current page.

Added by Anonymous , last edited by Jeffrey Fredrick on Jun 13, 2005  (view change)
Labels: 
(None)

experiencing this problem with Java 5? there's a special page for that: KnownIssuesWithJdk1.5


Zero length files in the cache directory means your are getting an exception during the xsl transform. The most common reason for this is mismatched versions of the xerces and xalan jar files. Solutions reported on the mailing list include:

  • changing jdk versions, such as from 1.4.2_01 to 1.4.2_02
  • removing the jars from the cruisecontrol/WEB-INF/lib directory (build w/the property "jdk1.4" defined and the war won't have these jars)
  • updating the tomcat/common/endorsed folder with the latest versions of the Xerces/Xalan jars, available at http://xml.apache.org/. This fixes issues with running the web app under Tomcat 4.1.27. Don't forget to update the taglib uri in most jsps since Tomcat 4.1.27 uses JSP 1.2 ...

When trying any of these options be sure to delete the existing zero length files or you won't see any change.

In a Unix environemt you shoudl also try to set encoding to UTF-8 .. <log dir="logs" encoding="UTF-8"/> .


If you prefer distinct steps to follow instead of options try:

  1. remove existing zero length files from the cache directory
  2. remove the xalan/xerces from the WEB-INF/lib directory
  3. create the file override.properties in cruisecontrol/reporting/jsp and add the line "jdk1.4=true"
  4. put the latest xalan/xerces jars some place they'll be used. Either tomcat/common/endorsed or jre/lib/ext
Powered by a free Atlassian Confluence Open Source Project / Non-profit License granted to ThoughtWorks, Inc.. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators