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 admin interface in a web browser fails. I also 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 the behaviour of the default field tag? Or maybe there's something deeper... -- Jonathan On Mon, Jun 11, 2007 at 10:32:26PM -0700, Chris Hostetter wrote: > : 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 process and starting a new one and it's not > seeing the new file? That's, ... hmm, i really have no idea what that is. > > Are you sure the first process is completely shutting down? If the old > process is still listening on the port the new process won't start up > cleanly. Other then that, i can't think of any reason why a new java > process wouldn't see the new file. > > > -Hoss >
