: get fresh log messages when the server is started again. The new
: schema.xml that shows the changes is via:
:
: http://localhost:8983/solr/admin/get-file.jsp?file=schema.xml
:
: Maybe there's some extra magic to getting the new field to show up at
: all as null or something valuable? Is that th
The java process is terminating to the point of not being visible in
the process list. As with my other experiences when shutting down java
processes it takes approximiately 5 seconds to completely go away. At
least to the point of nothing listening on the port I am aware that
refreshes of the solr
: replacing jetty's webapps/solr.war -- changes to schema.xml are not
: taking place by the method of exchanging solr/conf/schema.xml for an
: updated one with a new field name="foobar" and restarting the sending
: the solr java process a TERM and starting afresh...
you're terminated the java proc
I am having a similar(?) problem with 1.2 upgraded from an earlier
incubator release. We upgraded by building the new war with ant by and
replacing jetty's webapps/solr.war -- changes to schema.xml are not
taking place by the method of exchanging solr/conf/schema.xml for an
updated one with a new f
Hi Ryan,
I have my .war file located outside the webapps folder (I am using multiple
Solr instances with a config as suggested on the wiki:
http://wiki.apache.org/solr/SolrTomcat).
Nevertheless, I touched the .war file, the config file, the directory under
webapps, but nothing seems to be working
I don't use tomcat, so I can't be particularly useful. The behavior you
describe does not happen with resin or jetty...
My guess is that tomcat is caching the error state. Since fixing the
problem is outside the webapp directory, it does not think it has
changed so it stays in a broken state
