I would check if the Byte-order mark is the cause:
https://en.wikipedia.org/wiki/Byte_order_mark
The error message does not seem to be a perfect match to this issue,
but a good thing to check anyway.
That symbol (right at the file start) is usually invisible and can
trip Java XML parsers for some reasons. So I would check what editor
on your platform understands Byte-order mark and/or try to strip it.
I that does not help, I would run the file through XML validator to
see if there are maybe invisible/unexpected characters elsewhere in
the file.
Regards,
Alex.
On Sun, 21 Oct 2018 at 09:55, Moshe Recanati | KMS <mos...@kmslh.com> wrote:
>
> Hi,
>
> We've specific exception that happening only on Thai core and only once we're
> using SolrCloud.
>
> Same indexing activity is running successfully while running on EN core with
> SolrCloud or with Thai core and standalone configuration.
>
>
> We're running on Linux with Solr 4.6
>
> and with -Dfile.encoding=UTF-8 on all scenarios.
>
>
> This is the exception:
>
> com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR,
> code 26))
> and
>
> org.apache.solr.common.SolrException: Invalid UTF-8 middle byte 0xe0 (at char
> #1, byte #-1)
> at org.apache.solr.handler.loader.XMLLoader.load(XMLLoader.java:176)
> at
> org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:92)
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74)
> at
>
>
> Do you know what is the root cause of it and how to overcome it.
>
> As I mentioned this is not happning on standalon or in Core EN in any
> scenario.
>
>
> Thank you,
>
> Moshe
