>> I just triggered a reindex via the java admin client and got the
>> following error. It happens while reindexing two large collections.
>> Can anyone tell if the reindex is failing, or is this just a matter of
>> the admin client timing out during a request?
> Are there any exceptions/error messages on the server? If not, the reindex
> may have been successful and it was just the client loosing the connection.
Thanks for your reply. The exist.log covering the reindex was gone by
the time I checked, but luckily the reindex does appear to have
completed. The webpages that had been indicating certain files were
missing are now acting normally. So I think you're right that the
reindex was successful (or was still under way), and the client just
lost the connection.
That said, I haven't experienced the client losing the connection
before. Is there anything in particular on the java admin client or
eXist server that would cause the connection to be dropped, or does
this seem like something that just happens over the network? I'll
keep an eye out for this.