: > Is there a way to find out what string is being written (perhaps
: > modify the code to catch that particular exception and display the
: > string)
:
: I know its a bunch of text I culled from pages like this:
:
: <http://www.purl.org/swinburnearchive/txt/aicatlnt00>
:
: (it'll redirect)
I got a flat 404.
to pinpoint the exact text, i would start by changing the start/rows
params so that you get one doc at a time untill you find one that causes
the error .. then change your fl to just be the id and one other field,
and try each of the field names untill you find the one with the data that
caused the problem.
my hunch is that when POSTing the doc, the wrong charset (or char
encoding, i allways get them confused) was used by Jetty, so a corrupt
string was indexed, and it isn't obvious untill it was displayed.
: > 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);
I commited a modified XML.java last night, your line number may not match
Erik's build.
: I actually saw the stack trace in the partial not-well-formed XML
: response on the client as well, if that bit of trivia is useful.
that's pretty typical of a Solr error page unfortunately.
-Hoss
