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 field name="foobar" and restarting the sending the solr java process a TERM and starting afresh...
-- Jonathan On Fri, Jun 08, 2007 at 03:17:30PM -0400, [EMAIL PROTECTED] wrote: > 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. > > Any other suggestions? Is someone else experiencing the same problem? > thanks, > mirko > > > Quoting Ryan McKinley <[EMAIL PROTECTED]>: > > > 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. > > > > if you "touch" the .war file, does it restart ok? > > > > but i'm just guessing... > > > >
