Matt - hey!
In your Solr console, which of these three messages do you see?
* log.info("JNDI not configured for Solr
(NoInitialContextEx)");
* log.info("No /solr/home in JNDI");
* log.warning("Odd RuntimeException while testing for JNDI: "
+ ex.getMessage());
before you see either this:
log.info("using system property solr.home: " + home );
or this:
log.info("Solr home defaulted to '" + instanceDir +
"' (could not find system property or JNDI)");
???
Thanks,
Erik
On Sep 6, 2007, at 3:41 PM, Matt Mitchell wrote:
Here you go:
<Context docBase="/usr/local/lib/solr.war" debug="0"
crossContext="true" >
<Environment name="solr/home" type="java.lang.String" value="/
usr/local/projects/my_app/current/solr-home" />
</Context>
This is the same file I'm putting into the Tomcat manager "XML
Configuration file URL" form input.
Matt
On Sep 6, 2007, at 3:25 PM, Tom Hill wrote:
It works for me. (fragments with solr 1.2 on tomcat 5.5.20)
Could you post your fragment file?
Tom
On 9/6/07, Matt Mitchell <[EMAIL PROTECTED]> wrote:
Hi,
I recently upgraded to Solr 1.2. I've set it up through Tomcat using
context fragment files. I deploy using the tomcat web manager. In
the
context fragment I set the environment variable solr/home. This use
to work as expected. The solr/home value pointed to the directory
where "data", "conf" etc. live. Now, this value doesn't get used and
instead, tomcat creates a new directory called "solr" and "solr/
data"
in the same directory where the context fragment file is located.
It's not really a problem in this particular instance. I like the
idea of it defaulting to "solr" in the same location as the context
fragment file, but as long as I can depend on it always working like
that. It is a little puzzling as to why the value in my environment
setting doesn't work though?
Has anyone else experienced this behavior?
Matt
