On 4/12/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> : > The weird thing is that the last Solr line in the trace is
> : > org.apache.solr.util.XML.escapeCharData(XML.java:100)
> : >
> : > 99 if (start==0) {
> : > 100 out.write(str);
Thanks, I had missed that. I just verified that line 100 is the same
in both versions of the file, so the most likely explanation is a
corrupt string (the string might end in the first char of a multi char
character) that triggers the exception in Sun's UTF-8 encoder.
So the question then is, how did this bad string come about?
Chris' guess about a bad charset somewhere is probably right.
-Yonik
