Hi Jeff,

 

-- I'm pretty sure I had put it as a suggestion in the docs.  

 

Yes, yes you had.  It’s another reason I’m annoyed at myself for taking the 
difficult route.  I had seen a few comments complaining about small issues 
in NSSM (occasional issues with stopping ungracefully) and rather than 
researching those further I decided to try grabbing Jetty and using its 
service installer.  However I then hit issues with the “community version” 
of the wrapper not being available in 64bit…and down the dark path I went.

 

During early testing I had hit issues with SOLR running out of memory and 
because at the time it was using the same JVM as ColdFusion, ColdFusion 
stopped working as well.  This is why I was using a separate JVM to 
ColdFusion and wanting 64bit so I could allocate whatever memory SOLR 
needed.

 

-- We couldn't afford professional actors, so we improvised

 

While it might not be the most professional look it’s still funny.  Too 
many IT videos are boring and dry, so it makes for a nice change J  It’s 
certainly a lot better than anything I could do.

 

-- This is used in the *url* path that Solr uses to find the instance (it 
should be noted in the fthint).

 

The hint is showing but I didn’t follow exactly what it meant.  But I think 
I just realised what it’s doing.  So if SOLR is running as *
http://myserver.com:8983* <http://myserver.com:8983/> the default URL for 
SOLR is *http://myserver.com:8983/solr/* <http://myserver.com:8983/solr/>and 
therefore to access the collection you would need the value from 
“path”, which by default would be /solr/<myprojectname>.  The <projectname> 
is stored in solr.xml which then contains the file path.  The file path is 
taken from “Solr Collection Instance Dir”.  

 

If that correct then it’s now pretty obvious  J  I think I was confusing 
myself a bit because the path was /solr/<projectname> and the collection 
directory was <projectname>/solr/ and was occasionally looking at those the 
wrong way around.

 

Thanks for taking the time to respond and as I said to Sean, brilliant 
plugin guys!

 

Cheers

Mark

-- 
-- 
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: [email protected]
To unsubscribe, email: [email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry


Reply via email to