I finally figured this out yesterday. Because the jar files have the version in
the file name, I had a mix of jars from different versions. Depending on the
load order, Solr could get into a situation where it was calling something that
didn’t exist.
That was mysterious.
wunder
Walter Underwoo
SOLR-9739 changed the writeStr method to accept a CharSequence from
String in 6.4 so my guess is that your classpath has a newer (6.4+)
solrj version but an older solr-core jar that cannot find this new
method.
On Sat, Feb 18, 2017 at 5:16 AM, Walter Underwood
wrote:
> Any idea why I would be get
Any idea why I would be getting this on a brand new, empty collection on the
first update?
HTTP ERROR 500
Problem accessing /solr/tutors_shard1_replica9/update. Reason:
Server ErrorCaused
by:java.lang.NoSuchMethodError:
org.apache.solr.update.TransactionLog$LogCodec.writeStr(Ljava/lang/Stri
