KnownIssuesWithJdk1.5 - CruiseControl

note on context: this page is for problem between previous versions of CC and JDK 1.5, not a collection of random 1.5 problems.

There is no known problem with CC 2.4.0 and JDK 1.5 when using the bundled versions of Xalan and Xerces. Without them a ArrayIndexOutOfBoundsException is triggered in the JDK's internal version (com.sun.org.apache.xalan)

see also:
CruiseControl Issue with JDK1.5
http://jira.public.thoughtworks.org/browse/CC-172 (fixed in 2.2.2)

HTMLEmailPublisher fails to transform xml (fixed in 2.2.2)
http://jira.public.thoughtworks.org/browse/CC-112

Error transforming log.xml, ArrayIndexOutOfBoundsException (fixed in 2.3)
http://jira.public.thoughtworks.org/browse/CC-198

this is a special case of the ZeroLengthFiles problem.

From: William Sporrong
Sent: Wednesday, March 09, 2005 4:32 AM
Subject: [Cruisecontrol-user] RE: RE: FileNotFoundException when doing HTML email publish

I had the same problem and resolved it by deleting the xalan lib from
CruiseControl main/lib. It was a conflict between Java 1.5 XML classes and cc's old xalan lib.

/william

This FileNotFoundException is CC-112 solved with 2.3. See above. Note the advice is valid for CC 2.2 only. Users running 2.3+ should not delete the bundled xalan library.

From: Guerry Semones
Sent: Friday, March 04, 2005 1:56 PM
To: cruisecontrol-user@lists.sourceforge.net
Subject: [Cruisecontrol-user] OutOfMemory and to Merge or not to Merge

Okay, I'm one of those that is still trying to ferret out the
"OutOfMemory" error that eventually occurs post-build when CC publishs our email notification. I'm not the only one to have posted about this, but nothing that has come out has helped, soooo....

I have seen mentioned in several places, including the Wiki here:

http://confluence.public.thoughtworks.org/display/CC/OutOfMemoryError

"If you are merging the xml log files generated by cruise control (not advised) cruise control will report an Out of Memory error after merge
becomes unable to handle the size of the log file, for example."

The log files for a given CC run in my logs directory go from 1.5M to
4.5M in size depending on the type of run (unit tests only vs unit and integration tests).

In my build.xml, I have had the following directive since like forever:

If this is "not advised" as mentioned above, then what are my alternatives

I am running CC 2.2, JDK 1.5, and ANT 1.6.2.

Incidently, CC 2.2 with JDK 1.4 never showed this behavior.

Thanks in advance,

Guerry